4. Configuring the other internal to-be MASQed machines

Besides setting the appropriate IP address for each internal MASQed machine, you should also set each internal machine with the appropriate gateway IP address of the Linux MASQ server and required DNS servers. In general, this is rather straight forward. You simply enter the address of your Linux host (usually 192.168.0.1) as the machine's gateway address.

For the Domain Name Service, you can add in any DNS servers that are available. The most apparent one should be the one that your Linux server is using. You can optionally add any "domain search" suffix as well.

After you have properly reconfigured the internal MASQed machines, remember to restart their appropriate network services or reboot them.

The following configuration instructions assume that you are using a Class C network with 192.168.0.1 as your Linux MASQ server's address. Please note that 192.168.0.0 and 192.168.0.255 are reserved TCP/IP address.

As it stands, the following Platforms have been tested as internal MASQed machines. This is only an EXAMPLE of all of the compatible OSes out there:

• Apple Macintosh OS (with MacTCP or Open Transport)
• Commodore Amiga (with AmiTCP or AS225-stack)
• Digital VAX Stations 3520 and 3100 with UCX (TCP/IP stack for VMS)
• Digital Alpha/AXP with Linux/Redhat
• IBM AIX running on a RS/6000
• IBM OS/2 (including Warp v3)
• IBM OS400 running on a AS/400
• Linux 1.2.x, 1.3.x, 2.0.x, 2.1.x, 2.2.x
• Microsoft DOS (with NCSA Telnet package, DOS Trumpet works partially)
• Microsoft Windows 3.1 (with the Netmanage Chameleon package)
• Microsoft Windows For Workgroup 3.11 (with TCP/IP package)
• Microsoft Windows 95, OSR2, 98, 98se
• Microsoft Windows NT 3.51, 4.0, 2000 (both workstation and server)
• Novell Netware 4.01 Server with the TCP/IP service
• SCO Openserver (v3.2.4.2 and 5)
• Sun Solaris 2.51, 2.6, 7

4.1 Configuring Microsoft Windows 95

1. If you haven't installed your network card and adapter driver, do so now. Description of this is beyond the scope of this document.

2. Go to the 'Control Panel' --> 'Network'.

3. Click on Add --> Protocol --> Manufacture: Microsoft --> Protocol: 'TCP/IP protocol' if you don't already have it.

4. Highlight the TCP/IP item bound to your Windows95 network card and select 'Properties'. Now goto the 'IP Address' tab and set IP Address to 192.168.0.x, (1 < x < 255), and then set the Subnet Mask to 255.255.255.0

5. Now select the "Gateway" tab and add 192.168.0.1 as your gateway under 'Gateway' and hit "Add".

6. Under the 'DNS Configuration' tab, make sure to put in a name for this machine and enter in your official domain name. If you don't have your own domain, put in the domain of your ISP. Now, add all of the DNS server that your Linux host uses (usually found in /etc/resolv.conf). Usually these DNS servers are located at your ISP though you can be running either your own CACHING or Authoritative DNS server on your Linux MASQ server as well. Optionally, you can add any appropriate domain search suffixes as well.

7. Leave all the other settings as they are unless you know what you're doing.

8. Click 'OK' on all dialog boxes and restart system.

