Router - ArchWiki

Jump to content
Toggle the table of contents

# Router

2 languages

- 日本語
- 中文（简体）

From ArchWiki

This article is a tutorial for turning a computer into an internet gateway/router. To strengthen its security it should not run any services available to the outside world. Towards the LAN, run only gateway specific services; especially do not run httpd, ftpd, samba, nfsd, etc. as those belong on a server in the LAN since they introduce security risks.

This article does not attempt to show how to set up a shared connection between two machines using cross-over cables. For a simple internet sharing solution, see Internet sharing.

Note: Throughout the article, intern0 and extern0 are used as names for the network interfaces. The reasoning is further explained in #Persistent interface naming.

## Hardware Requirements

- 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 (actually a router can be made using a single physical interface that underlays two VLAN interfaces and is connected to a VLAN-aware switch, so-called router-on-a-stick configuration, but it is not covered in this article). 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

## Network interface configuration

### Persistent interface naming

systemd automatically chooses unique interface names for all your interfaces. These are persistent and will not change when you reboot. However you might want to rename your interfaces e.g. in order to highlight their different networks to which they connect. Throughout the following sections of this guide, the convention stated below is used:

- intern0: the network card connected to the LAN. On an actual computer it will probably have the name enp2s0, enp1s1, etc.
- extern0: the network card connected to the external network (or WAN). It will probably have the name enp2s0, enp1s1, etc.

You may change the assigned names of your devices by following Network configuration#Change interface name. Due to the example-rich nature of this article, you might want to choose the names above.

### IP configuration

#### With netctl

Now you will need to configure the network interfaces. One way to do so, is using netctl profiles. You will need to create two profiles.

Note: If you will be connecting to the Internet only via PPPoE (you have one WAN port) you do not need to setup or enable the extern0-profile. See below for more information on configuring PPPoE.

    /etc/netctl/extern0-profile

    Description='Public Interface.'
    Interface=extern0
    Connection=ethernet
    IP='dhcp'

    /etc/netctl/intern0-profile

    Description='Private Interface'
    Interface=intern0
    Connection=ethernet
    IP='static'
    Address=('10.0.0.1/24')

Note: The example configuration above assumes a full subnet. If you are building the gateway for a small amount of people, you will want to change the CIDR suffix to accommodate a smaller range. For example `/27` will give you `10.0.0.1` to `10.0.0.30`. There are many CIDR calculators, online and offline, for example sipcalc.
Tip: Use `SkipNoCarrier=yes` in the LAN profile to make sure the connection is enabled even when the guest on LAN is not yet up.

Next, we set up the interfaces with netctl:

    # netctl enable extern0-profile
    # netctl enable intern0-profile

#### With systemd-networkd

A straight-forward and simple way to configure network interfaces is via systemd-networkd.

- Apply a DHCP client configuration for the `extern0` interface.
- Apply a static IP configuration for the `intern0` interface.

See systemd-networkd#Configuration files for configuration details and an overview of the available options. Run `networkctl reload` to apply the configuration changes.

### ADSL connection/PPPoE

Using rp-pppoe, we can connect an ADSL modem to the `extern0` interface of the firewall and have Arch manage the connection. Make sure to put the modem in bridged mode though (either half-bridge or RFC1483), otherwise, the modem will act as a router too. Install the rp-pppoe package.

It should be noted that if you use only PPPoE to connect to the internet (i.e. you do not have another WAN port, except for the one that connects to your modem) you do not need to set up the `extern0-profile` as the external pseudo-interface will be ppp0.

#### PPPoE configuration

You can use netctl to setup the PPPoE connection. To get started, do

    # cp /etc/netctl/examples/pppoe /etc/netctl/

and start editing. For the interface configuration, choose the interface that connects to the modem. If you only connect to the internet through PPPoE, this will probably be `extern0`. Fill in the rest of the fields with your ISP information. See the PPPoE section in the netctl.profile(5) man page for more information on the fields.

## DNS and DHCP

The following comparison table lists the available DHCP servers and their features:

Server | DHCPv4 | DHCPv6 | IPv6 Router Advertisement | GUI | Interfaces | Storage backend(s) | Note
--- | --- | --- | --- | --- | --- | --- | ---
dhcpd | Yes | Yes | No | Glass-ISC-DHCP | ? | File | Superseded by Kea.
dnsmasq | Yes | Yes | Yes | No | ? | File | Also DNS, PXE and TFTP.
kea | Yes | Yes | No | Stork | REST, RADIUS, NETCONF | File, MySQL, PostgreSQL, Cassandra | Also DNS. Supersedes dhcpd.
systemd-networkd | Yes | No | Yes | No | ? | File | Installed with systemd.

A comparison of available DNS servers can be found in Domain name resolution#DNS servers.

### dnsmasq

To use dnsmasq as DNS server, and optionally DHCP server, for the LAN, install the dnsmasq package.

The default configuration already enables its DNS server, see Dnsmasq#Configuration for options.

For this router example, dnsmasq can to be configured to be a DHCP server with a configuration similar to the following:

    /etc/dnsmasq.conf

    interface=intern0 # make dnsmasq listen for requests only on intern0 (our LAN)
    #no-dhcp-interface=intern0  # optionally disable the DHCP functionality of dnsmasq and use systemd-networkd instead
    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 .255 with a subnet mask of 255.255.255.0 and a
                      # DHCP lease of 1 hour (change to your own preferences)

