Linux IP Masquerade HOWTO
November 13, 2005
This document describes how to enable the Linux IP Masquerade feature on a given Linux host. IP Masquerade is a form of Network Address Translation or NAT which NAT allows internally connected computers that do not have one or more registered Internet IP addresses to communicate to the Internet via the Linux server's Internet IP address.
- Table of Contents
- 1. Introduction
- 1.1. Introduction to IP Masquerading or IP MASQ
- 1.2. Foreword, Feedback & Credits
- 1.3. Copyright & Disclaimer
- 2. Background Knowledge
- 2.1. What is IP Masquerade?
- 2.2. Current Status
- 2.3. Who Can Benefit From IP Masquerade?
- 2.4. Who Doesn't Need IP Masquerade?
- 2.5. How does IP Masquerade Work?
- 2.6. Requirements for IP Masquerade on Linux 2.4.x
- 2.7. Requirements for IP Masquerade on Linux 2.2.x
- 2.8. Requirements for IP Masquerade on Linux 2.0.x
- 3. Setting Up IP Masquerade
- 3.1. Compiling a new kernel if needed
- 3.2. Checking your existing kernel for MASQ functionality
- 3.2.1. Compiling Linux 2.4.x Kernels
- 3.2.2. Compiling Linux 2.2.x Kernels
- 3.2.3. Compiling Linux 2.0.x Kernels
- 3.3. Assigning Private Network IP Addresses to the Internal LAN
- 3.4. Configuring IP Forwarding Policies
- 4. Configuring the other internal to-be MASQed machines
- 4.1. Configuring Microsoft Windows 95 and OSR2
- 4.2. Configuring Windows NT
- 4.3. Configuring Windows for Workgroup 3.11
- 4.4. Configuring UNIX Based Systems
- 4.5. Configuring DOS using NCSA Telnet package
- 4.6. Configuring MacOS Based System Running MacTCP
- 4.7. Configuring MacOS Based System Running Open Transport
- 4.8. Configuring Novell network using DNS
- 4.9. Configuring OS/2 Warp
- 4.10. Configuring OS/400 on a IBM AS/400
- 4.11. Configuring Other Systems
- 5. Testing IP Masquerade
- 5.1. Loading up the rc.firewall ruleset
- 5.2. Testing internal MASQ client PC connectivity
- 5.3. Testing internal MASQ client to MASQ server connectivity
- 5.4. Testing internal MASQ server connectivity
- 5.5. Testing internal MASQ server to MASQ client connectivity
- 5.6. Testing External MASQ server Internet connectivity
- 5.7. Testing internal MASQ client to external MASQ server connectivity
- 5.8. Testing external MASQ ICMP forwarding
- 5.9. Testing MASQ functionality without DNS
- 5.10. Testing MASQ functionality with DNS resolution
- 5.11. Testing more MASQ functionality with DNS
- 5.12. Any remaining functional, performance, etc. issues...
- 6. Other IP Masquerade Issues and Software Support
- 6.1. Problems with IP Masquerade
- 6.2. Incoming services
- 6.3. Supported Client Software and Other Setup Notes
- 6.3.1. Network Clients that -Work- with IP Masquerade
- 6.3.2. Clients that do not have full support in IP MASQ:
- 6.4. Stronger firewall rulesets to run after initial testing
- 6.4.1. Stronger IP Firewall (IPTABLES) rulesets
- 6.4.2. Stronger IP Firewall (IPCHAINS) rulesets
- 6.4.3. Stronger IP Firewall (IPFWADM) Rulesets
- 6.5. IP Masquerading multiple internal networks
- 6.5.1. iptables support for multiple internal lans
- 6.5.2. ipchains support for multiple internal lans
- 6.5.3. ipfwadm support for multiple internal lans
- 6.6. IP Masquerade and Dial-on-Demand Connections
- 6.7. Port Forwarding with IPTABLES or external tools like IPPORTFW, IPMASQADM, IPAUTOFW, REDIR, UDPRED, and other Port Forwarding tools
- 6.7.1. IPTABLES-based PORTFWD'ing: Using IPTABLES's PREROUTING option for 2.6.x and 2.4.x kernels
- 6.7.2. IPMASQADM-based PORTFWD'ing: Using IPMASQADM with 2.2.x kernels
- 6.7.3. IPPORTFW-based PORTFWD'ing: Using IPPORTFW on 2.0.x kernels
- 6.8. CU-SeeMe and Linux IP-Masquerade
- 6.9. Mirabilis ICQ
- 6.10. Gamers: The LooseUDP patch
* License
