Delegating IPv6 networks to a downstream router
-
@JKnott I see, thanks for the tip! That probably works, indeed.
The downside is that my static routes will become obsolete when my public IPv4 address (and thus IPv6 networks calculated based on that) change, right?
-
Probably. Do your IPv4 addresses change often? My ISP originally provided 6to4 and 6rd, but I didn't use either as I had 6in4 from elsewhere. However, my IPv4 address was virtually static. DHCP addresses normally don't change, unless you aren't connected for longer than the lease time, unless you have a nasty ISP.
-
One other possibility, some here use 6in4 from he.net to get a /48. That won't change with your IPv4 address.
-
@JKnott Not too often (maybe once every 3-4 months), but often enough still that some kind automation would probably be needed.
It seems that it might indeed be easier to separate the IPv6 gateway to a separate Linux VM or use some other IPv6 provider having static IPv6 addresses.. Too bad, the 6rd with pfSense was so easy to set up. :)
-
-
Yeah just use HE here, you can do anything you want with your /48.. Its just routed down your tunnel.. If you want to route part of that to a downstream, its as simple as creating the routes..
You can also then take that /48 with you if you change ISPs..
You could route a /56 to 1 downstream router, and a another /56 to a different one, etc. etc.
-
Can you provide some more info about "as simple a creating the routes" to delegate ipv6 networks to downstream routers? I'm trying to but only /64 (RA) worked.
-
With HE the /48 is routed to you statically via your tunnel.
So lets say your /48 is 2001:0420:aaaa::/48
So via a tunnel network you create just route whatever you want to some downstream router..
You could take the first /64 out of the first /56 and use that as your tunnel
2001:0420:aaaa:0000::/64Then route the 2nd /56 to downstream 2001:0420:aaaa:0100::/56
Then you can break that up in to /64's off that downstream router..
Does this help? This is really no different than routing in IPv4, just the networks are bigger and addresses are longer.. While yes lots and lots of stuff is different in IPv6 over IPv4.. When it comes to routing basics, its the same as IPv4..
-
@johnpoz It is what I'm trying to do with pfsense.
For example:
The first 2001:0420:aaaa::1/56 was set on LAN.
The others/56 was configured at RA.
But the router still got a /64.
-
You wouldn't use RA to delegate prefixes, you would use dhcpv6
-
Or manual config. I don't know that I'd want a router to rely on DHCP. I used manual config to connect to a Cisco router.
-
^Exactly - how I showed manually routing the /56 to a downstream router above ;) That his how I would do it as well.
-
Config is done and working as expected.
Got a /48 from HE and /50 subnets to LAN.
DHCPv6 Server & RA (/56 to downstream CPEs)
RA
Tested with Android 8/9, Android TV 7.1.2, iOS 9.3.6, Windows 10, Arch Linux, OpenWRT, and some others Home Gateways.
