Thanks for the explanation Mark. I will try that when I get home and get on my test setup. I'll report back with my findings or more inquiries.
On Wed, Oct 1, 2014 at 11:31 AM, Mark Tinberg mark.tinberg@wisc.edu wrote:
That's the thing Mark, configuring it is where I'm stuck. I'm unsure of what addresses I'm supposed to be using as the prefixes that Hurricane Electric gives me for /64 and /48, are different from the tunnel's
endpoint
address. At least I think I'm reading it right from the tunnel's information page.
So an he.net tunnel has a /64 used as a point-to-point network which is what runs on the IPv4 tunnel, and either a single /64 that you route for your internal subnet, or a /48 which allows you to carve out 65535 subnets of /64 each, equivalent addressing to an IPv4 /16 where each address is NATting for an entire network itself.
So pick the first /64 subnet inside your /48 allocated to you and route that internally and set that up in your router advertisement daemon.
For example if your point-to-point is 2001:470:AAAA:1234::1/64 (HE.net) -- 2001:470:AAAA:1234::2/64 (your router)
and your routed subnets are out of 2001:470:BBBB:1234::/48
2001:470:BBBB:1234::/64 2001:470:BBBB:1235::/64 ...
Then you'd have say 2001:470:BBBB:1234::1/64 on one router interface and advertise 2001:470:BBBB:1234::/64
— Mark Tinberg, System Administrator Division of Information Technology - Network Services University of Wisconsin - Madison mark.tinberg@wisc.edu _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos