• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

config.xml corruption

Scheduled Pinned Locked Moved General pfSense Questions
4 Posts 3 Posters 452 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W
    wlp94611
    last edited by Jul 1, 2021, 2:56 PM

    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.

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Jul 1, 2021, 3:02 PM

      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).

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • W
        wlp94611
        last edited by Jul 1, 2021, 7:25 PM

        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!

        J 1 Reply Last reply Jul 1, 2021, 8:36 PM Reply Quote 0
        • J
          JKnott @wlp94611
          last edited by Jul 1, 2021, 8:36 PM

          @wlp94611

          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.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received