Establishing and maintaining ip tunnels, Ip addressing for end devices, Using non-ip protocols – Allied Telesis AT-WL2411 User Manual
Page 95
AT-WL2411 Version 1.80 Installation and User’s Guide
95
Establishing
and
Maintaining IP
Tunnels
If the IP tunnel port control is enabled, the root access point sends hello
messages to each IP address in its IP address list. An access point on a
remote IP subnet automatically establishes an IP tunnel if it receives an
IP hello message from the root access point. An access point attached
through an IP tunnel transmits hello messages on the remote subnet so
that other access points on the remote subnet that do not receive IP
hello messages can also attach to the network.
If IP hello messages are sent to IP unicast addresses, then some access
points on a remote subnet will not receive hello messages; therefore,
those access points cannot establish an IP tunnel. If bridging is disabled
on the subnet, wireless traffic is forwarded to and from these access
points through data link tunnels. A data link tunnel is logically
concatenated with an IP tunnel so that wireless traffic can be completely
isolated from the remote IP subnet.
If you need to bridge to a remote subnet, see
IP Addressing
for End Devices
IP end devices must be assigned IP addresses that are on the home IP
subnet. There are no address restrictions for non-IP end devices.
Using Non-IP
Protocols
Servers that use a routable network protocol such as IP or IPX may be
located on any subnet; however, triangular routing can be minimized if
servers are located on the home IP subnet. (Note that this is also true for
standard mobile IP.) You should be able to use default flooding and
bridging settings if you are using routable protocols, even if servers are
located on remote IP subnets.
The NNL protocol is a simple Non-routable Network Layer protocol that
is used to carry high-layer data in a local area network environment. An
NNL gateway forwards NNL traffic to non-NNL hosts such as TCP/IP
hosts. You can use the default flooding and bridging settings, and
minimize triangular routing, if NNL gateways are located on the home
subnet. If NNL gateways are located or remote subnets, you must enable
outbound multicast flooding and secondary bridging.