 |
Reference Manual |
 |
HOW TO use NAT32 with Wireless LAN Adapters:
HOW TO use NAT32 with several private networks:
HOW TO use NAT32 with private networks behind private Gateways
Wireless LAN adapters are very similar to wired LAN adapters, except
that they use a 2.4 GHz radio link to establish connectivity. If your Wireless
LAN adapter is the only LAN Adapter in your system, then NAT32 treats it
just like a standard LAN adapter and no special measures are needed.
Some networks have both a wired LAN adapter and a Wireless LAN adapter
installed on the NAT32 machine as in the following diagram:

The following points should be noted:
-
Class B private addresses must be used on both private LANs.
-
Configure the Wired LAN adapter to use 172.16.2.1 (Mask 255.255.255.0)
under Windows and 172.16.2.254 (Mask 255.255.255.0) under NAT32.
-
Configure the Wireless LAN adapter to use 172.16.3.1 (Mask 255.255.255.0)
under Windows and 172.16.3.254 (Mask 255.255.255.0) under NAT32.
-
Start a NAT32 configuration run by clicking Start/Programs/Configure NAT32.
-
Either private adapter can be specified as the Secondary Interface, the
Internet adapter is the Primary Interface.
-
All the other machines on the Wired LAN use 172.16.2.254 as their
gateway and DNS address.
-
All the other machines on the Wireless LAN use 172.16.3.254 as their
gateway and DNS address.
-
If you require all machines to be visible in the Windows Network
Neighborhood of each machine, execute the NAT32 nb on command
so that NetBios broadcast packets are propagated from the 172.16.2.0 subnet
to the 172.16.3.0 subnet and vice versa.
Some networks have both a wired LAN adapter and a Wireless LAN adapter
installed on some other machine as in the following diagram:

In this case, the machine called Client Machine in the above diagram
must act as a gateway for the wireless LAN and must therefore have
IP Forwarding (IP Routing) enabled.
The following points should be noted:
-
To ensure that NAT32 can reach the wireless LAN, the following network-specific
route must be added to the NAT32 routing table:
route add 172.16.3.0 255.255.255.0 172.16.2.10 15 0
-
You can add the above command to your startup
file.
Finally, note that the use of Class B addresses is required because
NAT32 maps according to
network, not subnet. All machines,
including the machines on other private LANs, will then have Internet access
through NAT32.
SEE ALSO
route,
winrt