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

    IPv6 No Gateway after 2.5 upgrade

    Scheduled Pinned Locked Moved IPv6
    97 Posts 27 Posters 29.6k 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.
    • ?
      A Former User
      last edited by

      Have you tried disabling and then enabling the gateway? I have had that issue on and off with 2.4.5. I haven’t yet upgraded to 2.5.

      provelsP K 2 Replies Last reply Reply Quote 0
      • provelsP
        provels @A Former User
        last edited by provels

        @jwj
        Tried mine, same. Had not seen it before.

        Peder

        MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
        BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

        1 Reply Last reply Reply Quote 0
        • K
          k3nb5t @A Former User
          last edited by

          @jwj I appreciate the suggestion. I just tried it, no change.

          I've also tried rebooting the device (the desperation reboot).

          Here's a screenshot, just to illustrate what I'm seeing.

          interfaces.png

          1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash @k3nb5t
            last edited by

            @k3nb5t said in IPv6 No Gateway after 2.5 upgrade:

            • Single WAN interface
              • Comcast Gigabit, with a Motorola MB8600 modem
              • Configured for DHCP6, no checkboxes checked (except debug mode while I try to solve this) with prefix size is 64

            I'm pretty sure Comcast hands out a prefix size of 60

            K 1 Reply Last reply Reply Quote 0
            • K
              k3nb5t @dotdash
              last edited by

              @dotdash Pretty sure it was giving me a /64 before. Still, I tried changing the prefix delegation size to 60 and restarting the interface. The result was no change.

              dotdashD 1 Reply Last reply Reply Quote 0
              • dotdashD
                dotdash @k3nb5t
                last edited by

                @k3nb5t
                Looked into it a bit, and it seems they will go up to a /60, but if you request a /64, they will lock that to your DUID, so you can't get a larger one. The solution appears to be disabling v6 and resetting the DUID, then enabling and requesting a /60.
                (which is all completely off topic to your issue, sorry)

                K provelsP 2 Replies Last reply Reply Quote 1
                • K
                  k3nb5t @dotdash
                  last edited by

                  @dotdash I haven't run VLANs since I switched to Comcast, but If I end up setting them up again this info will come in handy. Thank you :)

                  1 Reply Last reply Reply Quote 0
                  • provelsP
                    provels @dotdash
                    last edited by

                    @dotdash said in IPv6 No Gateway after 2.5 upgrade:

                    resetting the DUID

                    How do I do that? Thanks.

                    Peder

                    MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                    BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                    dotdashD 1 Reply Last reply Reply Quote 0
                    • dotdashD
                      dotdash @provels
                      last edited by

                      @provels
                      Haven't had to do it myself, but my understanding is you disable v6, then delete /var/db/dhcp6c_duid, reboot and re-enable. I may have too many or too few reboots in there.

                      provelsP 1 Reply Last reply Reply Quote 0
                      • provelsP
                        provels @dotdash
                        last edited by provels

                        @dotdash
                        Thanks. Gave it a shot but no difference. Thanks again.

                        FWIW, I'm on Comcast, too.
                        64a6e243-e35c-4a67-9517-48efbcf3679a-image.png

                        Peder

                        MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                        BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                        1 Reply Last reply Reply Quote 0
                        • X
                          xpxp2002
                          last edited by

                          Upgraded from 2.4.5-p1 and also encountering this issue with Spectrum (legacy TWC). IPv6 and PD is working, but the gateway status is not being monitored. Reboot did not help. Also rebooted modem. I also tried switching off "do not wait for RA" on the WAN interface, thinking that it needed to see the router IP from the RA, but that also did not change anything.

                          This was affecting my dynamic DNS, as the IPv6 address wasn't being picked up off of the WAN interface anymore. Saving the WAN_DHCP6 gateway in Gateway settings fixed that, but it still doesn't report the gateway status, and simply shows "Pending".

                          1 Reply Last reply Reply Quote 0
                          • peteP
                            pete
                            last edited by

                            Same issue here after upgrade an hour or so ago.

                            Pending a resolution I have disabled IPV6 and IPV6 gateway.

                            • Pete

                            Auto mater
                            23.09.1-RELEASE (amd64)
                            built on Mon Dec 11 12:24:00 CST 2023
                            FreeBSD 14.0-CURRENT
                            PFSense + Qotom - Master
                            PFSense + Jetway - Backup
                            PFSense + Jetway - Backup
                            PFSense + Generic - Backup

                            1 Reply Last reply Reply Quote 0
                            • X
                              xpxp2002
                              last edited by

                              Found a workaround: Edit the IPv6 gateway and manually set the Monitor IP to the link-local address of the gateway.

                              It doesn’t fix that this should be automatically read, presumably out of the routing table, but it at least gets the gateway monitor working until a more permanent resolution is known.

                              JKnottJ 1 Reply Last reply Reply Quote 0
                              • N
                                nedyah700 Rebel Alliance
                                last edited by

                                I am having the same issue. Everything IPv6 is working post 21.02 (2.5) upgrade except for the monitoring. I've tried countless configuration changes and am giving up for the night.

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

                                  @xpxp2002

                                  Have you configured something to happen when the monitor fails? If not, why use it?

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

                                  X 1 Reply Last reply Reply Quote 0
                                  • peteP
                                    pete
                                    last edited by pete

                                    Renabled IP6 / XFinity this morning. Disabled monitoring.

                                    From the SSH console interface I can ping the Google IP6 DNS servers fine.

                                    From a shell I cannot ping the Google IP6 DNS servers.

                                    Disabled IP6 and deleted the DUID file under /var/db/dhcp6c_duid

                                    per

                                    Comcast's IPv6 prefix delegation is based on the DUID of your system as generated when it was first being set up.

                                    • Pete

                                    Auto mater
                                    23.09.1-RELEASE (amd64)
                                    built on Mon Dec 11 12:24:00 CST 2023
                                    FreeBSD 14.0-CURRENT
                                    PFSense + Qotom - Master
                                    PFSense + Jetway - Backup
                                    PFSense + Jetway - Backup
                                    PFSense + Generic - Backup

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      xpxp2002 @JKnott
                                      last edited by

                                      @jknott It seemed to be affecting dynamic DNS.

                                      Dynamic DNS (RFC2136 clients) was only publishing an A record for a DDNS update that should have included the v4 and v6 IPs of the WAN interface, and had with 2.4.5-p1. That's what originally led me to start looking to see if something odd was going on with IPv6 or DHCP6 after the upgrade.

                                      Once I added the gateway monitor manually, it immediately posted a new DDNS update with a AAAA record added.

                                      1 Reply Last reply Reply Quote 0
                                      • viktor_gV
                                        viktor_g Netgate
                                        last edited by viktor_g

                                        Could you provide more information about your configuration?

                                        Unable to reproduce it in my testing environment:
                                        Screenshot from 2021-02-18 20-10-19.png

                                        Screenshot from 2021-02-18 20-10-32.png

                                        K 1 Reply Last reply Reply Quote 0
                                        • peteP
                                          pete
                                          last edited by pete

                                          Renabled IP6 on the WAN interface.

                                          I can now ping the Google IP6 DNS server: 2001:4860:4860::8888

                                          From the console:

                                          root: ping6 2001:4860:4860::8888
                                          PING6(56=40+8+8 bytes) 2607:XXX --> 2001:4860:4860::8888
                                          16 bytes from 2001:4860:4860::8888, icmp_seq=0 hlim=117 time=40.559 ms
                                          16 bytes from 2001:4860:4860::8888, icmp_seq=1 hlim=117 time=30.148 ms
                                          16 bytes from 2001:4860:4860::8888, icmp_seq=2 hlim=117 time=39.546 ms
                                          16 bytes from 2001:4860:4860::8888, icmp_seq=3 hlim=117 time=39.262 ms

                                          Testing Comcast test-ipv6.comcast.net and ipv6-test.com shows I have no IP6.

                                          IP6 Gateway states on Dashboard shows pending with status unknown.

                                          • Pete

                                          Auto mater
                                          23.09.1-RELEASE (amd64)
                                          built on Mon Dec 11 12:24:00 CST 2023
                                          FreeBSD 14.0-CURRENT
                                          PFSense + Qotom - Master
                                          PFSense + Jetway - Backup
                                          PFSense + Jetway - Backup
                                          PFSense + Generic - Backup

                                          1 Reply Last reply Reply Quote 0
                                          • K
                                            k3nb5t @viktor_g
                                            last edited by

                                            @viktor_g I'm happy to assist, but I'm not certain what information to give. Can you be more specific?

                                            Here's a bunch of stuff that may or may not be helpful :)

                                            WAN
                                            WAN.png

                                            LAN
                                            LAN.png

                                            GATEWAY
                                            gateway.png

                                            RA
                                            RA.png

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