Atel IWE1200A-G, Руководство пользователя

Страница: 78 / 87

3.7.3.2. Periodical Restart
Fig. 106. Periodical restart settings.
The access gateway can be configured to restart at a specific time every day. This mechanism is
aimed at solving lockup caused by firmware bugs that surface only after the access gateway has oper-
ated for a long time. Specify the 24-hour time in
Auto-restart at hh:mm everyday and enable Func-
tionality to activate this auto recovery mechanism.
3.7.4. LAN Device Management
Fig. 107. LAN device management settings.
LAN device management is for the access gateway to pass management requests from the Internet
through its built-in NAT server to devices on the private network. As a result, network devices (such
as access points) behind the NAT server can be managed from the Internet. In this way, the access
gateway acts as a management proxy for the LAN devices. In addition, the gateway can periodically
check whether the managed devices are working by PINGing them (
Check devices if alive every n
minutes ). If it detects a device not working, it can send an SNMP trap ( remote system logging ) to a
back-end server to report such a situation (see Section 3.7.2.3 for more information). The LAN device
management functionality is especially useful for a WISP to remotely manage deployed APs that are
usually invisible from the Internet due to the employment of NAT for IP address space conservation.
A management server from the Internet sees a managed LAN device as a combination of the access
gateway’s WAN IP address and a
Virtual Port reserved for this device. When a TCP or UDP-based
management request (specified by the Protocol field) is received by the access gateway from the
Internet, the gateway translates the destination IP address and destination port of the request to the
corresponding
Device IP Address and Device Port . In other words, this request is passed through the
built-in NAT server of the gateway and routed to the corresponding managed LAN device.
For example, Fig. 108 illustrates a LAN device management scenario based on the settings values in
Fig. 107. AP1 can be managed from the management server by using a Web browser and a URL
“
http://61.16.31.110:60001 ”. AP2 can be managed by using a Web browser and a URL
“ http://61.16.31.110:60002 ”. AP3 can be managed from the management server by using an SNMP
manager program via IP address 61.16.31.110 and port 60003. Destination IP addresses and destina-
tion ports of management packets for AP1, AP2, and AP3 are translated to 192.168.168.201:80,
192.168.168.202:80, and 192.168.168,201:161, respectively. (161 is a well known port for SNMP
management.)
71