9. Ping the linux box to test the network connection: 'Start/Run', type: ping 192.168.0.1
   (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

10. You can optionally create a HOSTS file in the C:\Windows directory so that you can ping the "hostname" of the machines on your LAN without the need for a DNS server. There is an example called HOSTS.SAM in the C:\windows directory.

4.2 Configuring Windows NT

1. If you haven't installed your network card and adapter driver, do so now. Description of this is beyond the scope of this document.

2. Go to 'Control Panel' --> 'Network' --> Protocols

3. Add the TCP/IP Protocol and related Components from the 'Add Software' menu if you don't have TCP/IP service installed already.

4. Under 'Network Software and Adapter Cards' section, highlight the 'TCP/IP Protocol' in the 'Installed Network Software' selection box.

5. In 'TCP/IP Configuration', select the appropriate adapter, e.g. [1]Novell NE2000 Adapter. Then set the IP Address to 192.168.0.x (1 < x < 255), then set Subnet Mask to 255.255.255.0 and Default Gateway to 192.168.0.1

6. Do not enable any of the following options (unless you know what you are e xactly doing):
   • 'Automatic DHCP Configuration' : Unless you have a DHCP server running on your network.
   • Put anything in the 'WINS Server' input areas : Unless you hav e setup one or more WINS servers.
   • Enable IP Forwardings : Unless you are routing on your NT machine and really -REALLY- know EXACTLY what you're doing.

7. Click 'DNS', fill in the appropriate information that your Linux host uses (usually found in /etc/resolv.conf) and then click 'OK' when you're done.

8. Click 'Advanced', be sure to DISABLE 'DNS for Windows Name Resolution' and 'Enable LMHOSTS lookup' unless you known what these options do. If you want to use a LMHOSTS file, it is stored in C:\winnt\system32\drivers\etc.

9. Click 'OK' on all dialog boxes and restart system.

10. Ping the linux box to test the network connection: 'File/Run', type: ping 192.168.0.1
    (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

4.3 Configuring Windows for Workgroup 3.11

1. If you haven't installed your network card and adapter driver, do so now. Description of this is beyond the scope of this document.

2. Install the TCP/IP 32b package if you don't have it already.

3. In 'Main'/'Windows Setup'/'Network Setup', click on 'Drivers'.

4. Highlight 'Microsoft TCP/IP-32 3.11b' in the 'Network Drivers' section, click 'Setup'.

5. Set the IP Address to 192.168.0.x (1 < x < 255), then set the Subnet Mask to 255.255.255.0 and Default Gateway to 192.168.0.1

6. Do not enable any of the following options (unless you know what you are exactly doing):
   • 'Automatic DHCP Configuration' : Unless you have a DHCP server running on your network.
   • Put anything in the 'WINS Server' input areas : Unless you have setup one or more WINS servers.

7. Click 'DNS', fill in the appropriate information your Linux host uses (usually found in /etc/resolv.conf). Then click 'OK' when you're done with it.

8. Click 'Advanced', check 'Enable DNS for Windows Name Resolution' and 'Enable LMHOSTS lookup' found in c:\windows.

9. Click 'OK' on all dialog boxes and restart system.

10. Ping the linux box to test the network connection: 'File/Run', type: ping 192.168.0.1
    (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

4.4 Configuring UNIX Based Systems

1. If you haven't installed your network card and recompile your kernel with the appropriate adapter driver, do so now. Description of this is beyond the scope of this document.
2. Install TCP/IP networking, such as the net-tools package, if you don't have it already.

3. Set IPADDR to 192.168.0.x (1 < x < 255), then set NETMASK to 255.255.255.0, GATEWAY to 192.168.0.1, and BROADCAST to 192.168.0.255

   For example with Redhat Linux systems, you can edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file, or simply do it through the Control Panel. These changes are different for other UNIXes such as SunOS, BSDi, Slackware Linux, Solaris, SuSe, Debian, etc...). Please refer to your UNIX documentation for more information.

4. Add your domain name service (DNS) and domain search suffix in /etc/resolv.conf and for the appropreiate UNIX versions, edit the /etc/nsswitch.conf file to enable DNS services.

5. You may want to update your /etc/networks file depending on your settings.

6. Restart the appropriate services, or simply restart your system.

7. Issue a ping command: ping 192.168.0.1 to test the connection to your gateway machine.
   (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

4.5 Configuring DOS using NCSA Telnet package

1. If you haven't installed your network card, do so now. Description of this is beyond the scope of this document.

2. Load the appropriate packet driver. For example: using a NE2000 Ethernet card set for I/O port 300 and IRQ 10, issue nwpd 0x60 10 0x300

3. Make a new directory, and then unpack the NCSA Telnet package: pkunzip tel2308b.zip

4. Use a text editor to open the config.tel file

5. Set myip=192.168.0.x (1 < x < 255), and netmask=255.255.255.0

6. In this example, you should set hardware=packet, interrupt=10, ioaddr=60

7. You should have at least one individual machine specification set as the gateway, i.e. the Linux host:

   name=default
   host=yourlinuxhostname
   hostip=192.168.0.1
   gateway=1
   

8. Have another specification for a domain name service:

   name=dns.domain.com ; hostip=123.123.123.123; nameserver=1
   

   Note: substitute the appropriate information about the DNS that your Linux host uses

9. Save your config.tel file

10. Telnet to the linux box to test the network connection: telnet 192.168.0.1 If you don't receive a LOGIN prompt, please verify your network configuration.

4.6 Configuring MacOS Based System Running MacTCP

1. If you haven't installed the appropriate driver software for your Ethernet adapter, do so now. Description of this is beyond the scope of this document.

2. Open the MacTCP control panel. Select the appropriate network driver (Ethernet, NOT EtherTalk) and click on the 'More...' button.

3. Under 'Obtain Address:', click 'Manually'.

4. Under 'IP Address:', select class C from the popup menu. Ignore the rest of this section of the dialog box.

5. Fill in the appropriate information under 'Domain Name Server Information:'.

6. Under 'Gateway Address:', enter 192.168.0.1

7. Click 'OK' to save the settings. In the main window of the MacTCP control panel, enter the IP address of your Mac (192.168.0.x, 1 < x < 255) in the 'IP Address:' box.

8. Close the MacTCP control panel. If a dialog box pops up notifying you to do so, restart the system.

9. You may optionally ping the Linux box to test the network connection. If you have the freeware program MacTCP Watcher, click on the 'Ping' button, and enter the address of your Linux box (192.168.0.1) in the dialog box that pops up. (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

10. You can optionally create a Hosts file in your System Folder so that you can use the hostnames of the machines on your LAN. The file should already exist in your System Folder, and should contain some (commented-out) sample entries which you can modify according to your needs.

4.7 Configuring MacOS Based System Running Open Transport

1. If you haven't installed the appropriate driver software for your Ethernet adapter, do so now. Description of this is beyond the scope of this document.

2. Open the TCP/IP Control Panel and choose 'User Mode ...' from the Edit menu. Make sure the user mode is set to at least 'Advanced' and click the 'OK' button.

3. Choose 'Configurations...' from the File menu. Select your 'Default' configuration and click the 'Duplicate...' button. Enter 'IP Masq' (or something to let you know that this is a special configuration) in the 'Duplicate Configuration' dialog, it will probably say something like 'Default copy'. Then click the 'OK' button, and the 'Make Active' button

4. Select 'Ethernet' from the 'Connect via:' pop-up.

5. Select the appropriate item from the 'Configure:' pop-up. If you don't know which option to choose, you probably should re-select your 'Default' configuration and quit. I use 'Manually'.

6. Enter the IP address of your Mac (192.168.0.x, 1 < x < 255) in the 'IP Address:' box.

7. Enter 255.255.255.0 in the 'Subnet mask:' box.

8. Enter 192.168.0.1 in the 'Router address:' box.

9. Enter the IP addresses of your domain name servers in the 'Name server addr.:' box.

10. Enter the name of your Internet domain (e.g. 'microsoft.com') in the 'Starting domain name' box under 'Implicit Search Path:'.

11. The following procedures are optional. Incorrect values may cause erratic behavior. If you're not sure, it's probably better to leave them blank, unchecked and/or un-selected. Remove any information from those fields, if necessary. As far as I know there is no way through the TCP/IP dialogs, to tell the system not to use a previously select alternate "Hosts" file. If you know, I would be interested.

    Check the '802.3' if your network requires 802.3 frame types.

12. Click the 'Options...' button to make sure that the TCP/IP is active. I use the 'Load only when needed' option. If you run and quit TCP/IP applications many times without rebooting your machine, you may find that unchecking the 'Load only when needed' option will prevent/reduce the effects on your machines memory management. With the item unchecked the TCP/IP protocol stacks are always loaded and available for use. If checked, the TCP/IP stacks are automatically loaded when needed and un-loaded when not. It's the loading and unloading process that can cause your machines memory to become fragmented.

13. You may ping the Linux box to test the network connection. If you have the freeware program MacTCP Watcher, click on the 'Ping' button, and enter the address of your Linux box (192.168.0.1) in the dialog box that pops up. (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

14. You can optionally create a Hosts file in your System Folder so that you can use the hostnames of the machines on your LAN. The file may or may not already exist in your System Folder. If so, it should contain some (commented-out) sample entries which you can modify according to your needs. If not, you can get a copy of the file from a system running MacTCP, or just create your own (it follows a subset of the Unix /etc/hosts file format, described on RFC952). Once you've created the file, open the TCP/IP control panel, click on the 'Select Hosts File...' button, and open the Hosts file.

15. Click the close box or choose 'Close' or 'Quit' from the File menu, and then click the 'Save' button to save the changes you have made.

16. The changes take effect immediately, but rebooting the system won't hurt.

4.8 Configuring Novell network using DNS

1. If you haven't installed the appropriate driver software for your Ethernet adapter, do so now. Description of this is beyond the scope of this document.

2. Downloaded tcpip16.exe from The Novell LanWorkPlace page

3. edit c:\nwclient\startnet.bat
   

   : (here is a copy of mine)

   SET NWLANGUAGE=ENGLISH
   LH LSL.COM
   LH KTC2000.COM
   LH IPXODI.COM
   LH tcpip
   LH VLM.EXE
   F:
   

4. edit c:\nwclient\net.cfg
   

   : (change link driver to yours i.e. NE2000)

   Link Driver KTC2000
           Protocol IPX 0 ETHERNET_802.3    
           Frame ETHERNET_802.3     
           Frame Ethernet_II        
           FRAME Ethernet_802.2
   
   NetWare DOS Requester
              FIRST NETWORK DRIVE = F
              USE DEFAULTS = OFF
              VLM = CONN.VLM
              VLM = IPXNCP.VLM
              VLM = TRAN.VLM
              VLM = SECURITY.VLM
              VLM = NDS.VLM
              VLM = BIND.VLM
              VLM = NWP.VLM
              VLM = FIO.VLM
              VLM = GENERAL.VLM
              VLM = REDIR.VLM
              VLM = PRINT.VLM
              VLM = NETX.VLM
   
   Link Support
           Buffers 8 1500
           MemPool 4096
   
   Protocol TCPIP
           PATH SCRIPT     C:\NET\SCRIPT
           PATH PROFILE    C:\NET\PROFILE
           PATH LWP_CFG    C:\NET\HSTACC
           PATH TCP_CFG    C:\NET\TCP
           ip_address      192.168.0.xxx
           ip_router       192.168.0.1
   

   Change the IP address in the above "ip_address" field (192.168.0.x, 1 < x < 255) 
   and finally create c:\bin\resolv.cfg:
   
   SEARCH DNS HOSTS SEQUENTIAL
   NAMESERVER xxx.xxx.xxx.xxx
   NAMESERVER yyy.yyy.yyy.yyy
   

5. Now edit the above "NAMESERVER" entries and replace them with the correct IP addresses for your local DNS server.

6. Issue a ping command: ping 192.168.0.1 to test the connection to your gateway machine.
   (This is only an INTERNAL LAN connection test, you can't ping the outside world yet.) If you don't see "replies" to your PINGs, please verify your network configuration.

4.9 Configuring OS/2 Warp

1. If you haven't installed the appropriate driver software for your Ethernet adapter, do so now. Description of this is beyond the scope of this document.

2. Install the TCP/IP protocol if you don't have it already.

3. Go to Programs/TCP/IP (LAN) / TCP/IP Settings

4. In 'Network' add your TCP/IP Address (192.168.0.x) and set your netmask (255.255.255.0)

5. Under 'Routing' press 'Add'. Set the Type to 'default' and type the IP Address of your Linux Box in the Field 'Router Address'. (192.168.0.1).

6. Set the same DNS (Nameserver) Address that your Linux host uses in 'Hosts'.

7. Close the TCP/IP control panel. Say yes to the following question(s).

8. Reboot your system

9. You may ping the Linux box to test the network configuration. Type 'ping 192.168.0.1' in a 'OS/2 Command prompt Window'. When ping packets are received all is ok.

4.10 Configuring OS/400 on a IBM AS/400

The description of how to configure TCP/IP on OS/400 version V4R1M0 running on a AS/400 is beyond the scope of this document.

1) To perform any communications configuration tasks on your AS/400, you must have the special authority of *IOSYSCFG (I/O System Configuration) defined in your user profile. You can check the characteristics of your user profile with the DSPUSRPRF command.

2) Type GO CFGTCP command th reach the Configure TCP/IP menu.

3) Select Option 2 - Work with TCP/IP Routes.

4) Enter a 1 on the Opt field to add a route. * In Route Destination type *DFTROUTE * In Subnet Mask type *NONE * In Type of Service type *NORMAL * In Nex Hop type the address of your gataway (the Linux box)

4.11 Configuring Other Systems

The same logic should apply to setting up other platforms. Consult the sections above. If you're interested in writing about any of systems that have not been covered yet, please send a detail setup instruction to ambrose@writeme.com and dranch@trinnet.net.