Cry How To...

Set up IP Forwarding

The successful implementation of IP forwarding enables one workstation to sit on two LANs and to act as a gateway forwarding IP packets from one LAN to another. IP forwarding is also referred to as ‘bridging’ networks.

Requirements:

• At least two network cards installed in the workstation or server.
• Each network card to be connected to a different LAN

To set-up:

On the ‘gateway’ PC:

1. Ensure that a correct IP address is specified for each network card and that the IP address is static and not allocated from a DHCP server.
2. Enabled IP forwarding:

   On Windows XP:

   1. Open ‘Control Panel’
   2. Double click on ‘Network Connections’ to open it.
   3. Select/highlight the two network connections to ‘bridge’.
   4. Right click and select ‘Bridge Connections’.

   On Windows NT:

   1. Open ‘Control Panel’
   2. Double click on ‘Network’.
   3. Click the ‘Protocols’ tab.
   4. Double click on ‘TCP/IP Protocol’.
   5. Click the ‘Routing’ tab.
   6. Tick ‘Enable IP Forwarding’

On the workstations that will use the gateway, the workstation must be set-up to use the gateway:

1. Open a command/DOS session.
2. Type:

   Route add -p <sub-net-address> mask <subnet-mask> <IP-address-of-gateway>

   Or

   Route add -p <sub-net-address> mask <subnet-mask> <name-of-gateway>

   For example, if the remote subnet address is 192.0.0.x with a mask of 255.255.255.0, and the address of the gateway on the local LAN is 10.1.137.1, then the route command would be:

   Route –p add 192.0.0.0 mask 255.255.255.0 10.1.137.1

   or this could be expressed using the name of the gateway thus:

   Route –p add 192.0.0.0 mask 255.255.255.0 GatePC

   The ‘-p’ flag makes the route permanent across reboots. By default route changes are lost when the workstation is rebooted.

   Instead of specifying the IP address of the gateway, the name of the gateway can be specified.

   You will need to be logged in as a local administrator of the workstation to do this.

Workstations that will use the gateway will not know the IP addresses of the ‘remote’ workstations. These must be defined explicitly:

1. Edit or create the file ‘C:\WINNT\System32\drivers\etc\lmhosts.sam’ with a text editor (such as notepad).
2. Add a line at the end of the file of the following form for each ‘remote’ workstation that this workstation needs to talk to:

   <remote-IP-address> <computer-name>

   For example, if the remote computer were called ‘portable_brain’ and its IP address on the remote network were ‘10.1.128.29’ then the following should be appended to the lmhosts file:

   10.1.128.29 portable_brain

   As a rule each computer listed in the lmhosts file should have a reciprocal entry in its lmhosts file.

3. Open ‘Control Panel’
4. Double click on ‘Network’.
5. Click the ‘Protocols’ tab.
6. Double click on ‘TCP/IP Protocol’.
7. Click the ‘WINS addresses’ tab.
8. Tick ‘Enable LMHOSTS lookup’
9. Click ‘[Import LMHOSTS…]’
10. Open the file ‘C:\WINNT\System32\drivers\etc\lmhosts.sam’

Note:

• If the name specified in the LMHOSTS file is different from the real host-name then communications will still be possible but it will not be possible to mount shared drives.

These notes have been tested with Windows NT4, W2K and XP Workstation.