@ethereal said in IPv6 DHCPv6 Delegation Range:
@bob-dig probably his setup is a bit more complex and using the firewall as firewall - rather than a router for his lan.
@simple0ne I have a similar setup at home and I was thinking to go ahead and try to implement it.
Will give it a go next weekend or so.
@Ethereal sounds good. I will get back to testing this further in the next few days hopefully, so I'll let you know if I discover any thing interesting.
@Bob-Dig, yep two use separate use cases. One is where the firewall is basically already just serving as firewall (+ proxy for some services on IPv4) as @Ethereal mentioned.
The second scenario is actually a little different and has two flavours (though they are quite similar to each other):
The pf is serving as the outside firewall of a dual vendor DMZ, but the pf is also providing some services to devices/networks living within the DMZ.
Similar to the first, but the pf is the only firewall, but is providing some services to downstream clients. There are a few networks, each with a lot of WAPs (that are actually routing) on them, which are managed separately, but wish to have IPv6 routed to them for allocation to wireless clients.
Part of the problem here isn't purely technical, it's that the administrative domains for different devices/parts of the network are owned by different parties. This makes for some additional headwinds when it comes to adopting wider changes that could make everything a bit easier to resolve.