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.9k Views 30 Watching
    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.
    • peteP Offline
      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??

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

        Seems like the IPv6 link-local gateway address is not being parsed and populated neither for Status | Gateways or Status | Interfaces

        From my experience, it was partially defunct (restarting dpinger solved this after a reboot) on 2.4.5-p1 and completely borked now with pfSense+ 21.02 and pfSense CE 2.5.

        SpaceyS 1 Reply Last reply Reply Quote 1
        • SpaceyS Offline
          Spacey @lnguyen
          last edited by

          @lnguyen I'm beginning to wonder if it's possible to copy the interfaces section of my 2.4.5 XML file - specifically the DHCPv6, and appending it to my current 2.5 XML, having a hard time narrowing it down where it would go into, looking at the two side by side there isn't much of a difference, I just know it displayed correctly in Gateways for WAN DHCPv6 with the IPv6 address and showed online. ugh.

          L 2 Replies Last reply Reply Quote 0
          • L Offline
            lnguyen @Spacey
            last edited by lnguyen

            @spacey Obviously there is an underlying regression in code but for now what do you want to accomplish?

            • Display the IPv6 Link-Local Gateway address

            and/or

            • Monitor the IPv6 Link-Local Gateway address

            If so you can grab the IPv6 Link-Local Gateway address from Diagnostics | Routes and manually define it:

            System | Routing | Gateways | WAN_DHCP6 | Monitor IP
            1 Reply Last reply Reply Quote 0
            • L Offline
              lnguyen @Spacey
              last edited by

              @spacey said in IPv6 No Gateway after 2.5 upgrade:

              wonder if it's possible to copy the interfaces section of my 2.4.5 XML file - specifically the DHCPv6, and appending it to my current 2.5 XML

              I don't believe this would yield a positive difference as I think the issue is not config but rather code.

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

                Issue has been reported on Redmine:

                https://redmine.pfsense.org/issues/11454

                A 1 Reply Last reply Reply Quote 4
                • A Offline
                  anzenketh @lnguyen
                  last edited by

                  @lnguyen said in IPv6 No Gateway after 2.5 upgrade:

                  https://redmine.pfsense.org/issues/11454

                  Thanks for filing that bug. Hopefully it gets some attention soon. I think you are right about a bug in the code. I just upgraded to 21.02-RELEASE for my SG-1100. It states for WAN_DHCP6 unknown for status. Yet the following is true.

                  • Under interfaces it lists the IPV6 address for WAN
                  • I can ping ipv6.google.com with IP protocol IPV6 from Diagnostics -> Ping
                  L S 2 Replies Last reply Reply Quote 1
                  • L Offline
                    lnguyen @anzenketh
                    last edited by lnguyen

                    @anzenketh said in IPv6 No Gateway after 2.5 upgrade:

                    Thanks for filing that bug.

                    Someone else filed it. I only shared it here in the forums.

                    Under interfaces it lists the IPV6 address for WAN
                    I can ping ipv6.google.com with IP protocol IPV6 from Diagnostics -> Ping

                    Take note that in 2.4.5-p1 under Status | Interfaces there is a field for Gateway IPv6. This is completely missing for pfSense+ 21.02 and pfSense CE 2.5

                    WAN Interface (wan, igb0)
Status up
DHCP up     Relinquish Lease
MAC Address 00:08:a2:00:00:00 - ADI Engineering
IPv4 Address X.X.X.X
Subnet mask IPv4 255.255.248.0
Gateway IPv4 X.X.X.X
IPv6 Link Local fe80::X%igb0
IPv6 Address X::X
Subnet mask IPv6 128
Gateway IPv6 fe80::X 
DNS servers 127.0.0.1
                    M 1 Reply Last reply Reply Quote 0
                    • M Offline
                      mrsunfire @lnguyen
                      last edited by

                      I have the same problem after update to 2.5.0

                      IPv6 is working but there is no gateway.

                      Unbenannt.PNG

                      Netgate 6100 MAX

                      M viktor_gV 2 Replies Last reply Reply Quote 0
                      • M Offline
                        mrsunfire @mrsunfire
                        last edited by mrsunfire

                        pfSense has the IPv6 gateway but is not showing it under Interfaces tab and widget.

                        After I reboot the cable modem I again getting IP addresses but then no IPv6 connection. Pinging also isn't possible anymore. Tried everything only rebooting pfSense works.

                        BUT: my second WAN (PPPoE DSL) is working without any issues. It's only the cable connection. Both connections use the same IPv6 config to get the /56 prefix (that seems working) and the PPPoe also is getting IPv6 Gateway. The cable does not.

                        Netgate 6100 MAX

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

                          @mrsunfire Please attach the /var/log/dhcpd.log file for checking

                          M 1 Reply Last reply Reply Quote 0
                          • M Offline
                            mrsunfire @viktor_g
                            last edited by mrsunfire

                            @viktor_g said in IPv6 No Gateway after 2.5 upgrade:

                            /var/log/dhcpd.log

                            igb5 = WAN (DHCP6), igb4 = LAN (tracked)

                            Feb 19 09:21:26 pfsense dhcp6c[25262]: Sending Solicit
