2.2.1: No IPv6 assigned to LAN anymore

c0re

So I just upgraded to 2.2.1 and lost my IPv6 connectivity to the LAN as well. I'm in the same boat as many people here (with Canadian ISP Teksavvy) who hands out a /64 for the WAN and a /56 for the LAN. I was able to enable "track interface" and the internet seems to work, but now almost everything on the LAN is broken because of it. I'm probably just not figuring out how this works, but hopefully somebody here knows…

How do I get a static IPv6 address back to the router so I can add it to a local DNS server and not have to remember the IP?
How can I manually define internal DNS servers via IPv6 now? I need my systems to use domain controllers as DNS servers or else a lot of things will obviously break.
For my servers with IPv6 addresses, can I continue to manually assign static IPv6 addresses to them? What gateway do I use now if the router no longer has a static address?
How can I access servers by hostname/fqdn now? The track interface option got the internet back up, but all my static IP addresses that were assigned to my servers stopped working so I can't find them on the LAN anymore (via IPv6). What addresses should I assign?

It's certainly possible that a lot of this stuff is way over my head, but I really don't understand how using "Track interface" will function reliably in a managed environment. Doesn't this leave the network in an incredibly vulnerable situation where if the ISP changes something one day then all my servers, client devices and DNS settings will instantly break? It seems to me that if the ISP screws something up or gives you a different IP delegation one day then it's not too big of a deal if it causes your internet connection to stop working. If it simultaneously takes your whole LAN down though, that's a rather serious issue. There must be something I'm missing?

c0re

So in the end I with "Track Interface" selected on the LAN side my connection was very flaky over IPv6. For some reason, clients were taking a very long time to get their IPv6 addresses (up to 5 minutes). Then some clients started randomly losing their IPv6 internet access again. This piled on top of all the ways this breaks the LAN configuration and internal DNS resolution settings already in place, I decided that configuring it this way is probably going to be unreliable and more trouble than it's worth, at least with Teksavvy IPv6 addressed handed out via prefix delegation.

In the end, I configured Interfaces | WANv6 | DHCP6 client configuration like this and put everything else back how it was before and it works fine again:

Thanks to azzido in post #25 from this thread for the solution.

foxale08

Attempted the above fix, no dice. Syslog shows the following message:

rtsold[37541]: <sendpacket>sendmsg on em0_vlan100: Operation not permitted

My wan interface is em0_vlan100</sendpacket>

foxale08

Just an update. I got an Intel 350-T4 adapter (igb) and am using one of the ports for my wan (untagged) IPv6 is now working properly. Is this an issue with tagged interfaces on em cards?