This article is a tutorial for turning a computer into an internet gateway/router. It focuses on security, since the gateway is connected directly to the Internet. It should not run any services available to the outside world. Towards the LAN, it should only run gateway specific services. It should not run httpd, ftpd, samba, nfsd, etc. as those belong on a server in the LAN as they introduce security flaws.
This article does not attempt to show how to set up a shared connection between 2 PCs using cross-over cables. For a simple internet sharing solution, see Internet Share.
- 1 Hardware Requirements
- 2 Conventions
- 3 Installation
- 4 Network interface configuration
- 5 ADSL connection
- 6 DNS and DHCP
- 7 Connection sharing
- 8 Cleanup
- 9 Logrotate
- 10 Optional additions
- 11 See also
- At least 1 GB of hard drive space. The base install will take up around 500MB of space and if you want to use a caching web proxy, you will need to reserve space for the cache as well.
- At least two physical network interfaces: a gateway connects two networks with each other. You will need to be able to connect those networks to the same physical computer. One interface must connect to the external network, while the other connects to the internal network.
- A hub, switch or UTP cable: You need a way to connect the other computers to the gateway
Conventions in this guide will be to use non-realistic interface names, to avoid confusion about which interface is which.
- intern0: the network card connected to the LAN. On an actual computer it will probably have the name eth0, eth1, etc.
- extern1: the network card connected to the external network (or WAN). It will probably have the name eth0, eth1, etc.
A fresh install of Arch Linux is the easiest to start from, as no configuration changes have been made and there is a minimal amount of packages installed. This is helpful when attempting to reduce security risk.
For security purposes, /var, /tmp and /home should be separate from the / partition. This prevents disk space from being completely used up by log files, daemons or the unprivileged user. It also allows different mount options for those partitions. If you have already partitioned your drive, the gparted livecd can be used to resize, move, or create new partitions.
Your home and root partitions can be much smaller than a regular install since this is not a desktop machine. /var should be the largest partition - it is where databases, logs and long-term caches are stored. If you have a lot of RAM, mounting /tmp as tmpfs is a good idea, so making a disk partition for it during the initial install is unnecessary.
After installation boot Arch and upgrade all the packages to their latest version:
# pacman -Syu
# pacman -S sudo
Now, add a normal user. Be sure to add the user to the wheel group. This will allow the user to use sudo. Logging in as root is unsafe, it is much better to use sudo.
After sudo is installed and configured, it is possible to lock to root account and prevent login directly to root.
# passwd -l root
Network interface configuration
When you let udev handle loading the modules, you will notice your NIC's switch names: one boot your LAN NIC is eth0, the other boot it is eth1.
To fix this problem, see here.
CONNECTION='ethernet' DESCRIPTION='Public Interface.' INTERFACE='extern0' IP='dhcp'
CONNECTION='ethernet' DESCRIPTION='Private Interface.' INTERFACE='intern0' IP='static' ADDR='10.0.0.1' NETMASK='255.255.255.0' BROADCAST='10.0.0.255'
Next up is to set up the interfaces in /etc/rc.conf.
- Define the profiles
- Replace the "network" daemon with the netcfg one: "net-profiles"
DAEMONS=( ... net-profiles ... )
Using rp-pppoe, we can connect an ADSL modem to the extern1 of the firewall and have Arch manage the connection. Make sure you put the modem in bridged mode though, otherwise the modem will act as a router too.
# pacman -S rp-pppoe
The questions are all documented. You can select "no firewall" because we will let Shorewall / iptables handle that part.
DNS and DHCP
We will use dnsmasq, a DNS and DHCP daemon for the LAN. It was specifically designed for small sites.
First, install dnsmasq:
# pacman -S dnsmasq
Now, dnsmasq needs to be configured. To do this:
Edit /etc/dnsmasq.conf and add the following lines
interface=intern1 # make dnsmasq listen for requests only on intern1 (our LAN) expand-hosts # add a domain to simple hostnames in /etc/hosts domain=foo.bar # allow fully qualified domain names for DHCP hosts (needed when # "expand-hosts" is used) dhcp-range=10.0.0.2,10.0.0.255,255.255.255.0,1h # defines a DHCP-range for the LAN: # from 10.0.0.2 to .14 with a subnet mask of 255.255.255.240 and a # DHCP lease of 1 hour (change to your own preferences)
Somewhere below, you will notice you can also add "static" DHCP leases, i.e. assign an IP-address to the MAC-address of a computer on the LAN. This way, whenever the computer requests a new lease, it will get the same IP. That is very useful for network servers with a DNS record. You can also deny certain MAC's from getting an IP. Evil!! ^_^ Now start dnsmasq
# /etc/rc.d/dnsmasq start
and add the daemon to the DAEMONS list in /etc/rc.conf.
Time to tie the two network interfaces to each other.
Shorewall, an iptables frontend, can be used as an easier alternative.
# pacman -S shorewall
Time to configure Shorewall! Open its config file in /etc/shorewall/shorewall.conf and start editing. The file is very well documented.
SUBSYSLOCK=/var/run IP_FORWARDING=On : it is a gateway, remember! ;) STARTUP_ENABLED=Yes # when you are done editing
After installing shorewall, run
$ pacman -Ql shorewall | grep Sample
to see where the sample files are. cd into the directory "two-interfaces" and copy the contents to the /etc/shorewall/ directory. Now use Shorewall's guide to set up the files correctly.
Read the document carefully. Take special care to change eth0 and eth1 (or ppp0 in if you are using PPPoE where appropriate in your config files as the Shorewall guide uses different names for the interfaces. When you have followed it thoroughly, make the following changes:
- /etc/shorewall/interfaces : add "dhcp" to the loc line to allow computers on the LAN to make use of our DHCP server
- /etc/shorewall/rules : add
ACCEPT loc $FW TCP 2367
but change 2367 into whatever port you have your SSH server listening on.
# /etc/rc.d/shorewall start
From here on, the Arch box is operational. Connect a hub or switch to intern0 and a computer to the LAN to test it.
Port forwarding (DNAT)
- /etc/shorewall/rules : here is an example for a webserver on our LAN with IP 10.0.0.85. You can reach it on port 5000 of our "external" IP.
DNAT net loc:10.0.0.85:80 tcp 5000
Now that the installation has been performed, it is necessary to remove as many packages as possible. Since we are making a gateway, keeping unneeded packages only "bloats" the system, and increases the number of security risks.
First, check for obsolete/deprecated packages (likely after a fresh install and massive series of updates):
$ pacman -Qm
Review the list of explicitly installed packages that are not dependencies and remove any that are unneeded. Having only needed packages installed is an important security consideration.
$ pacman -Qet
Completely remove the packages you do not need along with their configuration files and dependencies:
# pacman -Rsn package1 package2 package3
You should review the logrotate configuration to make sure the box is not brought down by lack of diskspace due to logging.
Logrotate is installed by default, so you will not have to install it.
The above configuration of shorewall does not include UPnP support. Use of UPnP is discouraged as it may make the gateway vulnerable to attacks from within the LAN. However, some applications such as MSN require this to function correctly.
Read the Shorewall guide on UPnP for more information
OpenSSH can be used to administer your router remotely. This is useful for running it "headless" (no monitor or input devices).
Caching web proxy
To use the router as a time server, see Network Time Protocol.
Then, configure shorewall or iptables to allow NTP traffic in and out.
Install and configure DansGuardian if you need a content filtering solution.
Traffic shaping is very useful, especially when you are not the only one on the LAN. The idea is to assign a priority to different types of traffic. Interactive traffic (ssh, online gaming) probably needs the highest priority, while P2P traffic can do with the lowest. Then there is everything in between.
Traffic shaping with shorewall
Read Shorewall's Traffic Shaping/Control guide.
Here is my config as an example:
- /etc/shorewall/tcdevices : here is where you define the interface you want to have shaped and its rates. I have got a ADSL connection with a 4MBit down/256KBit up profile.
ppp0 4mbit 256kbit
- /etc/shorewall/tcclasses : here you define the minimum (rate) and maximum (ceil) throughput per class. You will assign each one to a type of traffic to shape.
# interactive traffic (ssh) ppp0 1 full full 0 # online gaming ppp0 2 full/2 full 5 # http ppp0 3 full/4 full 10 # rest ppp0 4 full/6 full 15 default
- /etc/shorewall/tcrules : this file contains the types of traffic and the class it belongs to.
1 0.0.0.0/0 0.0.0.0/0 tcp ssh 2 0.0.0.0/0 0.0.0.0/0 udp 27000:28000 3 0.0.0.0/0 0.0.0.0/0 tcp http 3 0.0.0.0/0 0.0.0.0/0 tcp https 4 0.0.0.0/0 0.0.0.0/0 all
I have split it up my traffic in 4 groups:
- interactive traffic or ssh: although it takes up almost no bandwidth, it is very annoying if it lags due to leechers on the LAN. This get the highest priority.
- online gaming: needless to say you ca not play when your ping sucks. ;)
- webtraffic: can be a bit slower
- everything else: every sort of download, they are the cause of the lag anyway.
Intrusion detection and prevention with snort