Here is an Example
Code:
# In / etc / network / interfaces would define something as follows:
auto tun6to4
inet6 tun6to4 iface v4tunnel
address 2002: YYYY: YYYY: 1:: 1
netmask 16
gateway:: 192.88.99.1
Any endpoint
XXX.XXX.XXX.XXX local
up ip -6 route add:: / 0 metric 1 dev tun6to4
up ip -6 route add 2000:: / 3 via:: 192.88.99.1 metric 1 dev tun6to4
up ip -6 route add 2000:: / 3 via 2002: YYYY: YYYY:: 1 metric 1 dev tun6to4
up ip -6 addr add 2002: YYYY: YYYY:: 1 / 16 dev tun6to4
up ip -6 addr add 2002: YYYY: YYYY: 1:: 1 / 64 dev br0
down ip -6 route flush dev tun6to4
up / etc/network/ipv6rules.sh
255 ttl
mtu 1480
# Where it says XXX.XXX.XXX.XXX is your public IPv4, where is your place YYYY.YYYY converted to hexadecimal IPv4, the IPv6 prefix 2002 in the format indicates a compatibility and this means that we have a range of 65535 IPv6 for us all alone, until the alarm can be IP.
This will create an interface that automatically route the IPv6 traffic for us. Look at what I call the script / etc/network/ipv6rules.sh to configure the IPv6 firewall (in my case is ipv6tables, native linux kernel). Once created and launched the tunnel of the forms listed above, would fail to install a program to transfer the routes to other computers on the network, in the case of linux using radvd. If not installed and configured, only the team with the tunnel 6to4 IPv6 connectivity will, while if it is installed and configured, the other teams know how to reach the next router and be publicly visible, this is how IPv6 solves the problem of NAT (remember the typical: To go out there to use the front door pass it on!).
Bookmarks