SixXS::Sunset 2017-06-06

Having "subnet" addresses preferred over "tunnel" addresses
[de] Shadow Hawkins on Wednesday, 11 October 2006 22:45:27
Hi, I have a tunnel to my box at home, and a subnet routed to it for all the remaining boxen. For consistency, I was wondering whether it would make sense to use the address from the internal, "subnet" interface on the tunnel endpoint only, as the status quo is that the IPv6 stack selects the one that has the longest common prefix with the destination, so connections from my host seem to originate on two different addresses. Also, I'm not sure it is necessary to use globally routed adresses on the tunnel interface if the first thing one does is add a subnet over it. So, would it make sense to "force" the address scope down to "link" on the tunnel (if that is at all possible; the Linux IPv6 stack seems to ignore me anyway)? Would it make sense to have an option to "give back" the addresses on the tunnel link, as they are unneeded as soon as a subnet is present, in order to conserve address space :-) Simon
Having "subnet" addresses preferred over "tunnel" addresses
[ch] Jeroen Massar SixXS Staff on Wednesday, 11 October 2006 22:52:14
On Linux just assign a /128 from the subnet also on the tunnel interface. eg, I have on purgatory: eth1 Link encap:Ethernet HWaddr 08:00:2B:E7:02:B3 inet addr:213.136.24.43 Bcast:213.136.24.255 Mask:255.255.255.0 inet6 addr: 2001:7b8:5:10:74::2/80 Scope:Global inet6 addr: fe80::a00:2bff:fee7:2b3/64 Scope:Link inet6 addr: 2001:7b8:20d:0:290:27ff:fe24:c19f/128 Scope:Global The /80 is the block for the transit tunnel. The /128 is from the /48 assigned to that endpoint. Linux kernel apparently uses the 'last assigned address' when deciding which IPv6 address to use for sending packets outbound. Thus because of that assigning the /128 after the /64 it works ;)

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker