Quatech HD500, IN5000, DP500 user manual Not be the same

Quatech, Inc. AirborneDirect™ User Manual

Step

Optional

Press Restart [Button]

Description

Restarts the device. After the device as rebooted it will attempt to authenticate to the configured network. As long as the network is in range the wireless interface will connect.

Access to the public network from the private network is now possible.

The private network supports the Airborne™ discovery protocol (UDAP) and will respond to discovery requests.

	The subnet for the private network IP addresses (Ethernet Client and Gateway) and
	public IP address (WLAN), obtained by the module via the wireless interface, MUST
	NOT be the same.
	Failure to observe this requirement will result in unpredictable behavior of the
	adapter.

When attempting to make an out-bound connection to a device on the public network, the public network IP address of the device should be used e.g. In Figure 21 the client with address 192.168.2.100 wants to connect to an FTP server, with the address of 123.45.67.99, on the public network to perform a firmware download. The FTP address that would be used in the Configuration/Advanced Settings FTP Server Address or Name would be

123.45.67.99.Note that this is not within the subnet of the Ethernet client, however the NAT router will do the necessary address translations and packet header manipulations to ensure the out-bound and in-bound connections are maintained.

Any traffic between the Airborne Ethernet Adapter’s Ethernet interface and Ethernet client, on the private network, will not be broadcast on the public network unless it is directed at the public network.

For most users there will be no modification of the private network settings needed and if the target Ethernet client uses DHCP to obtain an IP address, no change in configuration will be required either.

86 2/21/2011 100-8510-110