Setting Up a Linux Gateway

Setting up a Linux gateway can be a rewarding experience in both home and commercial environments.

Networks are extremely common these days—you see them in businesses, schools, even homes. Networking is popular because it allows users to share resources. You can share files, printers and a myriad of other devices in a network. Now, wouldn't it be great if you could share an Internet connection? With Linux, you can.

Setting up Linux as an Internet gateway is not difficult to do. A Linux gateway allows two or more computers to use the Internet at the same time. While doing so, only the gateway's IP address will be visible on the Internet. The rest of the computers will be “hidden” behind the gateway. This is called IP masquerading.

What can you do with this setup? Well, if you have four computers connected to the gateway, you can surf the Web from any of the four computers at the same time. You can run telnet sessions, go on IRC (Internet relay chat), read newsgroups, etc.—almost anything you can do on the Internet can be done. Of course, there are certain things that may need your attention, and I will discuss them as well as setting up both Linux and Windows machines to use the gateway.

What You Need

First of all, you need a working TCP/IP network. I assume your network is up and running, and all your machines are able to “see” each other.

I will discuss setting up IP masquerading using Linux kernel 2.2.x and ipchains 1.3.x. If for some reason you are running an early kernel such as 1.x.x, please refer to Chris Kostick's articles on IP masquerading in issues 27 and 43 of Linux Journal.