Feb 19 09:21:26 pfsense dhcp6c[25262]: a new XID (56b2b5) is generated
Feb 19 09:21:26 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:26 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:26 pfsense dhcp6c[25262]: send solicit to ff02::1:2%igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1091
Feb 19 09:21:26 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162142, T2=259427
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284 vltime=929084
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162137, T2=259420
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324275 vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:26 pfsense dhcp6c[25262]:   preference: 255
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:26 pfsense dhcp6c[25262]: server ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx, pref=255
Feb 19 09:21:26 pfsense dhcp6c[25262]: Sending Request
Feb 19 09:21:26 pfsense dhcp6c[25262]: a new XID (1e2c66) is generated
Feb 19 09:21:26 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set server ID (len 14)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA address
Feb 19 09:21:26 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:26 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:26 pfsense dhcp6c[25262]: send request to ff02::1:2%igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: reset a timer on igb5, state=REQUEST, timeo=0, retrans=909
Feb 19 09:21:26 pfsense dhcp6c[25262]: receive reply from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162142, T2=259427
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284 vltime=929084
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162137, T2=259420
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324275 vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:26 pfsense dhcp6c[25262]: dhcp6c Received REQUEST
Feb 19 09:21:26 pfsense dhcp6c[25262]: nameserver[0] 2a02:908:2:a::1
Feb 19 09:21:26 pfsense dhcp6c[25262]: nameserver[1] 2a02:908:2:b::1
Feb 19 09:21:26 pfsense dhcp6c[25262]: make an IA: PD-0
Feb 19 09:21:26 pfsense dhcp6c[25262]: create a prefix 2a02:80xx:xxx:xxxx::/56 pltime=324275, vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:26 pfsense dhcp6c[25262]: make an IA: NA-0
Feb 19 09:21:26 pfsense dhcp6c[25262]: create an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284, vltime=2143238558160137532
Feb 19 09:21:26 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: executes /var/etc/dhcp6c_wan_script.sh
Feb 19 09:21:26 pfsense dhcp6c[26929]: dhcp6c RELEASE, REQUEST or EXIT on igb5 running rc.newwanipv6
Feb 19 09:21:28 pfsense dhcp6c[25262]: script "/var/etc/dhcp6c_wan_script.sh" terminated
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=REQUEST
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing server (ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx)
Feb 19 09:21:28 pfsense dhcp6c[25262]: got an expected reply, sleeping.
Feb 19 09:21:28 pfsense dhcp6c[25262]: restarting
Feb 19 09:21:28 pfsense dhcp6c[25262]: Bypassing address release because of -n flag
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an IA: NA-0
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=118
Feb 19 09:21:28 pfsense dhcp6c[25262]: Bypassing address release because of -n flag
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an IA: PD-0
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove a site prefix 2a02:80xx:xxx:xxxx::/56
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=256
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=INIT
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=INIT
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=244
Feb 19 09:21:29 pfsense dhcp6c[25262]: Sending Solicit
Feb 19 09:21:29 pfsense dhcp6c[25262]: a new XID (2fb2e1) is generated
Feb 19 09:21:29 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:29 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:29 pfsense dhcp6c[25262]: send solicit to ff02::1:2%igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1055
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=302400, T2=483840
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx pltime=604800 vltime=1209600
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=302400, T2=483840
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:8071:xxxx:xxxx::/56 pltime=604800 vltime=1209600
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:29 pfsense dhcp6c[25262]:   preference: 0
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: server ID: 00:01:00:01:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx, pref=0
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset timer for igb5 to 0.985677
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162140, T2=259424
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281 vltime=929081
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162136, T2=259417
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324272 vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:29 pfsense dhcp6c[25262]:   preference: 255
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: server ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx, pref=255
Feb 19 09:21:29 pfsense dhcp6c[25262]: Sending Request
Feb 19 09:21:29 pfsense dhcp6c[25262]: a new XID (c679ec) is generated
Feb 19 09:21:29 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set server ID (len 14)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA address
Feb 19 09:21:29 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:29 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:29 pfsense dhcp6c[25262]: send request to ff02::1:2%igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset a timer on igb5, state=REQUEST, timeo=0, retrans=1019
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive reply from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162140, T2=259424
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281 vltime=929081
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162136, T2=259417
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324272 vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: dhcp6c Received REQUEST
Feb 19 09:21:29 pfsense dhcp6c[25262]: nameserver[0] 2a02:908:2:a::1
Feb 19 09:21:29 pfsense dhcp6c[25262]: nameserver[1] 2a02:908:2:b::1
Feb 19 09:21:29 pfsense dhcp6c[25262]: make an IA: PD-0
Feb 19 09:21:29 pfsense dhcp6c[25262]: create a prefix 2a02:80xx:xxx:xxxx::/56 pltime=324272, vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:29 pfsense dhcp6c[25262]: make an IA: NA-0
Feb 19 09:21:29 pfsense dhcp6c[25262]: create an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281, vltime=2143238558160137529
Feb 19 09:21:29 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: executes /var/etc/dhcp6c_wan_script.sh
Feb 19 09:21:29 pfsense dhcp6c[34946]: dhcp6c RELEASE, REQUEST or EXIT on igb5 running rc.newwanipv6

                            Netgate 6100 MAX

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

                              This worked for me. Now passes on all IPv6 test sites I tried.

                              https://forum.netgate.com/topic/161047/updated-to-2-5-everything-went-smooth-except-for-wan-ipv6-status-being-stuck-on-unknown-and-pending-have-comcast-despite-multiple-cable-modem-restarts-and-pfsense-restarts/3

                              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
                              • A Offline
                                amessinamessinet.com
                                last edited by

                                As suggested, manually adding the Monitor address seems to solve part of the issue, though with Gateway hardcoded as "dynamic", it seems to affect the ability to use it in firewall rules -- CoDel Limiters, for example below.

                                21:00:51 There were error(s) loading the rules: /tmp/rules.debug:223: no routing address with matching address family found. - The line in question reads [223]: pass  out  quick  on {  igb1  }  $GWWAN_DHCP6 inet6 from any to any tracker 1610764779 keep state  dnqueue( 2,1)  label "USER_RULE: CoDel Limiters"
                                H S MikeV7896M 3 Replies Last reply Reply Quote 0
                                • H Offline
                                  heyj @amessinamessinet.com
                                  last edited by

                                  @amessinamessinet-com I am having the same issue.

                                  1 Reply Last reply Reply Quote 0
                                  • S Offline
                                    Segfault 0 @amessinamessinet.com
                                    last edited by

                                    @amessinamessinet-com This is the problem I'm having as well. I set the monitor address to the link-local address but now my CoDel Limiter for IPv6 is giving that error.

                                    1 Reply Last reply Reply Quote 0
                                    • MikeV7896M Offline
                                      MikeV7896 @amessinamessinet.com
                                      last edited by

                                      @amessinamessinet-com said in IPv6 No Gateway after 2.5 upgrade:

                                      As suggested, manually adding the Monitor address seems to solve part of the issue, though with Gateway hardcoded as "dynamic", it seems to affect the ability to use it in firewall rules -- CoDel Limiters, for example below.

                                      Yep... See this bug: https://redmine.pfsense.org/issues/11454

                                      As you mentioned, only part of the issue has a workaround (the monitoring, which affects IPv6 connectivity as a whole). The gateway selection part will likely require an update to pfSense once fixed.

                                      The S in IOT stands for Security

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

                                        This post is deleted!
                                        M 1 Reply Last reply Reply Quote 0
                                        • M Offline
                                          mrsunfire @pete
                                          last edited by

                                          Still no ETA for a fix? IPv6 is unusable after WAN fails one time.

                                          Netgate 6100 MAX

                                          1 Reply Last reply Reply Quote 2
                                          • S Offline
                                            SteveITS Rebel Alliance @anzenketh
                                            last edited by SteveITS

                                            @anzenketh said in IPv6 No Gateway after 2.5 upgrade:

                                            I can ping ipv6.google.com with IP protocol IPV6 from Diagnostics -> Ping

                                            That's where I am on an SG-2100 with 21.02, I can ping that from my PC behind it. Status/Interfaces has a default route for IPv6. The router has a default route for IPv6 in Diagnostics/Routes, just no gateway for IPv6 shown in Status/Interfaces.

                                            It sounds like some people have IPv6 connectivity and some don't? Essentially for me it's just a cosmetic issue with the GUI. After upgrade I (re)installed pfBlockerNG-devel and Snort but didn't reboot again.

                                            Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                            When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
                                            Upvote 👍 helpful posts!

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