Difference between revisions of "Internet sharing"

From ArchWiki
Jump to: navigation, search
(Enable NAT: fix commands - let's do it right with conntrack, interface names are explained in Internet_Sharing#Configuration)
(Manually adding an ip: merged into resolv.conf)
Line 70: Line 70:
  # ip route add default via dev eth0
  # ip route add default via dev eth0
{{Merge|resolv.conf|The following should be merged there to keep things in one place.}}
Configure a DNS server, see [[resolv.conf]] for details.
Add a nameserver:
# echo "nameserver <nameserver ip>" >> /etc/resolv.conf
You can figure out the address of the nameserver by looking into the {{ic|/etc/resolv.conf}} of the server, if its Internet connection is already established.
If you don't have a nameserver, you can use any of the free public DNS servers, which are relatively fast:
* [https://code.google.com/speed/public-dns/ Google Public DNS]
** [2001:4860:4860::8888]
** [2001:4860:4860::8844]
* [https://opendns.com OpenDNS]:
** [2620:0:ccc::2]
** [2620:0:ccd::2]
{{Note|Bracket notation must be used for IPv6 addresses in resolv.conf.}}
That's it. The client PC should now have Internet.
That's it. The client PC should now have Internet.

Revision as of 11:04, 1 February 2014

This article explains how to share the internet connection from one machine to other(s).


  • The machine acting as server should have an additional network device.
  • That network device should be connected to the machines that are going to receive internet access. They can be one or more machines. To be able to share internet to several machines a switch is required. If you are sharing to only one machine, a crossover cable is sufficient.
Note: If one of the two computers has a gigabit ethernet card, a crossover cable is not necessary and a regular ethernet cable should be enough


This section assumes, that the network device connected to the client computer(s) is named net0 and the network device connected to the internet as internet0.

Tip: You can rename your devices to this scheme using Udev#Setting static device names.

Static IP address

Assign an static IPv4 address to the interface connected to the other machines. The first 3 bytes of this address cannot be exactly the same as those of another interface.

# ip link set up dev net0
# ip addr add dev net0 # arbitrary address

To have your static ip assigned at boot, you can use netctl.

Enable packet forwarding

Check the current packet forwarding settings;

# sysctl -a | grep forward

Enter this command to temporarily enable packet forwarding:

# sysctl net.ipv4.ip_forward=1

Edit /etc/sysctl.d/30-ipforward.conf to make the previous change persistent after a reboot.


Enable NAT

Install the package iptables from the official repositories. Use iptables to enable NAT:

# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE
# iptables -A FORWARD -i net0 -o internet0 -j ACCEPT
# iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
Note: Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1).

Read the iptables article for more information (especially saving the rule and applying it automatically on boot). There is also an excellent guide on iptables Simple Stateful Firewall.

Assigning ip addresses to the client pc(s)

If you are planning to regularly have several machines using the internet shared by this machine, then is a good idea to install a dhcp server.

You can read the dhcpd wiki article, to add a dhcp server. Then, install the dhcpcd client on every client pc.

If you are not planing to use this setup regularly, you can manually add an ip to each client instead.

Manually adding an ip

Instead of using dhcp, on each client pc, add an ip address and the default route:

# ip addr add dev eth0
# ip link set up dev eth0
# ip route add default via dev eth0

Configure a DNS server, see resolv.conf for details.

That's it. The client PC should now have Internet.


If you are able to connect the two PCs but cannot send data (for example, if the client PC makes a DHCP request to the server PC, the server PC receives the request and offers an IP to the client, but the client does not accept it, timing out instead), check that you don't have other Iptables rules interfering.

See also