Chapter Three
Operation
Page 35
© April 2007
hop router (or gateway) will then deliver the data to the required destination (or forward it on
to another router that will).
Client
Router
LAN C
169.254.102.17
192.168.0.73
LAN A
Client
Bridge
Access Point
Bridge
192.168.0.34
192.168.0.34
192.168.0.72
192.168.0.72
Client
Router
LAN B
169.254.109.40
192.168.0.74
The above network diagram illustrates a situation where routing rules may need to be
configured. In this example, the 905U-E clients need only specify the Access Point as their
default gateway (i.e. they require no routing rules be configured). However, for the Access
Point to be able to deliver traffic to LAN B and LAN C it needs to have routing rules
configured that specify the respective 905U-E client/routers as next-hop routers (i.e.
gateways) to networks B and C. Note that devices on LAN A should specify the 905U-E
Access Point as their default gateway. An alternative to adding routing rules to the 905U-E in
this example would be for each device on LAN A that needs to communicate with LANs B
and C to independently have routing rules specifying the 905U-E clients at B and C as
gateways to those networks.
The routing rules for the Access Point in the above example are shown below. The first entry
shows the route to LAN B. The gateway for the route to LAN B is configured as the wireless
IP address of the 905U-E client connected to LAN B. The destination for the route is
configured as the network address of LAN B. Because the host id of the destination IP
address is 0, it specifies a network address. Consequently, any traffic received at the Access
Point with destination IP address 169.254.109.x (where x is any host id) will be forwarded to
the 905U-E at LAN B.
