I finally found a reason to use IPv6 NAT/masquerading and this feels so wrong. Trying to route my home net into a walled garden /64 subnet.
-
-
Replying to @marcan42
Some ISP provides subnet delegation of around /60 size via dhcpv6, and openwrt provides an automatic setup by default.
1 reply 0 retweets 0 likes -
Replying to @nakayoshikw_gyx @Gyx__
This isn't an ISP service, but a walled garden. DHCPv6 only hands out split DNS, no prefixes. My real ISP gives me a /56 of course.
1 reply 0 retweets 0 likes -
What I'm trying to do is NAT my subnets (which are from my real /56) into the walled garden prefixes so they can access it and the Internet.
2 replies 0 retweets 0 likes -
Replying to @marcan42
In this case, I think avoiding NAT is still possible but might be harder to configure than the NAT approach.
1 reply 0 retweets 0 likes -
Replying to @nakayoshikw_gyx @marcan42
eg., allocate a /64 out of the /56 and then setup routing and dhcp/slaac accordingly, using some scripts to adapt to changes in dhcp leases
1 reply 0 retweets 0 likes -
Replying to @nakayoshikw_gyx @Gyx__
I still have the issue that I only get a /64 to participate in the walled garden. There's no way around doing address translation.
1 reply 0 retweets 0 likes -
Maybe using router advertisements for my main network and sub-/64 allocation via DHCPv6 for the walled garden, but that's even messier.
1 reply 0 retweets 0 likes -
I want my end hosts to not have to change. They get a simple single routable v6 address and can just transparently NAT to the walled garden.
1 reply 0 retweets 0 likes -
Replying to @marcan42
OK, I misunderstood at the first reading... So here NAT is used for home subnet to access the walled garden, not the other way around
2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.