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

    Troubleshooting LAN IPv6 Track Interface (Cox)

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 838 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.
    • ChrisLynchC
      ChrisLynch
      last edited by

      I'm using pfSense 2.5.2-Release Community.

      I just recently upgraded to Cox's Gigablast service, from an older DOCSIS 3.0 modem where IPv6 was working just fine. My WAN interface received a lease, and the LAN interface received a delegate block. Clients on the LAN side received their IPv6 addresses. I then replace the modem with the one provided by Cox, and now only the WAN interface receives an IPv6 address. A different one than before, even though the DUID-UUID didn't change.

      My WAN interface is configured as such:

      b2453563-2529-409a-a23b-7e23a69c9539-image.png
      dee72070-b324-4628-8ab3-81f762db9df1-image.png

      Originally, I did not have Use IPv4 connectivity as parent interface, Send IPv6 prefix hint and the Prefix Delegation size was default of 60. I have rebooted the firewall several times after making these changes, and still only the WAN interface receives an IPv6 address.

      Are there logs that I can look at to help me figure out what could be happening with the LAN interface?

      Here's a screenshot of the interfaces screen on my firewall:

      63a1013a-ce70-4210-b3c3-9be97c0b95a3-image.png

      1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott
        last edited by

        @chrislynch said in Troubleshooting LAN IPv6 Track Interface (Cox):

        I then replace the modem with the one provided by Cox, and now only the WAN interface receives an IPv6 address.

        Is it in bridge or gateway mode? You need bridge mode.

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

        ChrisLynchC 2 Replies Last reply Reply Quote 1
        • ChrisLynchC
          ChrisLynch @JKnott
          last edited by

          @jknott

          Ah, I wasn't aware of that. I just found Cox's support article on how to change this. I'll do that and then see. Thanks!

          1 Reply Last reply Reply Quote 0
          • ChrisLynchC
            ChrisLynch @JKnott
            last edited by

            @jknott Thank you so much for pointing that out. The presense of the 192.168.0.0/24 address should have been a clue. Stupid me didn't think of bridge mode. I was able to enable bridge mode and everything is working as expected.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.