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.
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.
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 22.214.171.124/24 dev net0 # arbitrary address
To have your static ip assigned at boot, you can use netctl.
Enable packet forwarding
Enter this command to temporaly enable packet forwarding:
# sysctl net.ipv4.ip_forward=1
/etc/sysctl.conf to make the previous change persistent after a reboot.
If you are using ipv6, use this:
# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE # iptables-save > /etc/iptables/iptables.rules # systemctl start iptables
iptables.serviceto auto start at boot.
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.
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 126.96.36.199/24 dev eth0 # ip link set up dev eth0 # ip route add default via 188.8.131.52 dev eth0
Add a nameserver:
# echo "nameserver <nameserver ip>" >> /etc/resolv.conf
You can figure out the address of the nameserver by looking into the
/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:
- Google Public DNS
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.