Re:Hetzner removes traffic limitation for dedicated servers
by lambada on Tuesday October 02, 2018 @10:18AM
(#18121902)
Could you elaborate more about how pfsense doesn't like just /64? As someone who ordered a Hetzner server from them a couple of days ago after a hefty price increase from my current provider this concerns me - getting IPv6 working through pfsense and into machines behind it is the next tech project I have on my list!
[ Parent
| on HN ]
Re:Hetzner removes traffic limitation for dedicated servers
by zaarn on Tuesday October 02, 2018 @10:28AM
(#18122018)
How well it works depends on your setup, in my case I use a routed configuration, I'm unsure if bridged would be better.
The basic gist is that pfSense wants to be allocated a /64 via prefix allocation via a router advertisement (SLAAC or DHCPv6). Only in this configuration can you set the LAN interface to track the WAN, which allows you to use a single /64.
Sadly there isn't a dedicated server provider out there that I know off that cleanly supports this configuration.
In almost all cases you'll have to manually assign subnets inside the /64 (ie a /65 for the WAN interface and a /65 for LAN) so you can route around traffic. It's a bit annoying to setup but possible.
(It's still much better than OVH's IPv6 support which is just plain broken)
Re:Hetzner removes traffic limitation for dedicated servers
by rashomon on Tuesday October 02, 2018 @02:34PM
(#18124382)
Why aren't they offering a /56. People offering /64 are doing the same things while thinking of IPv4 exhaustion