[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.1 Interface configuration | ||
7.2 Routes |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When configuring an interface, one normally assigns it an address and a netmask. The address uniquely identifies the host on the network attached to the interface. The netmask, combined with the address, forms a subnet. It is used to add a route to the routing table instructing the kernel to send all packets which fall into that subnet to that interface. Because all packets for the entire VPN should go to the virtual network interface used by tinc, the netmask should be such that it encompasses the entire VPN.
For IPv4 addresses:
Linux | |
Linux iproute2 | |
FreeBSD | |
OpenBSD | |
NetBSD | |
Solaris | |
Darwin (MacOS/X) | |
Windows | |
For IPv6 addresses:
Linux | |
FreeBSD | |
OpenBSD | |
NetBSD | |
Solaris | |
| |
Darwin (MacOS/X) | |
Windows | |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In some cases it might be necessary to add more routes to the virtual network interface. There are two ways to indicate which interface a packet should go to, one is to use the name of the interface itself, another way is to specify the (local) address that is assigned to that interface (local_address). The former way is unambiguous and therefore preferable, but not all platforms support this.
Adding routes to IPv4 subnets:
Linux | |
Linux iproute2 | |
FreeBSD | |
OpenBSD | |
NetBSD | |
Solaris | |
Darwin (MacOS/X) | |
Windows | |
Adding routes to IPv6 subnets:
Linux | |
Linux iproute2 | |
FreeBSD | |
OpenBSD | |
NetBSD | |
Solaris | |
Darwin (MacOS/X) | ? |
Windows | |
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by root on November, 5 2007 using texi2html 1.78.