Also, please make sure you have a copy of the Linux IP Masquerade mini HOWTO ( by Ambrose Au and David Ranch. It contains much more detailed information on setting up IP masquerading, including setting up Macintosh and Windows NT clients. It also contains a useful FAQ should you run into problems. This article is based on that mini HOWTO as well as personal experience.

I also assume you are familiar with basic Linux system administration, and that you know how to recompile your kernel and modify your init scripts.

What Do You Want to Do?

The next thing to figure out is what you want to do. How many machines are on the network? Which machine do you wish to set up as the gateway? Which machines will be the clients? What operating system is each machine running? The answers to these questions can be complex and unique, so for the purposes of this article, we will use the setup shown in Figure 1. This is a three-node network with a Linux gateway (antioch), a Linux client (nazareth) and a Windows 95 client (lystra).

Figure 1. Gateway Setup

Setting Up the Gateway

Let's start by setting up the gateway, which in our case is antioch ( Antioch runs Linux 2.2.x, and in order for it to become a gateway, we need to turn on certain kernel options. My gateway has the kernel options shown in Table 1 turned on.

Table 1

After booting our newly compiled kernel, we will have to load a few kernel modules using either insmod or modprobe:

/sbin/insmod ip_masq_user
/sbin/insmod ip_masq_raudio
/sbin/insmod ip_masq_ftp
/sbin/insmod ip_masq_irc

It would be wise to add these lines into one of your init scripts so they will run on every startup. There are other kernel modules related to IP masquerading; for a full list, type the command

/sbin/modprobe -l | grep ip_masq
Linux 2.2 does not turn on IP forwarding by default. To find out whether IP forwarding is switched on, check the contents of the file /proc/sys/net/ipv4/ip_forward. If it is 0, IP forwarding is off; if 1, it is on.
# cat /proc/sys/net/ipv4/ip_forward
# echo "1" > /proc/sys/net/ipv4/ip_forward
# cat /proc/sys/net/ipv4/ip_forward
Again, it is wise to add the line which turns on IP forwarding (the one with the echo command) to one of your init scripts.

Now we come to an interesting situation. How do we know who gets to use the gateway and who doesn't? This is where ipchains comes in. My current policy is to deny access to the gateway from everybody unless explicitly allowed. For example, let's say we want only our client machines nazareth and lystra to access our gateway and no one else. In order to do this, we have to issue the following commands:

ipchains -P forward DENY
ipchains -A forward -s\
  -j MASQ
ipchains -A forward -s\
  -j MASQ

If, on the other hand, we want everybody on the network 192.168.0.* to use the gateway, we can issue these commands:

ipchains -P forward DENY
ipchains -A forward -s\
  -j MASQ
Note that we assume the netmask is If your netmask is different, simply change the values accordingly. There are many other things you can do with ipchains; however, they are beyond the scope of this article. I trust that the two simple examples above will get you started. (See also “Building a Firewall with IP Chains” by Pedro Bueno,

That's it! The gateway is now up and running. Remember to add the relevant lines to the startup scripts. Also remember to connect to the Internet before testing your gateway. Now let's set up the clients.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

File upload problem

Omar Faruk's picture

I have configured a Linux gateway and all internet connectivity(download) is okey from client pc but problem is file upload or file attached from client pc.Suppose if I want to attach a file in my gmail but I can not attached. And no error message shown whats the problem??? Please give me an solution....

Setting Up a Linux Gateway

Josh's picture

Great! Also refer the following URL for more details.

Good Article

Rajesh's picture

This is an amazing article,well done lawrence,do post good articles

Update on this info

Rommel's picture

I know this article is several years old now. But if the author or anybody who still reads this, kindly point me to an updated site. I'm using ubuntu and would appreciate any help to set it up as an internet gateway.


Easy gateway/firewall setup for Ubuntu

UbuntuLANman's picture

It's still a good article!

I just got an Ubuntu 6.10 machine configured as a gateway! After perusing the net for a bit, I found out about the firehol package that sets up an iptables-based firewall. Here are the steps I followed to configure my machine:

  1. Install the firehol package. I used synaptic from the menu (Applications => System => Synaptic Package Manager). Simply search for "firehol", mark it for installation, and Apply.
  2. Edit the /etc/firehol/firehol.conf configuration file. See below for the configuration I used.
  3. Edit the /etc/default/firehol file to enable the firewall to come up at boot time and to wait until all necessary network interfaces are up first.
  4. Start the firewall with the firehol start command.
  5. Your LAN machines will need to know how to reach the Internet through your new gateway machine. You can either set up a DHCP server on your gateway, or manually configure each machine on the LAN with a static route. (Since I only have a couple of machines on my LAN, I just manually configured them.)
  6. Your LAN machines will also need to know how to resolve domain names to IP addresses. If you set up your gateway as a DHCP server, it will pass through the nameservers it uses to each LAN machine. Otherwise, you'll need to edit each LAN machine's /etc/resolv.conf file.

That's it!

You should test your setup with the following steps. If any one of these steps doesn't work, check your configuration files and get it working before proceeding to the next step.

  1. From your newly configured gateway, make sure you can ping a non-stealthed network address such as Make a note of the IP address ( was when I wrote this).
  2. From your gateway, make sure you can ping all the machines on your LAN.
  3. Make sure that you can ping the gateway from each of the machines on your LAN.
  4. From each machine on your LAN, make sure you can ping the network IP address you wrote down in the first test. (DNS may not be working yet, so avoid domain names at this point.)
  5. From each machine on your LAN, make sure domain names get resolved correctly. You can use the host command for this. Try the domain name you used in the first step, and try pinging it too.


If all five steps worked, your should have a fully working gateway and LAN! To REALLY make sure, reboot your firewall and use the firehol status command to verify the firewall is running.

Here is the /etc/firehol/firehol.conf file I used:

interface eth0 INET
policy drop
protection strong
client all accept
interface eth1 LAN
policy accept
router LAN_2_INET inface eth1 outface eth0
route all accept

In my setup, "eth0" is the interface that connects the gateway to my ISP, and "eth1" is the interface that connects the gateway to my LAN.

Here is my /etc/default/firehol file:

#If you want to have firehol wait for an iface to be up add it here

In my /etc/network/interfaces file, the interface "eth0" occurs before "eth1", so both interfaces will be active before the firewall gets started at boot time.

This firewall configuration is very basic; it assumes all LAN machines are completely trustworthy, and that there are no services running on the gateway or LAN machines that need to be visible to the internet (such as FTP, SSH, or HTTP). That being said, however, firehol looks like it can handle most situations with ease, and is fairly well documented.

I hope this helps! Please note any corrections needed here (if any).

NOTE: Because firehol is a single bash script, it should work on just about any Gnu/Linux distribution with iptables support. (Your mileage may vary.)

wrong URL

Anonymous's picture

"...Linux IP Masquerade mini HOWTO ( by Ambrose Au and David Ranch..."

wrong URL, but still interesting nevertheless. LOL

Re: wrong URL

Anonymous's picture

omg! .... next time give a warning about that link to those of us at school

Re: Setting Up a Linux Gateway

Anonymous's picture

thx! :)

White Paper
Linux Management with Red Hat Satellite: Measuring Business Impact and ROI

Linux has become a key foundation for supporting today's rapidly growing IT environments. Linux is being used to deploy business applications and databases, trading on its reputation as a low-cost operating environment. For many IT organizations, Linux is a mainstay for deploying Web servers and has evolved from handling basic file, print, and utility workloads to running mission-critical applications and databases, physically, virtually, and in the cloud. As Linux grows in importance in terms of value to the business, managing Linux environments to high standards of service quality — availability, security, and performance — becomes an essential requirement for business success.

Learn More

Sponsored by Red Hat

White Paper
Private PaaS for the Agile Enterprise

If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.

Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.

Learn More

Sponsored by ActiveState