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

−

Let's assume you have an Internet connection and you want to share it. There are two main ways to do that.

−

<pre>

+

== Requirements ==

−

Internet pc1

−

1. ----> |router| ---> |switch| --->-<

−

pc2 ..etc

−

−

Internet

−

2. ------> |pc1 (router)| --> pc2..etc

−

</pre>

−

==Instructions==

+

* The machine acting as server should have an additional network device.

−

I'll explain the second way (it is easier and requires one less machine).

+

* 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 [[Wikipedia:Network switch|switch]] is required. If you are sharing to only one machine, a [[Wikipedia:Ethernet crossover cable|crossover cable]] is sufficient.

−

<ol>

−

<li>Install a second network card to the first PC.</li>

−

<li>Connect the two PCs using an ethernet cable or a [[Wikipedia:Network switch|switch]]. If one of the two computers has a gigabit ethernet card, a regular ethernet cable should work. Otherwise, use [[Wikipedia:Ethernet crossover cable|crossover cable]].</li>

+

{{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}}

−

<li>Let's assume that the first card (with the Internet) is called '''''internet0''''' and the other one (for the sharing) is called '''''local0'''''. (If those two keep switching at every boot read [[Udev#Setting static device names]]). The network interface of the client machine will be called '''''local1'''''.

+

== Configuration ==

−

The interfaces '''''local0''''' and '''''local1''''' will have to be in the same network.</li>

+

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'''''.

−

<li>Configure the second network card with:

+

{{Tip|You can rename your devices to this scheme using [[Udev#Setting static device names]].}}

−

:'''IP:''' 192.168.0.1

−

:'''Netmask:''' 255.255.255.0

−

or enter in a console (as root)

−

<pre>ifconfig local0 192.168.0.1 netmask 255.255.255.0

−

ip link set local0 up</pre></li>

−

<li>To make this permanent, install [[netcfg]] if you don't have it and set up a network profile in '''/etc/network.d''', drawing on the examples in '''/etc/network.d/examples'''. Or, put the above lines in '''/etc/rc.local'''.

+

=== Static IP address ===

−

<li>Enable packet forwarding. To do so, write a "'''1'''" to '''/proc/sys/net/ipv4/ip_forward''' with:

+

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 139.96.30.100/24 dev net0 # arbitrary address

−

{{bc|1=sysctl net.ipv4.ip_forward=1}}

+

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

−

<li>Edit '''/etc/sysctl.conf''' and add this line, which will make the previous change persistent after a reboot.

<li>Add iptables in your DAEMONS array in your /etc/rc.conf so that it is started each time.</li>

+

Edit {{ic|/etc/sysctl.conf}} to make the previous change persistent after a reboot.

+

{{hc|/etc/sysctl.conf|<nowiki>

+

net.ipv4.ip_forward=1

+

</nowiki>}}

−

<li>Go to the client PC and set:

+

If you are using ipv6, use this:

−

:'''IP:''' 192.168.0.2

+

{{hc|/etc/sysctl.conf|<nowiki>

−

:'''Netmask:''' 255.255.255.0

+

net.ipv6.conf.default.forwarding=1

−

:'''Gateway:''' 192.168.0.1

+

net.ipv6.conf.all.forwarding=1

−

:'''DNS:''' The same DNS as the first PC

+

</nowiki>}}

−

<pre>ifconfig local1 192.168.0.2 netmask 255.255.255.0

+

=== Enable NAT ===

−

ifconfig local1 up

−

route add default gw 192.168.0.1 local1

−

echo "nameserver <adr of nameserver>" >> /etc/resolv.conf

−

</pre>

−

You can figure out the address of the nameserver by looking into the /etc/resolv.conf of PC1, if its Internet connection is already established. If you don't have a nameserver, you can use [https://code.google.com/speed/public-dns/ Google Public DNS] which is relatively fast. Its addresses are '''8.8.8.8''' and '''8.8.4.4'''.</li></ol>

+

[[pacman|Install]] the package {{Pkg|iptables}} from the [[Official Repositories|official repositories]]. Use iptables to enable NAT:

−

{{Note| Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)}}

+

# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE

+

# iptables-save > /etc/iptables/iptables.rules

+

# systemctl start iptables

+

+

{{Note|Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1).}}

+

+

{{Tip|You can set {{ic|iptables.service}} to [[Daemon|auto start at boot]].}}

+

+

Read the [[iptables]] article for more information. There's 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 [[Wikipedia:dhcp|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 139.96.30.120/24 dev eth0

+

# ip link set up dev eth0

+

# ip route add default via 139.96.30.100 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 {{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]

+

** 8.8.8.8

+

** 8.8.4.4

+

** [2001:4860:4860::8888]

+

** [2001:4860:4860::8844]

+

* [https://opendns.com OpenDNS]:

+

** 208.67.222.222

+

** 208.67.220.220

+

** [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.

Line 77:

Line 98:

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 [https://bbs.archlinux.org/viewtopic.php?pid=1093208 interfering].

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 [https://bbs.archlinux.org/viewtopic.php?pid=1093208 interfering].

−

==See also==

+

== See also ==

−

*[[Sharing ppp connection with wlan interface]]

+

−

*[[Simple stateful firewall]]

+

* [[Ad-hoc networking]]

−

*[[Router]]

+

* [[Sharing PPP Connection]]

−

*[[USB 3G Modem]]

+

* [[Simple stateful firewall]]

+

* [[Router]]

+

* [[USB 3G Modem]]

Revision as of 12:06, 30 August 2013

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

Contents

Requirements

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

Configuration

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.

Note: Bracket notation must be used for IPv6 addresses in resolv.conf.

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

Troubleshooting

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.