Configuration for IPv6 over tunnel

Joe Holden lists at rewt.org.uk
Wed Sep 10 20:52:27 UTC 2014


On 10/09/2014 18:26, Dan Langille wrote:
> The existing documentation for setting up IPv6 over a tunnel is incorrect.
>
> Specifically: gifconfig is deprecated.  Use cloned_interfaces="gif0" instead.
>
>    https://www.freebsd.org/doc/handbook/network-ipv6.html
>
> I have filed a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193523
>
> I have the following configuration for my IPv6 tunnel on FreeBSD 9.3 from Hurricane Electric.
>
> Given:
>
> IPv6 Tunnel Endpoints
> Server IPv4 Address:  209.51.x.y
> Server IPv6 Address:  2001:470:xx06:9ea::1/64
> Client IPv4 Address:  96.245.100.201
> Client IPv6 Address:  2001:470:xx06:9ea::2/64
>
> Routed /64:           2001:470:xx07:9ea::/64
>
>
> My /etc/rc.conf includes
>
> cloned_interfaces="gif0”
>
> ifconfig_gif0="tunnel 96.245.100.201 209.51.x.y mtu 1480”
>
> ifconfig_gif0_ipv6="inet6 2001:470:xx06:9ea::2 2001:470:xx06:9ea::1 prefixlen 128"
>
> ifconfig_em0_ipv6="inet6 2001:470:xx07:9ea:1::1”
>
> ipv6_defaultrouter="2001:470:xx06:9ea::1"
>
> ipv6_gateway_enable=“YES"
>
> rtadvd_enable=“YES”
>
>
> Comments?  Suggestions?
>
While we're at it, "Routers only store network aggregation addresses in 
their routing tables, thus reducing the average space of a routing table 
to 8192 entries. This addresses the scalability issues associated with 
IPv4, which required every allocated block of IPv4 addresses to be 
exchanged between Internet routers, causing their routing tables to 
become too large to allow efficient routing."

isn't true and neither is

  "These addresses are syntactically indistinguishable from unicast 
addresses but they address a group of interfaces. The packet destined 
for an anycast address will arrive at the nearest router interface. 
Anycast addresses are only used by routers."

No idea what you'd put in place, though :)


More information about the freebsd-net mailing list