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

    No IPv6 after upgrade to 23.01

    Scheduled Pinned Locked Moved IPv6
    88 Posts 19 Posters 56.4k 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.
    • GertjanG
      Gertjan
      last edited by

      @maverickws said in No IPv6 after upgrade to 23.01:

      Internet6:
      Destination Gateway Flags Netif Expire
      localhost link#7 UHS lo0
      2001:8ZZ:6cZZ:f500 link#1 U igb0
      pfs-fw link#1 UHS lo0

      netstat -r shows me :

      d856c476-aacf-470e-b4c5-a82716c3d89a-image.png

      There should be a default route.

      No "help me" PM's please. Use the forum, the community will thank you.
      Edit : and where are the logs ??

      maverickwsM 1 Reply Last reply Reply Quote 0
      • maverickwsM
        maverickws @Gertjan
        last edited by maverickws

        @gertjan yeah I also noticed that.

        So, what's wrong with the pfSense software and why isn't a default route added?
        It's nothing with the config for sure. Don't even have the IPv6 gateway on automatic, explicitly selected the WAN interface.

        The very same config was working for the previous version. Looking at some posts around, seems like many users are getting the IPv6 broken. Should I go and add routes manually? I can, but I shouldn't have to.

        As you said:

        The DHCP4 client and DHCP6 client obtain their info from the ISP DHCP4 server - and DHCP6 server, both are upstream and not local to you.

        The DHCP6 server upstream is working correctly for sure. It didn't stop working because I updated my software.
        Actually if I plug my machine directly to the modem I get IPv6 connectivity without issues.

        Bob.DigB S 2 Replies Last reply Reply Quote 0
        • Bob.DigB
          Bob.Dig LAYER 8 @maverickws
          last edited by

          @maverickws Show your configs, like WAN, LANs and Routing with the Gateways, also your rules on LAN.
          Pending Gateways you often have to change the monitor address.
          Here it is working as always.

          maverickwsM 1 Reply Last reply Reply Quote 0
          • maverickwsM
            maverickws @Bob.Dig
            last edited by maverickws

            @bob-dig sure, here goes:

            Screenshot 2023-02-21 at 13.14.09.png

            Screenshot 2023-02-21 at 13.14.36.png

            Screenshot 2023-02-21 at 13.15.21.png

            Screenshot 2023-02-21 at 13.22.14.png

            The gateway is pending because something is blocking IPv6 otherwise, wouldn't have any issue in reaching it, just as it didn't BEFORE the update, just like my machine is able if I plug it directly to the modem.

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @maverickws
              last edited by

              @maverickws

              You can make DHCPD on WAN so it logs with a lot more details. Go to System > Advanced > Networking and check :

              c647d68d-5e82-4726-9d24-25b3d39d1e5a-image.png

              Now do a Status > Interfaces Release and then a Renew for WAN.

              You should see a lot of dhcp6c log lines on the DHCP log page.

              If, by any change, the IPv6 gateway isn't replying to ping, then you could give it an IPv6 'monitor' IP that will reply.
              For example :

              nslookup dns.google.com
              

              and instead of the usual 8.8.8.8, pick the IPv6 equivalent, like 2001:4860:4860::8888.

              They reply both (for me) to ICMP6.

              Or : (ok during test phase) check "Disable Gateway Monitoring".

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              maverickwsM 1 Reply Last reply Reply Quote 0
              • S
                SteveITS Galactic Empire @maverickws
                last edited by

                @maverickws said in No IPv6 after upgrade to 23.01:

                Don't even have the IPv6 gateway on automatic, explicitly selected the WAN interface

                Did you try automatic? (Usually it's the other way around, automatic has some issue and selecting the gateway works...)

                Does Status/Interfaces show an IPv6 gateway?

                Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
                Upvote 👍 helpful posts!

                1 Reply Last reply Reply Quote 0
                • maverickwsM
                  maverickws @Gertjan
                  last edited by maverickws

                  @gertjan

                  Here's the debug log, rebooted after enabling the option. The log starts on the end.

                  Feb 21 13:56:21	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:56:21	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:56:21	dhcp6c	39062	status code: no addresses
                  Feb 21 13:56:21	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:56:21	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:56:21	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:56:21	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:56:21	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:56:21	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:56:21	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:56:21	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:56:21	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:56:21	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=6, retrans=64125
                  Feb 21 13:56:21	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:56:21	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:56:21	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:56:21	dhcp6c	39062	set identity association
                  Feb 21 13:56:21	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:56:21	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:49	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:49	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:49	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:49	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:49	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:49	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:49	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:49	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:49	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:49	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:49	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:49	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:49	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=5, retrans=31623
                  Feb 21 13:55:49	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:49	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:49	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:49	dhcp6c	39062	set identity association
                  Feb 21 13:55:49	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:49	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:37	dhcpd	67775	Server starting service.
                  Feb 21 13:55:37	dhcpd	67775	Sending on Socket/6/igb0/2001:8XX:6YY0:1600::/64
                  Feb 21 13:55:37	dhcpd	67775	Listening on Socket/6/igb0/2001:8XX:6YY0:1600::/64
                  Feb 21 13:55:37	dhcpd	67775	Sending on Socket/6/igb0.3/2001:8XX:6YY0:1603::/64
                  Feb 21 13:55:37	dhcpd	67775	Listening on Socket/6/igb0.3/2001:8XX:6YY0:1603::/64
                  Feb 21 13:55:37	dhcpd	67775	Sending on Socket/6/igb0.1/2001:8XX:6YY0:1601::/64
                  Feb 21 13:55:37	dhcpd	67775	Listening on Socket/6/igb0.1/2001:8XX:6YY0:1601::/64
                  Feb 21 13:55:37	dhcpd	67775	Bound to *:547
                  Feb 21 13:55:37	dhcpd	67775	Wrote 0 NA, 0 TA, 0 PD leases to lease file.
                  Feb 21 13:55:37	dhcpd	67775	For info, please visit https://www.isc.org/software/dhcp/
                  Feb 21 13:55:37	dhcpd	67775	All rights reserved.
                  Feb 21 13:55:37	dhcpd	67775	Copyright 2004-2022 Internet Systems Consortium.
                  Feb 21 13:55:37	dhcpd	67775	Internet Systems Consortium DHCP Server 4.4.3-P1
                  Feb 21 13:55:37	dhcpd	67775	PID file: /var/run/dhcpdv6.pid
                  Feb 21 13:55:37	dhcpd	67775	Database file: /var/db/dhcpd6.leases
                  Feb 21 13:55:37	dhcpd	67775	Config file: /etc/dhcpdv6.conf
                  Feb 21 13:55:37	dhcpd	67775	For info, please visit https://www.isc.org/software/dhcp/
                  Feb 21 13:55:37	dhcpd	67775	All rights reserved.
                  Feb 21 13:55:37	dhcpd	67775	Copyright 2004-2022 Internet Systems Consortium.
                  Feb 21 13:55:37	dhcpd	67775	Internet Systems Consortium DHCP Server 4.4.3-P1
                  Feb 21 13:55:37	dhcpd	67305	Server starting service.
                  Feb 21 13:55:37	dhcpd	67305	Sending on Socket/fallback/fallback-net
                  Feb 21 13:55:37	dhcpd	67305	Sending on BPF/igb0/40:62:31:03:bd:10/192.168.AA.0/24
                  Feb 21 13:55:37	dhcpd	67305	Listening on BPF/igb0/40:62:31:03:bd:10/192.168.AA.0/24
                  Feb 21 13:55:37	dhcpd	67305	Sending on BPF/igb0.3/40:62:31:03:bd:10/192.168.BB.0/24
                  Feb 21 13:55:37	dhcpd	67305	Listening on BPF/igb0.3/40:62:31:03:bd:10/192.168.BB.0/24
                  Feb 21 13:55:37	dhcpd	67305	Sending on BPF/igb0.2/40:62:31:03:bd:10/192.168.CC.0/24
                  Feb 21 13:55:37	dhcpd	67305	Listening on BPF/igb0.2/40:62:31:03:bd:10/192.168.CC.0/24
                  Feb 21 13:55:37	dhcpd	67305	Sending on BPF/igb0.1/40:62:31:03:bd:10/192.168.DD.0/24
                  Feb 21 13:55:37	dhcpd	67305	Listening on BPF/igb0.1/40:62:31:03:bd:10/192.168.DD.0/24
                  Feb 21 13:55:37	dhcpd	67305	Wrote 18 leases to leases file.
                  Feb 21 13:55:37	dhcpd	67305	Wrote 0 new dynamic host decls to leases file.
                  Feb 21 13:55:37	dhcpd	67305	Wrote 0 deleted host decls to leases file.
                  Feb 21 13:55:37	dhcpd	67305	Wrote 0 class decls to leases file.
                  Feb 21 13:55:37	dhcpd	67305	For info, please visit https://www.isc.org/software/dhcp/
                  Feb 21 13:55:37	dhcpd	67305	All rights reserved.
                  Feb 21 13:55:37	dhcpd	67305	Copyright 2004-2022 Internet Systems Consortium.
                  Feb 21 13:55:37	dhcpd	67305	Internet Systems Consortium DHCP Server 4.4.3-P1
                  Feb 21 13:55:37	dhcpd	67305	PID file: /var/run/dhcpd.pid
                  Feb 21 13:55:37	dhcpd	67305	Database file: /var/db/dhcpd.leases
                  Feb 21 13:55:37	dhcpd	67305	Config file: /etc/dhcpd.conf
                  Feb 21 13:55:37	dhcpd	67305	For info, please visit https://www.isc.org/software/dhcp/
                  Feb 21 13:55:37	dhcpd	67305	All rights reserved.
                  Feb 21 13:55:37	dhcpd	67305	Copyright 2004-2022 Internet Systems Consortium.
                  Feb 21 13:55:37	dhcpd	67305	Internet Systems Consortium DHCP Server 4.4.3-P1
                  Feb 21 13:55:33	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:33	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:33	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:33	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:33	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:33	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:33	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:33	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:33	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:33	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:33	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:33	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:33	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=4, retrans=16314
                  Feb 21 13:55:33	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:33	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:33	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:33	dhcp6c	39062	set identity association
                  Feb 21 13:55:33	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:33	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:24	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:24	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:24	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:24	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:24	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:24	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:24	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:24	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:24	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:24	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:24	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:24	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:24	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=3, retrans=8193
                  Feb 21 13:55:24	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:24	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:24	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:24	dhcp6c	39062	set identity association
                  Feb 21 13:55:24	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:24	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:20	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:20	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:20	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:20	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:20	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:20	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:20	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:20	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:20	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:20	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:20	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:20	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:20	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=2, retrans=4058
                  Feb 21 13:55:20	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:20	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:20	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:20	dhcp6c	39062	set identity association
                  Feb 21 13:55:20	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:20	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:18	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:18	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:18	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:18	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:18	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:18	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:18	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:18	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:18	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:18	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:18	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:18	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:18	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=1, retrans=2075
                  Feb 21 13:55:18	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:18	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:18	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:18	dhcp6c	39062	set identity association
                  Feb 21 13:55:18	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:18	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:17	dhcp6c	39062	advertise contains no address/prefix
                  Feb 21 13:55:17	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:17	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:17	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:17	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:17	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:17	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:17	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:17	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:17	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:17	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:17	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:17	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1025
                  Feb 21 13:55:17	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:17	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:17	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:17	dhcp6c	39062	set identity association
                  Feb 21 13:55:17	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:17	dhcp6c	39062	a new XID (234d9d) is generated
                  Feb 21 13:55:17	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:17	dhcp6c	39062	got an expected reply, sleeping.
                  Feb 21 13:55:17	dhcp6c	39062	removing server (ID: 00:03:00:01:20:e0:9c:14:e4:01)
                  Feb 21 13:55:17	dhcp6c	39062	removing an event on igb5, state=REQUEST
                  Feb 21 13:55:17	dhcp6c	39062	script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh" terminated
                  Feb 21 13:55:17	dhcp6c	73605	dhcp6c REQUEST on igb5 - running rtsold
                  Feb 21 13:55:15	dhcp6c	39062	executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh
                  Feb 21 13:55:15	dhcp6c	39062	reset a timer on igb5, state=INIT, timeo=0, retrans=118
                  Feb 21 13:55:15	dhcp6c	39062	remove an IA: NA-0
                  Feb 21 13:55:15	dhcp6c	39062	IA NA-0 is invalidated
                  Feb 21 13:55:15	dhcp6c	39062	status code for NA-0: no addresses
                  Feb 21 13:55:15	dhcp6c	39062	make an IA: NA-0
                  Feb 21 13:55:15	dhcp6c	39062	add an address 2001:8XX:6YY0:16ff:4262:31ff:fe03:bd10/64 on igb0.2
                  Feb 21 13:55:15	dhcp6c	39062	add an address 2001:8XX:6YY0:1603:4262:31ff:fe03:bd10/64 on igb0.3
                  Feb 21 13:55:15	dhcp6c	39062	add an address 2001:8XX:6YY0:1601:4262:31ff:fe03:bd10/64 on igb0.1
                  Feb 21 13:55:15	dhcp6c	39062	add an address 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10/64 on igb0
                  Feb 21 13:55:15	dhcp6c	39062	create a prefix 2001:8XX:6YY0:1600::/56 pltime=90000, vltime=90000
                  Feb 21 13:55:15	dhcp6c	39062	make an IA: PD-0
                  Feb 21 13:55:15	dhcp6c	39062	nameserver[1] 2001:8XX:2206:5:212:55:154:190
                  Feb 21 13:55:15	dhcp6c	39062	nameserver[0] 2001:8XX:2106:5:212:55:154:174
                  Feb 21 13:55:15	dhcp6c	39062	dhcp6c Received REQUEST
                  Feb 21 13:55:15	dhcp6c	39062	IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option IA_PD prefix, len 25
                  Feb 21 13:55:15	dhcp6c	39062	IA_PD: ID=0, T1=45000, T2=72000
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option IA_PD, len 41
                  Feb 21 13:55:15	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:15	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:15	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:15	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:15	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:15	dhcp6c	39062	receive reply from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:15	dhcp6c	39062	reset a timer on igb5, state=REQUEST, timeo=0, retrans=909
                  Feb 21 13:55:15	dhcp6c	39062	send request to ff02::1:2%igb5
                  Feb 21 13:55:15	dhcp6c	39062	set IA_PD
                  Feb 21 13:55:15	dhcp6c	39062	set IA_PD prefix
                  Feb 21 13:55:15	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:15	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:15	dhcp6c	39062	set identity association
                  Feb 21 13:55:15	dhcp6c	39062	set status code
                  Feb 21 13:55:15	dhcp6c	39062	set server ID (len 10)
                  Feb 21 13:55:15	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:15	dhcp6c	39062	a new XID (c0df77) is generated
                  Feb 21 13:55:15	dhcp6c	39062	Sending Request
                  Feb 21 13:55:15	dhcp6c	39062	picked a server (ID: 00:03:00:01:20:e0:9c:14:e4:01)
                  Feb 21 13:55:14	dhcp6c	39062	reset timer for igb5 to 0.810179
                  Feb 21 13:55:14	dhcp6c	39062	server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1
                  Feb 21 13:55:14	dhcp6c	39062	IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option IA_PD prefix, len 25
                  Feb 21 13:55:14	dhcp6c	39062	IA_PD: ID=0, T1=45000, T2=72000
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option IA_PD, len 41
                  Feb 21 13:55:14	dhcp6c	39062	status code: no addresses
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option status code, len 33
                  Feb 21 13:55:14	dhcp6c	39062	IA_NA: ID=0, T1=0, T2=0
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option identity association, len 49
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option DNS, len 32
                  Feb 21 13:55:14	dhcp6c	39062	DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option client ID, len 14
                  Feb 21 13:55:14	dhcp6c	39062	DUID: 00:03:00:01:20:e0:9c:14:e4:01
                  Feb 21 13:55:14	dhcp6c	39062	get DHCP option server ID, len 10
                  Feb 21 13:55:14	dhcp6c	39062	receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
                  Feb 21 13:55:14	dhcp6c	39062	reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1091
                  Feb 21 13:55:14	dhcp6c	39062	send solicit to ff02::1:2%igb5
                  Feb 21 13:55:14	dhcp6c	39062	set IA_PD
                  Feb 21 13:55:14	dhcp6c	39062	set option request (len 4)
                  Feb 21 13:55:14	dhcp6c	39062	set elapsed time (len 2)
                  Feb 21 13:55:14	dhcp6c	39062	set identity association
                  Feb 21 13:55:14	dhcp6c	39062	set client ID (len 14)
                  Feb 21 13:55:14	dhcp6c	39062	a new XID (254c18) is generated
                  Feb 21 13:55:14	dhcp6c	39062	Sending Solicit
                  Feb 21 13:55:13	dhcp6c	39062	reset a timer on igb5, state=INIT, timeo=0, retrans=891
                  Feb 21 13:55:13	dhcp6c	39062	called
                  Feb 21 13:55:13	dhcp6c	39062	called
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[8] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-len] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[255] (3)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-id] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<5>[igb0.2] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[prefix-interface] (16)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[8] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-len] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[3] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-id] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<5>[igb0.3] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[prefix-interface] (16)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[8] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-len] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[1] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-id] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<5>[igb0.1] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[prefix-interface] (16)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[8] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-len] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[0] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[sla-id] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<5>[igb0] (4)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[prefix-interface] (16)
                  Feb 21 13:55:13	dhcp6c	39062	<13>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<13>[0] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<13>[pd] (2)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[id-assoc] (8)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<13>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<13>[0] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<13>[na] (2)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[id-assoc] (8)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of closure [}] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>comment [# we'd like nameservers and RTSOLD to do all the work] (53)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>["/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh"] (46)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[script] (6)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[domain-name] (11)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[request] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[domain-name-servers] (19)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[request] (7)
                  Feb 21 13:55:13	dhcp6c	39062	<3>comment [# request prefix delegation] (27)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[0] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[ia-pd] (5)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[send] (4)
                  Feb 21 13:55:13	dhcp6c	39062	<3>comment [# request stateful address] (26)
                  Feb 21 13:55:13	dhcp6c	39062	<3>end of sentence [;] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[0] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[ia-na] (5)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[send] (4)
                  Feb 21 13:55:13	dhcp6c	39062	<3>begin of closure [{] (1)
                  Feb 21 13:55:13	dhcp6c	39062	<5>[igb5] (4)
                  Feb 21 13:55:13	dhcp6c	39062	<3>[interface] (9)
                  Feb 21 13:55:13	dhcp6c	39062	skip opening control port
                  Feb 21 13:55:13	dhcp6c	39062	failed initialize control message authentication
                  Feb 21 13:55:13	dhcp6c	39062	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
                  Feb 21 13:55:13	dhcp6c	39062	extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10
                  Feb 21 13:55:13	dhclient	32283	bound to 80.000.000.111 -- renewal in 1800 seconds.
                  Feb 21 13:55:13	dhclient	37953	Creating resolv.conf
                  Feb 21 13:55:13	dhclient	37774	Adding new routes to interface: igb5
                  Feb 21 13:55:13	dhclient	37217	New Routers (igb5): 80.000.000.1
                  Feb 21 13:55:13	dhclient	37165	New Broadcast Address (igb5): 80.000.000.255
                  Feb 21 13:55:13	dhclient	37076	New Subnet Mask (igb5): 255.255.255.0
                  Feb 21 13:55:13	dhclient	37054	New IP Address (igb5): 80.000.000.111
                  Feb 21 13:55:13	dhclient	36880	ifconfig igb5 inet 80.000.000.111 netmask 255.255.255.0 broadcast 80.000.000.255
                  Feb 21 13:55:13	dhclient	36606	Starting add_new_address()
                  Feb 21 13:55:13	dhclient	36260	REBOOT
                  Feb 21 13:55:13	dhclient	32283	DHCPACK from 10.116.112.1
                  Feb 21 13:55:13	dhclient	32283	DHCPREQUEST on igb5 to 255.255.255.255 port 67
                  Feb 21 13:55:13	dhclient	35339	PREINIT
                  Feb 21 13:55:08	dhclient	23313	bound to 90.00.00.66 -- renewal in 6836 seconds.
                  Feb 21 13:55:08	dhclient	29666	Creating resolv.conf
                  Feb 21 13:55:08	dhclient	29389	Adding new routes to interface: igb4
                  Feb 21 13:55:08	dhclient	28933	New Routers (igb4): 90.00.00.254
                  Feb 21 13:55:08	dhclient	28623	New Broadcast Address (igb4): 90.00.00.255
                  Feb 21 13:55:08	dhclient	28597	New Subnet Mask (igb4): 255.255.248.0
                  Feb 21 13:55:08	dhclient	28396	New IP Address (igb4): 90.00.00.66
                  Feb 21 13:55:08	dhclient	28188	ifconfig igb4 inet 90.00.00.66 netmask 255.255.248.0 broadcast 90.00.00.255
                  Feb 21 13:55:08	dhclient	28121	Starting add_new_address()
                  Feb 21 13:55:08	dhclient	27711	REBOOT
                  Feb 21 13:55:08	dhclient	23313	unknown dhcp option value 0x65
                  Feb 21 13:55:08	dhclient	23313	unknown dhcp option value 0x64
                  Feb 21 13:55:08	dhclient	23313	DHCPACK from 109.00.00.254
                  Feb 21 13:55:08	dhclient	23313	DHCPREQUEST on igb4 to 255.255.255.255 port 67
                  Feb 21 13:55:08	dhclient	27124	PREINIT
                  
                  GertjanG 1 Reply Last reply Reply Quote 0
                  • GertjanG
                    Gertjan @maverickws
                    last edited by

                    pfSense asked for a prefix. I got one :
                    IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000
                    So : It uses create a prefix
                    2001:8XX:6YY0:1600::/56 pltime=90000, vltime=90000

                    The ‘0x00’ ID goes to the first interface :
                    2001:8XX:6YY0:1600:4262:31ff:fe03:bd10/64 on igb0
                    This means your first LAN interface has the IPv6 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10

                    The ‘0x01’ ID goes to the next interface :
                    2001:8XX:6YY0:1601:4262:31ff:fe03:bd10/64 on igb0.1

                    Etc.
                    2001:8XX:6YY0:16ff:4262:31ff:fe03:bd10/64 on igb0.2
                    Etc.
                    2001:8XX:6YY0:1603:4262:31ff:fe03:bd10/64 on igb0.3

                    Other LAN 'igb0' based devices should also get an IPv6 in the /64 range of 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10

                    Btw : first time I see interface (LAN) TRACKING actually working.

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

                    maverickwsM 1 Reply Last reply Reply Quote 0
                    • maverickwsM
                      maverickws @Gertjan
                      last edited by maverickws

                      @gertjan interface tracking has been working here for YEARS.

                      All local interfaces are correctly assigned an IPv6 from upstream correctly.

                      Now, NO Gateway. WHY?

                      All I did was update the software. There were no changes in the config. I'm here day after day providing every single thing I'm asked. It's all wonder, but in the end, IPv6 isn't working.

                      In my opinion there is clearly an issue with this software version. I'm starting to be alarmed for not seeing any involvement from anyone of Netgate on this thread. It's like something alike Schrödinger's cat? There is a problem and there isn't, let's not open the box and find out?

                      Bob.DigB 1 Reply Last reply Reply Quote 0
                      • Bob.DigB
                        Bob.Dig LAYER 8 @maverickws
                        last edited by

                        @maverickws Mine doesn't say dynamic, so something is wrong there I guess.

                        maverickwsM 1 Reply Last reply Reply Quote 0
                        • maverickwsM
                          maverickws @Bob.Dig
                          last edited by maverickws

                          @bob-dig your's doesn't say dynamic?

                          When it gets the GW from the upstream DHCP it changes from dynamic to something. Dynamic because it's configured by DHCP: Dynamic Host Configuration Protocol. Go figure.

                          If I unplug the network cable from WAN and reboot, IPv4 WAN will also show "dynamic" until its configured (by DHCP).

                          GertjanG 1 Reply Last reply Reply Quote 0
                          • GertjanG
                            Gertjan @maverickws
                            last edited by Gertjan

                            @maverickws said in No IPv6 after upgrade to 23.01:

                            IPv4 WAN will also show "dynamic" until its configured (by DHCP).

                            That looks like

                            IPv6 WAN will also show "dynamic" until its configured (by DHCP).
                            So, yeah, it doesn't get configured.

                            This is :

                            @maverickws said in No IPv6 after upgrade to 23.01:

                            receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5

                            your gateway I guess, if igb5 is your WAN interface.

                            I see the same lines in my dhcp6c log :

                            2023-02-21 16:15:36.288257+01:00 	dhcp6c 	76460 	receive reply from fe80::46d4:54ff:fe2a:3600%ix3 on ix3
                            

                            and then

                            efc4d71c-084d-47d4-a329-12372313357c-image.png

                            Strange indeed.
                            I'll locate my IPv6-expert list, see if I can ping request some one.
                            The thing is : it - the thing that communicates with the other side = dhcp6c, works "for me".
                            With the identical bare bone "DHCP6 Client Configuration" settings.
                            I'm using 23.01 Release.
                            ( and I'm pretty sure we don't have the same ISP ... )

                            Anyway, we should find what we haven't seen yet ;)

                            edit : do you need to check "Do not wait for a RA" ?

                            No "help me" PM's please. Use the forum, the community will thank you.
                            Edit : and where are the logs ??

                            maverickwsM Bob.DigB 2 Replies Last reply Reply Quote 0
                            • maverickwsM
                              maverickws @Gertjan
                              last edited by maverickws

                              @gertjan I have that option selected bc when I first configured it followed a tut for my ISP (Altice/MEO Portugal) and it said to enable that option. I can try and remove it an see how it goes.

                              Before updating to 23.01 it would show exactly as your Gateways print. I'm clueless.

                              igb5 is WAN
                              igb4 is WAN2

                              igb0 is LAN

                              Thank you for your effort in accompanying this and trying to get someone else to help

                              GertjanG S 2 Replies Last reply Reply Quote 0
                              • GertjanG
                                Gertjan @maverickws
                                last edited by

                                @maverickws said in No IPv6 after upgrade to 23.01:

                                my ISP (Altice/MEO Portugal) and it said to enable that option.

                                This post : https://forum.meo.pt/internet-fixa-e-movel-11/pfsense-ipv6-155245 ?

                                No "help me" PM's please. Use the forum, the community will thank you.
                                Edit : and where are the logs ??

                                maverickwsM 1 Reply Last reply Reply Quote 0
                                • maverickwsM
                                  maverickws @Gertjan
                                  last edited by maverickws

                                  @gertjan I don't think it was that, was another on a tech forum from around which name I don't recall. but in the end the options are basically those yes.

                                  Just noticing I'm not sending a prefix delegation hint, but been working fine since. And I'd say I don't need it actually, looking at the logs, wouldn't you say?

                                  1 Reply Last reply Reply Quote 0
                                  • Bob.DigB
                                    Bob.Dig LAYER 8 @Gertjan
                                    last edited by

                                    @gertjan said in No IPv6 after upgrade to 23.01:

                                    edit : do you need to check "Do not wait for a RA" ?

                                    Yeah, I would disable that and maybe delete the gateway and start over, just to be sure.

                                    maverickwsM 1 Reply Last reply Reply Quote 0
                                    • S
                                      SteveITS Galactic Empire @maverickws
                                      last edited by

                                      @maverickws To help rule out a config problem you could try resetting to a default config, see if it's still an issue. If it works, save a copy of that working config, and compare to your saved/backup config. If it's still a problem, just restore your old config.

                                      I totally get "but it used to work"...23.01 skipped an entire FreeBSD version so could well have different behavior. For instance unbound set to forward, with DNSSEC enabled, seems to be causing problems for people now. IPv6 isn't broken for everyone which implies it's something specific to the people having problems.

                                      Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
                                      Upvote 👍 helpful posts!

                                      Bob.DigB 1 Reply Last reply Reply Quote 0
                                      • Bob.DigB
                                        Bob.Dig LAYER 8 @SteveITS
                                        last edited by

                                        @steveits said in No IPv6 after upgrade to 23.01:

                                        For instance unbound set to forward, with DNSSEC enabled, seems to be causing problems for people now.

                                        But that is only with quad9 I guess, working here fine with google and cloudflare.

                                        1 Reply Last reply Reply Quote 0
                                        • maverickwsM
                                          maverickws @Bob.Dig
                                          last edited by maverickws

                                          @bob-dig You know you don't "delete" dynamic gateways, right? Because, well, how interface is configured and DHCP.

                                          And by the way, stop with the "it's working here". Your config isn't everyone's config. There isn't ONE config only. There are many variables, different ISP's, different modes.

                                          Just saying "its working here" is just annoying.

                                          I rebooted after removing the option "do not wait for RA" and it didn't really make a difference. I get the IPv6 addresses the same, and nothing else.

                                          @SteveITS I could if I had the time right now or other similar hardware where I could do AB testing. I will try to do that test, but I got no timetable for it.

                                          It seems to me that this release has been poorly tested, specially in what concerns IPv6.

                                          1 Reply Last reply Reply Quote 2
                                          • M
                                            mhillmann
                                            last edited by mhillmann

                                            My issue here is: the ISP honors DHCPv6c giving me an IPV6 address on the WAN interface and a delegation to apply on a track interface. Both show up correctly on the matching interfaces. BUT: the RA announcement from the ISP does not follow the RFC convention of setting the "O" or "M" flags on the RA packet when DHCPv6 is available. Thus rtsold() does NOT invoke the -M or -O scripts resulting in gateway of the relevant interface not being defined/assigend (stuck in "dynamic"), dpinger not running and no default route assigned or the interface not eligible in a gateway group. The strange thing is that it worked up to version 22.05 with this same ISP, ceasing to function with the recent 23.01 update. I suspect the inner workings of rtsold() changed with FreeBSD 14 (current), but cannot find any references to any relevant changes.
                                            Another ISP which honors the M+O flags works fine on the same router...
                                            BTW, IPv4 with the troublesome ISP works OK, so no connectivity issue.

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