config.xml corruption
-
My config.xml seems to be corrupted.
Comcast recently upgraded their service to be 2.5gbs capable, with my Motorola MB8600 going from compatible to not compatible, so I replace it with a Motorola MB8611.
I'm run a dual-stack network, with IPv6 set to track the WAN interface. Prior to Comcast's upgrade, I received an IPv6 address with a /64 subnet mask. Post upgrade the subnet mask changed to a /128.
Comcast, of course, tells me that the problem is with the Motorola modem. Yesterday, out of frustration and curiosity, I booted pfSense with a basic configuration file I keep for testing, and to my surprise IPv6 came up with a /64 subnet mask.
All of this leads me to believe there is some sort of corruption in my production config.
Does anyone have any thoughts about how I might track that down. I don't relish the thought of having to rebuild my firewall.
Thanks for your input.
-
It's unlikely to be any kind of corruption. Incorrect settings, perhaps, but not corruption.
Take the basic config and your previous config and look at the differences in the interface settings for both WAN and LAN. Odds are something is not quite right in the DHCPv6 settings on one or the other (e.g. PD length).
-
Jim,
Thank for your input.
My testing shows that if I only request an IPv6 prefix, my internal networks are supplied addresses with a /64 subnet mask. As soon as I request an external IPv6 address, Comcast supplies a WAN address with a /128 subnet mask, breaking my internal network.
Everything functioned flawlessly until Comcast upgraded their service. The ball is in their court, and as soon as I can get a fiber connection here in my neighborhood, I will be dropping them.
My best regards to you and the team. I love your software!
-
You don't need a WAN address, as link local addresses are often used for routing. So, run that way for a while and see what happens later.