See Dnsmasq#DHCP server for other options. For example, 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 MACs from obtaining an IP.

Now start and enable the `dnsmasq.service`.

### systemd-networkd

To use systemd-networkd instead of dnsmasq as DHCP server, add a `[DHCPServer]` section to the configuration file for the `intern0` interface. See systemd-networkd#[DHCPServer] for the available options.

To make systemd-resolved answer DNS requests on the routers interfaces, their addresses have to be added as described in systemd-resolved#Additional listening interfaces.

## Connection sharing

Time to tie the two network interfaces together.

### Manual

First of all, we need to allow packets to hop from one network interface to the other. For this one needs to have packet forwarding enabled in kernel via sysctl(8). See Internet sharing#Enable packet forwarding for details.

Assuming `net.**forwarding` is set correctly (i.e. is `1`), packets still need to be properly sent and received. Hence, it is necessary to translate the IP addresses between the outward facing network and the subnet used locally. The technique is called masquerading . We also need two forwarding rules to keep connections going and enable LAN to WAN forwarding. For this task, we are going to use iptables.

Refer to the section Internet sharing#Enable NAT for how to masquerade the `extern0` interface and packages from `intern0` to `extern0`. Afterwards persist the newly added rules via `iptables-save -f /etc/iptables/iptables.rules`, see iptables#Configuration and usage for details.

Start and enable `iptables.service`. The router should now be fully functional and route your traffic. Since it is facing the public Internet, it makes sense to additionally secure it using a Simple stateful firewall.

### With systemd-networkd

Amend or create the previously discussed network configuration for `intern0` to include the `IPMasquerade=ipv4` option in the `[Network]` section. This configuration will implicitly enable packet forwarding on all interfaces, see systemd.network(5). See systemd-networkd#[DHCPServer] for an example configuration.

### Connection sharing with shorewall

See Shorewall for a detailed configuration guide.

## IPv6 tips

This article or section is a candidate for merging with IPv6.

Notes: Merge into the main article, the topic is not specific to router configuration. The wording should be probably changed along the way. (Discuss in Talk:Router)

Useful reading: IPv6 and the wikipedia:IPv6.

### Unique Local Addresses

You can use your router in IPv6 mode even if you do not have an IPv6 address from your ISP. Unless you disable IPv6, all interfaces should have been assigned a unique `fe80::/10` address.

This article or section needs expansion.

Reason: Add an offline method to generate an ULA. (Discuss in Talk:Router)

For internal networking the block `fc00::/7` has been reserved. These addresses are guaranteed to be unique and non-routable from the open Internet. Addresses that belong to the `fc00::/7` block are called Unique Local Addresses. To get started generate a ULA /64 block to use in your network. For this example we will use `fd00:aaaa:bbbb:cccc::/64`. Firstly, we must assign a static IPv6 on the internal interface. Modify the `intern0-profile` we created above to include the following line:

     Address6=('fd00:aaaa:bbbb:cccc::1/64')

This will add the ULA to the internal interface. As far as the router goes, this is all you need to configure.

### Global Unicast Addresses

If your ISP or WAN network can access the IPv6 Internet, you can additionally assign global link addresses to your router and propagate them through SLAAC to your internal network. The global unicast prefix is usually either static or provided through prefix delegation.

#### Static IPv6 prefix

If your ISP has provided you with a static prefix, then edit `/etc/netctl/extern0-profile` and simply add the IPv6 and the IPv6 prefix (usually /64) you have been provided

     Address6=('2002:1:2:3:4:5:6:7/64')

You can use this in addition to the ULA address described above.

#### Acquiring IPv6 prefix via DHCPv6-PD

If your ISP handles IPv6 via prefix delegation, then you can follow the instructions in the IPv6#Prefix delegation (DHCPv6-PD) on how to properly configure your router. Following the conventions of this article, the WAN interface is `extern0` (or `ppp0` if you are connecting through PPPoE) and the LAN interface is `intern0`.

### Router Advertisement and Stateless Autoconfiguration (SLAAC)

To properly hand out IPv6s to the network clients, we will need to use an advertising daemon. Follow the details of the main IPv6 article on how to set up `radvd`. According to this guide's convention, the LAN-facing interface is `intern0`. You can either advertise all prefixes or choose which prefixes will be assigned to the local network.

## Optional additions

### UPnP

This article or section needs expansion.

Reason: Mention the alternative port forwarding protocol NAT-PMP, that is supported by miniupnpd. (Discuss in Talk:Router)

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 require this to function correctly.

To enable UPnP on your router, you need to install an UPnP Internet Gateway Device (IGD) protocol daemon. To get it, install the miniupnpd package.

Read the Shorewall guide on UPnP for more information.

### Remote administration

OpenSSH can be used to administer your router remotely. This is useful for running it in headless mode (no monitor or input devices).

### Caching web proxy

See Squid for the setup of a web proxy to speed up browsing and/or adding an extra layer of security.

### Time server

To use the router as a time server, see System time#Time synchronization for available Network Time Protocol (NTP) server implementations.

Then, configure shorewall or iptables to allow NTP traffic in and out.

### Content filtering

Install and configure Privoxy if you need a content filtering solution.

### Traffic shaping

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

See Shorewall#Traffic shaping.

## See also

- Simple stateful firewall
- Internet sharing

Categories:

- Network sharing
- Security
- Firewalls

Hidden categories:

- Pages or sections flagged with Template:Merge
- Pages or sections flagged with Template:Expansion