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.
    • 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
                              • K
                                k3nb5t
                                last edited by

                                An update: my clients are now routing IPv6 correctly, but the gateway issue persists.

                                I needed to update a couple firewall rules, but my rules have been failing to apply since my CoDel limiter requires an address on my IPv6 gateway to function. I disabled the IPv6 pass rule that applies the limiter so that I could complete my other update. After doing so, IPv6 traffic has begun to flow again.

                                So it seems there is no issue with the underlying routing, in my case. Only that without a gateway address populated on the interface, I'm unable to apply my limiter. Possibly other issues? Not sure, but perhaps this changes the conversation a bit?

                                1 Reply Last reply Reply Quote 0
                                • SpaceyS
                                  Spacey @k3nb5t
                                  last edited by

                                  @k3nb5t What is that IPv6 Address pointed to for your monitor IP?

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

                                    @spacey That's Google Public DNS. I don't use their DNS services, but I do ping them :)

                                    https://developers.google.com/speed/public-dns/docs/using

                                    SpaceyS 1 Reply Last reply Reply Quote 0
                                    • SpaceyS
                                      Spacey @k3nb5t
                                      last edited by Spacey

                                      @k3nb5t said in IPv6 No Gateway after 2.5 upgrade:

                                      https://developers.google.com/speed/public-dns/docs/using

                                      I'd hate to hijack the thread but I am also experiencing this issue with WAN IPv6 on Comcast, strangely under interfaces it says it has an IPv6 address, even for LAN, but under Gateways it says Unknown and Pending for IPv6- where it didn't previously before updating. I tried everything mentioned in this thread, also not quite sure why after editing the monitor IP (which didn't work) for WAN DHCPv6 it shows an anchor now

                                      bf75825d-4b1b-4721-b7db-5c84eadb422e-image.png

                                      L 1 Reply Last reply Reply Quote 0
                                      • SpaceyS
                                        Spacey
                                        last edited by

                                        Actually Update- it works now after restarting and putting the monitor IP as Google (which I don't understand why this has to be done I don't want to use Google at all and never had this previously at all)

                                        But still doesn't display correctly

                                        3e966f26-40a3-492b-900e-4b758a55d59a-image.png

                                        1 Reply Last reply Reply Quote 0
                                        • L
                                          lnguyen @Spacey
                                          last edited by

                                          @spacey said in IPv6 No Gateway after 2.5 upgrade:

                                          why after editing the monitor IP (which didn't work) for WAN DHCPv6 it shows an anchor now

                                          Because once you edited it and saved the gateway, it overrides the default in the list. If you delete it, the default will reappear and will not have an anchor. You will also notice that you won't be able to delete the default.

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

                                            Got it working here too using the IP6 address on the WAN interface as a monitor ID.

                                            On the LAN side I can now ping Google's IP6 DNS servers.

                                            May change the monitor IP to Google IP6 DNS server as it was before.

                                            1 - "What is my IP" is showing an IP6 address
                                            2 - test-ipv6.comcast.net shows a 10 now
                                            3 - ipv6-test.com shows 17/20.
                                            4 - not showing an IP 6 gateway address in Dashboard
                                            5 - not showing an IP 6 address in console
                                            6 - can ping google's IP6 DNS servers from the console shell and ping

                                            As mentioned above looks like but not sure that it is a DHCP6 issue or PFSense doesn't display gateway address anymore??

                                            • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.