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

    Cox IPv6 Settings?

    Scheduled Pinned Locked Moved IPv6
    coxipv6interface
    3 Posts 2 Posters 3.8k 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.
    • beremonavabiB
      beremonavabi
      last edited by

      Does anyone have a link to actual, current information from Cox about what IPv6 settings we should use to connect to their network? My WAN/LAN Interface settings have been based on things gleaned here over the years and I've been wondering if they need updating. Searching here doesn't seem to get me anything newer than 2018. Checking my Cox account or their web pages gives me nothing of substance. Even DSL Reports doesn't seem to have anything past 2017. And searches of the general internet give me almost nothing.

      Currently my IPv6 settings in my WAN Interface are set as:

      • IPv6 Configuration Type: DHCP6
      • DHCPv6 Prefix Delegation size: 56
      • Send IPv6 prefix hint: On

      For my LAN Interface:

      • IPv6 Configuration Type: Track Interface
      • IPv6 Interface: WAN
      • IPv6 Prefix ID: 0

      The one thing I'm really wondering about is that Track Interface setting on the LAN. Does Cox actually restrict us to that? Or, can we use something like DHCP6 or SLAAC? From:

      https://docs.netgate.com/pfsense/en/latest/interfaces/configure-ipv6.html

      Track Interface looks like a good option. But, in my ignorance, DHCP6 actually looks better. SLAAC also looks good except for the possible issue with DNS.

      SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

      1 Reply Last reply Reply Quote 0
      • MikeV7896M
        MikeV7896
        last edited by

        If you use DHCPv6 on WAN to request a prefix, the only proper way to pass that to your internal networks is through "Track Interface". That way, if your prefix changes in the future, your networks will update to use the new prefix. Each internal network needs to use a unique prefix ID.

        SLAAC and DHCP6 won't work on your internal networks because you're not getting IPv6 information from another router on those networks. If pfSense is your only router, the only things that could be used internally are Static (if you have a static prefix assigned to you by your ISP) or Track Interface (if you're getting a prefix delegated to you by your ISP's DHCPv6 server).

        As far as Cox-specific settings... it's unlikely that they've changed anything, since their rollout is complete nationwide (at least according to their website), so if /56 works for you, then keep on using it. The prefix ID for your LAN can be anything within the range of the prefix you've requested. So if you wanted to change that, you could at any time. That's not specific to your ISP.

        The S in IOT stands for Security

        beremonavabiB 1 Reply Last reply Reply Quote 1
        • beremonavabiB
          beremonavabi @MikeV7896
          last edited by

          @virgiliomi Thanks. That's a really helpful answer. I appreciate it.

          SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

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