Difference between revisions of "Internet sharing"

From ArchWiki
Jump to: navigation, search
(Instructions: fix old link)
m (Manually adding an ip: Fix command for setting up client ip)
(11 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
[[it:Internet Share]]
 
[[it:Internet Share]]
 
[[ru:Internet Share]]
 
[[ru:Internet Share]]
==Preface==
+
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
+
* The machine acting as server should have an additional network device
1. ----> |router| ---> |switch| --->-<
+
* That network device should be connected to the machines are going to receive internet access. They can be one or more machines,. To be able to share internet to several machies a [[Wikipedia:Network switch|switch]] is required. If you are sharing to only one machine, a [[Wikipedia:Ethernet crossover cable|crossover cable]] is sufficient
                                      pc2 ..etc
+
{{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==
  Internet
+
Using [[Udev#Setting static device names]], name the network device connected the other computer(s) as '''''net0''''' and the network device connected to the internet as '''''internet0'''''.
2. ------> |pc1 (router)| --> pc2..etc
+
===Static IP address===
</pre>
+
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.
 +
{{bc|
 +
# ip link set up dev net0
 +
# ip addr add 139.96.30.100/24 dev net0 # arbitrary address
 +
}}
 +
To have your static ip assigned at boot, you can use [[netcfg]].
  
==Instructions==
+
===Enable packet forwarding===
I'll explain the second way (it is easier and requires one less machine).
+
Enter this command to temporaly enable packet forwarding:
<ol>
+
{{bc|<nowiki>sysctl net.ipv4.ip_forward=1</nowiki>}}
<li>Install a second network card to the first PC.</li>
+
Edit {{ic|/etc/sysctl.conf}} and add this line, which will make the previous change persistent after a reboot.
 
+
{{bc|<nowiki>net.ipv4.ip_forward=1</nowiki>}}
<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>
+
 
+
<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'''''.
+
 
+
The interfaces '''''local0''''' and '''''local1''''' will have to be in the same network.</li>
+
 
+
<li>Configure the second network card with:
+
:'''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
+
ifconfig 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'''.
+
 
+
<li>Enable packet forwarding. To do so, write a "'''1'''" to '''/proc/sys/net/ipv4/ip_forward''' with:
+
<pre>echo 1 > /proc/sys/net/ipv4/ip_forward</pre></li>
+
 
+
<li>Edit '''/etc/sysctl.conf''' and add this line, which will make the previous change persistant after a reboot.
+
<pre>net.ipv4.ip_forward=1</pre>
+
 
If you are using ipv6, use these lines:
 
If you are using ipv6, use these lines:
<pre>net.ipv6.conf.default.forwarding=1
+
{{bc|<nowiki>
net.ipv6.conf.all.forwarding=1</pre></li>
+
net.ipv6.conf.default.forwarding=1
 +
net.ipv6.conf.all.forwarding=1
 +
</nowiki>}}
 +
===Enable NAT===
 +
[[pacman|Install]] the package {{Pkg|iptables}} from the [[Official Repositories|official repositories]].
 +
Use iptables to enable NAT:{{bc|<nowiki>
 +
# iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE
 +
# iptables-save > /etc/iptables/iptables.rules
 +
# systemctl start iptables
 +
</nowiki>}}{{Note| Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)}}
 +
You can set {{ic|iptables.service}} to [[Daemon|auto start a boot]].
  
<li>Install iptables, enable NAT (needed to share Internet), save and start it.
+
Read the [[iptables]] article for more information.
<pre>pacman -S iptables
+
iptables -t nat -A POSTROUTING -o internet0 -j MASQUERADE
+
rc.d save iptables
+
rc.d start iptables</pre></li>
+
  
<li>Add iptables in your DAEMONS array in your /etc/rc.conf so that it is started each time.</li>
+
===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]].
  
<li>Go to the client PC and set:
+
You can read the [[dhcpd]] wiki article, to add a dhcp server. Then, install the [[dhcpcd]] client on every client pc.
:'''IP:''' 192.168.0.2
+
:'''Netmask:''' 255.255.255.0
+
:'''Gateway:''' 192.168.0.1
+
:'''DNS:''' The same DNS as the first PC
+
  
<pre>ifconfig local1 192.168.0.2 netmask 255.255.255.0
+
If you are not planing to use this setup regularly, you can manually add an ip to each client instead.
ifconfig local1 up
+
====Manually adding an ip====
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>
+
Instead of using dhcp, on each client pc, add an ip address and the default route:
 +
{{bc|<nowiki>
 +
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
 +
</nowiki>}}
 +
Add a nameserver:
 +
{{bc|<nowiki>
 +
echo "nameserver <nameserver ip>" >> /etc/resolv.conf
 +
</nowiki>}}
  
{{Note| Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)}}
+
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 [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'''.
  
 
That's it. The client PC should now have Internet.
 
That's it. The client PC should now have Internet.

Revision as of 02:09, 13 January 2013

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

Requirements

  • The machine acting as server should have an additional network device
  • That network device should be connected to the machines are going to receive internet access. They can be one or more machines,. To be able to share internet to several machies 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

Using Udev#Setting static device names, name the network device connected the other computer(s) as 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 139.96.30.100/24 dev net0 # arbitrary address

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

Enable packet forwarding

Enter this command to temporaly enable packet forwarding:

sysctl net.ipv4.ip_forward=1

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

net.ipv4.ip_forward=1

If you are using ipv6, use these lines:

net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1

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-save > /etc/iptables/iptables.rules
# systemctl start iptables
Note: Of course, this also works with a mobile broadband connection (usually called ppp0 on PC1)

You can set iptables.service to auto start a boot.

Read the iptables article for more information.

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 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 /etc/resolv.conf of the server, if its Internet connection is already established. If you don't have a nameserver, you can use Google Public DNS which is relatively fast. Its addresses are 8.8.8.8 and 8.8.4.4.

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.

See also