[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

7. Platform specific information


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

7.1 Interface configuration

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:

Linuxifconfig interface address netmask netmask
Linux iproute2ip addr add address/prefixlength dev interface
FreeBSDifconfig interface address netmask netmask
OpenBSDifconfig interface address netmask netmask
NetBSDifconfig interface address netmask netmask
Solarisifconfig interface address netmask netmask
Darwin (MacOS/X)ifconfig interface address netmask netmask
Windowsnetsh interface ip set address interface static address netmask

For IPv6 addresses:

Linuxifconfig interface add address/prefixlength
FreeBSDifconfig interface inet6 address prefixlen prefixlength
OpenBSDifconfig interface inet6 address prefixlen prefixlength
NetBSDifconfig interface inet6 address prefixlen prefixlength
Solarisifconfig interface inet6 plumb up
ifconfig interface inet6 addif address address
Darwin (MacOS/X)ifconfig interface inet6 address prefixlen prefixlength
Windowsnetsh interface ipv6 add address interface static address/prefixlength

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

7.2 Routes

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:

Linuxroute add -net network_address netmask netmask interface
Linux iproute2ip route add network_address/prefixlength dev interface
FreeBSDroute add network_address/prefixlength local_address
OpenBSDroute add network_address/prefixlength local_address
NetBSDroute add network_address/prefixlength local_address
Solarisroute add network_address/prefixlength local_address -interface
Darwin (MacOS/X)route add network_address/prefixlength local_address
Windowsnetsh routing ip add persistentroute network_address netmask interface local_address

Adding routes to IPv6 subnets:

Linuxroute add -A inet6 network_address/prefixlength interface
Linux iproute2ip route add network_address/prefixlength dev interface
FreeBSDroute add -inet6 network_address/prefixlength local_address
OpenBSDroute add -inet6 network_address local_address -prefixlen prefixlength
NetBSDroute add -inet6 network_address local_address -prefixlen prefixlength
Solarisroute add -inet6 network_address/prefixlength local_address -interface
Darwin (MacOS/X)?
Windowsnetsh interface ipv6 add route network address/prefixlength interface

[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by buildd user on December 2, 2011 using texi2html 1.82.