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

    WAN_DHCP6 Stuck Pending / Unknown

    2.5 Development Snapshots (Retired)
    7
    35
    6.6k
    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.
    • B
      bimmerdriver
      last edited by

      I cleared the logs and rebooted. Logs for dhclient and dhcp6c are below. (Skipped dhcpd, since it's working.)

      2.4.5

      May 19 17:32:57	dhcp6c	16051	got an expected reply, sleeping.
May 19 17:32:57	dhcp6c	16051	removing server (ID: 00:03:00:01:0c:a4:02:29:50:01)
May 19 17:32:57	dhcp6c	16051	removing an event on hn0, state=REQUEST
May 19 17:32:57	dhcp6c	16051	script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh" terminated
May 19 17:32:57	dhcp6c	40435	dhcp6c renew, no change - bypassing update on hn0
May 19 17:32:57	dhcp6c	16051	executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh
May 19 17:32:57	dhcp6c	16051	add an address 2001:569:74b4:9200:215:5dff:fe67:5b1c/64 on hn1
May 19 17:32:57	dhcp6c	16051	create a prefix 2001:569:74b4:9200::/56 pltime=14400, vltime=14700
May 19 17:32:57	dhcp6c	16051	make an IA: PD-0
May 19 17:32:57	dhcp6c	16051	nameserver[1] 2001:568:ff09:10b::122
May 19 17:32:57	dhcp6c	16051	nameserver[0] 2001:568:ff09:10a::55
May 19 17:32:57	dhcp6c	16051	dhcp6c Received REQUEST
May 19 17:32:57	dhcp6c	16051	get DHCP option DNS, len 32
May 19 17:32:57	dhcp6c	16051	IA_PD prefix: 2001:569:74b4:9200::/56 pltime=14400 vltime=14700
May 19 17:32:57	dhcp6c	16051	get DHCP option IA_PD prefix, len 25
May 19 17:32:57	dhcp6c	16051	IA_PD: ID=0, T1=7200, T2=10800
May 19 17:32:57	dhcp6c	16051	get DHCP option IA_PD, len 41
May 19 17:32:57	dhcp6c	16051	DUID: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 17:32:57	dhcp6c	16051	get DHCP option client ID, len 14
May 19 17:32:57	dhcp6c	16051	DUID: 00:03:00:01:0c:a4:02:29:50:01
May 19 17:32:57	dhcp6c	16051	get DHCP option server ID, len 10
May 19 17:32:57	dhcp6c	16051	receive reply from fe80::ea4:2ff:fe29:5001%hn0 on hn0
May 19 17:32:57	dhcp6c	16051	reset a timer on hn0, state=REQUEST, timeo=0, retrans=909
May 19 17:32:57	dhcp6c	16051	send request to ff02::1:2%hn0
May 19 17:32:57	dhcp6c	16051	set IA_PD
May 19 17:32:57	dhcp6c	16051	set IA_PD prefix
May 19 17:32:57	dhcp6c	16051	set option request (len 4)
May 19 17:32:57	dhcp6c	16051	set elapsed time (len 2)
May 19 17:32:57	dhcp6c	16051	set server ID (len 10)
May 19 17:32:57	dhcp6c	16051	set client ID (len 14)
May 19 17:32:57	dhcp6c	16051	a new XID (27d8de) is generated
May 19 17:32:57	dhcp6c	16051	Sending Request
May 19 17:32:57	dhcp6c	16051	picked a server (ID: 00:03:00:01:0c:a4:02:29:50:01)
May 19 17:32:56	dhcp6c	16051	reset timer for hn0 to 0.989263
May 19 17:32:56	dhcp6c	16051	server ID: 00:03:00:01:0c:a4:02:29:50:01, pref=-1
May 19 17:32:56	dhcp6c	16051	get DHCP option DNS, len 32
May 19 17:32:56	dhcp6c	16051	IA_PD prefix: 2001:569:74b4:9200::/56 pltime=14400 vltime=14700
May 19 17:32:56	dhcp6c	16051	get DHCP option IA_PD prefix, len 25
May 19 17:32:56	dhcp6c	16051	IA_PD: ID=0, T1=7200, T2=10800
May 19 17:32:56	dhcp6c	16051	get DHCP option IA_PD, len 41
May 19 17:32:56	dhcp6c	16051	DUID: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 17:32:56	dhcp6c	16051	get DHCP option client ID, len 14
May 19 17:32:56	dhcp6c	16051	DUID: 00:03:00:01:0c:a4:02:29:50:01
May 19 17:32:56	dhcp6c	16051	get DHCP option server ID, len 10
May 19 17:32:56	dhcp6c	16051	receive advertise from fe80::ea4:2ff:fe29:5001%hn0 on hn0
May 19 17:32:56	dhcp6c	16051	reset a timer on hn0, state=SOLICIT, timeo=0, retrans=1091
May 19 17:32:56	dhcp6c	16051	send solicit to ff02::1:2%hn0
May 19 17:32:56	dhcp6c	16051	set IA_PD
May 19 17:32:56	dhcp6c	16051	set option request (len 4)
May 19 17:32:56	dhcp6c	16051	set elapsed time (len 2)
May 19 17:32:56	dhcp6c	16051	set client ID (len 14)
May 19 17:32:56	dhcp6c	16051	a new XID (9f70f4) is generated
May 19 17:32:56	dhcp6c	16051	Sending Solicit
May 19 17:32:55	dhcp6c	16051	reset a timer on hn0, state=INIT, timeo=0, retrans=891
May 19 17:32:55	dhcp6c	15719	called
May 19 17:32:55	dhcp6c	15719	called
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>end of closure [}] (1)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>end of closure [}] (1)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>[8] (1)
May 19 17:32:55	dhcp6c	15719	<3>[sla-len] (7)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>[0] (1)
May 19 17:32:55	dhcp6c	15719	<3>[sla-id] (6)
May 19 17:32:55	dhcp6c	15719	<3>begin of closure [{] (1)
May 19 17:32:55	dhcp6c	15719	<5>[hn1] (3)
May 19 17:32:55	dhcp6c	15719	<3>[prefix-interface] (16)
May 19 17:32:55	dhcp6c	15719	<13>begin of closure [{] (1)
May 19 17:32:55	dhcp6c	15719	<13>[0] (1)
May 19 17:32:55	dhcp6c	15719	<13>[pd] (2)
May 19 17:32:55	dhcp6c	15719	<3>[id-assoc] (8)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>end of closure [}] (1)
May 19 17:32:55	dhcp6c	15719	<3>comment [# we'd like nameservers and RTSOLD to do all the work] (53)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>["/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh"] (46)
May 19 17:32:55	dhcp6c	15719	<3>[script] (6)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>[domain-name] (11)
May 19 17:32:55	dhcp6c	15719	<3>[request] (7)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>[domain-name-servers] (19)
May 19 17:32:55	dhcp6c	15719	<3>[request] (7)
May 19 17:32:55	dhcp6c	15719	<3>comment [# request prefix delegation] (27)
May 19 17:32:55	dhcp6c	15719	<3>end of sentence [;] (1)
May 19 17:32:55	dhcp6c	15719	<3>[0] (1)
May 19 17:32:55	dhcp6c	15719	<3>[ia-pd] (5)
May 19 17:32:55	dhcp6c	15719	<3>[send] (4)
May 19 17:32:55	dhcp6c	15719	<3>begin of closure [{] (1)
May 19 17:32:55	dhcp6c	15719	<5>[hn0] (3)
May 19 17:32:55	dhcp6c	15719	<3>[interface] (9)
May 19 17:32:55	dhcp6c	15719	skip opening control port
May 19 17:32:55	dhcp6c	15719	failed initialize control message authentication
May 19 17:32:55	dhcp6c	15719	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
May 19 17:32:55	dhcp6c	15719	extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 17:32:52	dhclient	12389	Creating resolv.conf
May 19 17:32:52	dhclient	12222	Adding new routes to interface: hn0
May 19 17:32:52	dhclient	12115	New Routers (hn0): 154.20.116.1
May 19 17:32:52	dhclient	11789	New Broadcast Address (hn0): 154.20.119.255
May 19 17:32:52	dhclient	11529	New Subnet Mask (hn0): 255.255.252.0
May 19 17:32:52	dhclient	11246	New IP Address (hn0): 154.20.118.82
May 19 17:32:52	dhclient	10963	ifconfig hn0 inet 154.20.118.82 netmask 255.255.252.0 broadcast 154.20.119.255
May 19 17:32:52	dhclient	10759	Starting add_new_address()
May 19 17:32:52	dhclient	10327	BOUND
May 19 17:32:51	dhclient	9747	ARPCHECK
May 19 17:32:49	dhclient	6902	ARPSEND
May 19 17:32:49	dhclient	5628	PREINIT

      2.5.0

      May 19 21:22:12	dhcp6c	14771	got an expected reply, sleeping.
May 19 21:22:12	dhcp6c	14771	removing server (ID: 00:03:00:01:0c:a4:02:29:50:01)
May 19 21:22:12	dhcp6c	14771	removing an event on hn0, state=REQUEST
May 19 21:22:12	dhcp6c	14771	script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh" terminated
May 19 21:22:12	dhcp6c	39547	dhcp6c renew, no change - bypassing update on hn0
May 19 21:22:12	dhcp6c	14771	executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh
May 19 21:22:12	dhcp6c	14771	add an address 2001:569:74bd:2600:215:5dff:fe67:5b1c/64 on hn1
May 19 21:22:12	dhcp6c	14771	create a prefix 2001:569:74bd:2600::/56 pltime=14400, vltime=14700
May 19 21:22:12	dhcp6c	14771	make an IA: PD-0
May 19 21:22:12	dhcp6c	14771	nameserver[1] 2001:568:ff09:10b::122
May 19 21:22:12	dhcp6c	14771	nameserver[0] 2001:568:ff09:10a::55
May 19 21:22:12	dhcp6c	14771	dhcp6c Received REQUEST
May 19 21:22:12	dhcp6c	14771	get DHCP option DNS, len 32
May 19 21:22:12	dhcp6c	14771	IA_PD prefix: 2001:569:74bd:2600::/56 pltime=14400 vltime=14700
May 19 21:22:12	dhcp6c	14771	get DHCP option IA_PD prefix, len 25
May 19 21:22:12	dhcp6c	14771	IA_PD: ID=0, T1=7200, T2=10800
May 19 21:22:12	dhcp6c	14771	get DHCP option IA_PD, len 41
May 19 21:22:12	dhcp6c	14771	DUID: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 21:22:12	dhcp6c	14771	get DHCP option client ID, len 14
May 19 21:22:12	dhcp6c	14771	DUID: 00:03:00:01:0c:a4:02:29:50:01
May 19 21:22:12	dhcp6c	14771	get DHCP option server ID, len 10
May 19 21:22:12	dhcp6c	14771	receive reply from fe80::ea4:2ff:fe29:5001%hn0 on hn0
May 19 21:22:11	dhcp6c	14771	reset a timer on hn0, state=REQUEST, timeo=0, retrans=909
May 19 21:22:11	dhcp6c	14771	send request to ff02::1:2%hn0
May 19 21:22:11	dhcp6c	14771	set IA_PD
May 19 21:22:11	dhcp6c	14771	set IA_PD prefix
May 19 21:22:11	dhcp6c	14771	set option request (len 4)
May 19 21:22:11	dhcp6c	14771	set elapsed time (len 2)
May 19 21:22:11	dhcp6c	14771	set server ID (len 10)
May 19 21:22:11	dhcp6c	14771	set client ID (len 14)
May 19 21:22:11	dhcp6c	14771	a new XID (a08807) is generated
May 19 21:22:11	dhcp6c	14771	Sending Request
May 19 21:22:11	dhcp6c	14771	picked a server (ID: 00:03:00:01:0c:a4:02:29:50:01)
May 19 21:22:10	dhcp6c	14771	reset timer for hn0 to 0.990555
May 19 21:22:10	dhcp6c	14771	server ID: 00:03:00:01:0c:a4:02:29:50:01, pref=-1
May 19 21:22:10	dhcp6c	14771	get DHCP option DNS, len 32
May 19 21:22:10	dhcp6c	14771	IA_PD prefix: 2001:569:74bd:2600::/56 pltime=14400 vltime=14700
May 19 21:22:10	dhcp6c	14771	get DHCP option IA_PD prefix, len 25
May 19 21:22:10	dhcp6c	14771	IA_PD: ID=0, T1=7200, T2=10800
May 19 21:22:10	dhcp6c	14771	get DHCP option IA_PD, len 41
May 19 21:22:10	dhcp6c	14771	DUID: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 21:22:10	dhcp6c	14771	get DHCP option client ID, len 14
May 19 21:22:10	dhcp6c	14771	DUID: 00:03:00:01:0c:a4:02:29:50:01
May 19 21:22:10	dhcp6c	14771	get DHCP option server ID, len 10
May 19 21:22:10	dhcp6c	14771	receive advertise from fe80::ea4:2ff:fe29:5001%hn0 on hn0
May 19 21:22:10	dhcp6c	14771	reset a timer on hn0, state=SOLICIT, timeo=0, retrans=1091
May 19 21:22:10	dhcp6c	14771	send solicit to ff02::1:2%hn0
May 19 21:22:10	dhcp6c	14771	set IA_PD
May 19 21:22:10	dhcp6c	14771	set option request (len 4)
May 19 21:22:10	dhcp6c	14771	set elapsed time (len 2)
May 19 21:22:10	dhcp6c	14771	set client ID (len 14)
May 19 21:22:10	dhcp6c	14771	a new XID (989c4c) is generated
May 19 21:22:10	dhcp6c	14771	Sending Solicit
May 19 21:22:09	dhcp6c	14771	reset a timer on hn0, state=INIT, timeo=0, retrans=891
May 19 21:22:09	dhcp6c	14708	called
May 19 21:22:09	dhcp6c	14708	called
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>end of closure [}] (1)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>end of closure [}] (1)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>[8] (1)
May 19 21:22:09	dhcp6c	14708	<3>[sla-len] (7)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>[0] (1)
May 19 21:22:09	dhcp6c	14708	<3>[sla-id] (6)
May 19 21:22:09	dhcp6c	14708	<3>begin of closure [{] (1)
May 19 21:22:09	dhcp6c	14708	<5>[hn1] (3)
May 19 21:22:09	dhcp6c	14708	<3>[prefix-interface] (16)
May 19 21:22:09	dhcp6c	14708	<13>begin of closure [{] (1)
May 19 21:22:09	dhcp6c	14708	<13>[0] (1)
May 19 21:22:09	dhcp6c	14708	<13>[pd] (2)
May 19 21:22:09	dhcp6c	14708	<3>[id-assoc] (8)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>end of closure [}] (1)
May 19 21:22:09	dhcp6c	14708	<3>comment [# we'd like nameservers and RTSOLD to do all the work] (53)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>["/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh"] (46)
May 19 21:22:09	dhcp6c	14708	<3>[script] (6)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>[domain-name] (11)
May 19 21:22:09	dhcp6c	14708	<3>[request] (7)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>[domain-name-servers] (19)
May 19 21:22:09	dhcp6c	14708	<3>[request] (7)
May 19 21:22:09	dhcp6c	14708	<3>comment [# request prefix delegation] (27)
May 19 21:22:09	dhcp6c	14708	<3>end of sentence [;] (1)
May 19 21:22:09	dhcp6c	14708	<3>[0] (1)
May 19 21:22:09	dhcp6c	14708	<3>[ia-pd] (5)
May 19 21:22:09	dhcp6c	14708	<3>[send] (4)
May 19 21:22:09	dhcp6c	14708	<3>begin of closure [{] (1)
May 19 21:22:09	dhcp6c	14708	<5>[hn0] (3)
May 19 21:22:09	dhcp6c	14708	<3>[interface] (9)
May 19 21:22:09	dhcp6c	14708	skip opening control port
May 19 21:22:09	dhcp6c	14708	failed initialize control message authentication
May 19 21:22:09	dhcp6c	14708	failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory
May 19 21:22:09	dhcp6c	14708	extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:26:54:a4:d0:00:15:5d:67:5b:1b
May 19 21:22:06	dhclient	9284	Creating resolv.conf
May 19 21:22:06	dhclient	9226	Adding new routes to interface: hn0
May 19 21:22:06	dhclient	9002	New Routers (hn0): 154.20.116.1
May 19 21:22:06	dhclient	8886	New Broadcast Address (hn0): 154.20.119.255
May 19 21:22:06	dhclient	8758	New Subnet Mask (hn0): 255.255.252.0
May 19 21:22:06	dhclient	8537	New IP Address (hn0): 154.20.118.82
May 19 21:22:06	dhclient	7913	ifconfig hn0 inet 154.20.118.82 netmask 255.255.252.0 broadcast 154.20.119.255
May 19 21:22:06	dhclient	7623	Starting add_new_address()
May 19 21:22:06	dhclient	7224	REBOOT
May 19 21:22:06	dhclient	5605	PREINIT
      1 Reply Last reply Reply Quote 1
      • w0wW
        w0w
        last edited by

        I see no difference.

        Can you answer those questions that @jimp asked in another topic:

        We need to know more about what you're experiencing.
        Is it failing on WAN? On LAN?
        Do you use DHCP for WAN? On LAN? Static?
        Does pfSense get an IPv6 address? Do clients?
        What does the IPv6 routing table look like?
        That sort of stuff, plus an idea of how your setup is configured in general for IPv6 (Interface IPv6 settings, DHCPv6 settings you are using, and so on).

        I think route tables you can get by netstat -r and you have already answered last question about settings.

        B 1 Reply Last reply Reply Quote 0
        • B
          bimmerdriver @w0w
          last edited by

          @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

          I see no difference.

          Can you answer those questions that @jimp asked in another topic:

          We need to know more about what you're experiencing.
          Is it failing on WAN? On LAN?
          Do you use DHCP for WAN? On LAN? Static?
          Does pfSense get an IPv6 address? Do clients?
          What does the IPv6 routing table look like?
          That sort of stuff, plus an idea of how your setup is configured in general for IPv6 (Interface IPv6 settings, DHCPv6 settings you are using, and so on).

          I think route tables you can get by netstat -r and you have already answered last question about settings.

          I think the original post answers most of the questions. Aside from the gateway being stuck pending / unknown, the only other thing that may be notable is the gateway status for 2.5.0 shows the address as ~, whereas it shows the link-local address for 2.4.5. This seems strange, since pfsense has the gateway address, otherwise I'm not sure how IPv6 would not be working. (It's used in the default route.)

          Also, there is a slight difference in the routing tables for 2.4.5 and 2.5.0.

          2.4.5

          Shell Output - netstat -W -r
Routing tables

Internet:
Destination        Gateway            Flags       Use    Mtu      Netif Expire
default            d162-156-4-1.bchsia.telus.net UGS     3206   1500        hn0
localhost          link#2             UH           55  16384        lo0
162.156.4.0/22     link#5             U           311   1500        hn0
d162-156-6-212.bchsia.telus.net link#5 UHS          0  16384        lo0
192.168.1.0/24     link#6             U          1592   1500        hn1
pfSense            link#6             UHS           0  16384        lo0

Internet6:
Destination        Gateway            Flags       Use    Mtu    Netif Expire
default            fe80::ea4:2ff:fe29:5001%hn0 UG     1351   1500      hn0
localhost          link#2             UH            0  16384      lo0
node-1w7jr9qla9jg28ewy6wmg3aio.ipv6.telus.net link#6 U           625   1500      hn1
pfSense            link#6             UHS           0  16384      lo0
fe80::ea4:2ff:fe29:5001 fe80::ea4:2ff:fe29:5001%hn0 UGHS        0   1500      hn0
fe80::%lo0/64      link#2             U             0  16384      lo0
fe80::1%lo0        link#2             UHS           0  16384      lo0
fe80::%hn0/64      link#5             U           301   1500      hn0
fe80::215:5dff:fe67:5b09%hn0 link#5   UHS           0  16384      lo0
fe80::%hn1/64      link#6             U            16   1500      hn1
fe80::1:1%hn1      link#6             UHS           0  16384      lo0

          2.5.0

          Shell Output - netstat -W -r
Routing tables

Internet:
Destination        Gateway            Flags       Use    Mtu      Netif Expire
default            d154-20-116-1.bchsia.telus.net UGS    69943   1500        hn0
localhost          link#1             UH          176  16384        lo0
154.20.116.0/22    link#5             U        293292   1500        hn0
d154-20-118-82.bchsia.telus.net link#5 UHS          0  16384        lo0
192.168.1.0/24     link#6             U        193774   1500        hn1
pfSense            link#6             UHS           0  16384        lo0

Internet6:
Destination        Gateway            Flags       Use    Mtu    Netif Expire
default            fe80::ea4:2ff:fe29:5001%hn0 UG    16094   1500      hn0
localhost          link#1             UH            0  16384      lo0
node-1w7jr9ql9x8i509sb93jlqy2o.ipv6.telus.net link#6 U         88728   1500      hn1
pfSense            link#6             UHS           0  16384      lo0
fe80::%lo0/64      link#1             U             0  16384      lo0
fe80::1%lo0        link#1             UHS           0  16384      lo0
fe80::%hn0/64      link#5             U          2440   1500      hn0
fe80::215:5dff:fe67:5b1b%hn0 link#5   UHS           0  16384      lo0
fe80::%hn1/64      link#6             U           176   1500      hn1
fe80::1:1%hn1      link#6             UHS           0  16384      lo0
fe80::215:5dff:fe67:5b1c%hn1 link#6   UHS           0  16384      lo0
          w0wW 1 Reply Last reply Reply Quote 2
          • w0wW
            w0w @bimmerdriver
            last edited by

            @bimmerdriver
            Do you remember what 2.5 build you have used before you found this problem?
            I am not sure, but there are several dhcpv6 related changes in the end of Aprill, before system moved to stable branch...

            B 1 Reply Last reply Reply Quote 0
            • B
              bimmerdriver @w0w
              last edited by

              @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

              @bimmerdriver
              Do you remember what 2.5 build you have used before you found this problem?
              I am not sure, but there are several dhcpv6 related changes in the end of Aprill, before system moved to stable branch...

              Unfortunately, no, and I forgot to checkpoint the VM before I upgraded. If older versions were available, I would go through them until I found which one introduced the problem. It seems very likely that the problem I'm having is the same problem that was identified in the thread Ipv6 not working build 2.5.0.a.20200428.1204, so it's a good bet the change is in build 2.5.0.a.20200428.1204 or possibly earlier, depending on how long between updates the other person was.

              1 Reply Last reply Reply Quote 0
              • w0wW
                w0w
                last edited by

                https://github.com/pfsense/pfsense/commit/c01fa17a2748d2803d025fa727e484ed205b9537
                https://redmine.pfsense.org/issues/9634
                Not sure is it related, but you can try to revert those changes...

                B 1 Reply Last reply Reply Quote 1
                • B
                  bimmerdriver @w0w
                  last edited by

                  @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

                  https://github.com/pfsense/pfsense/commit/c01fa17a2748d2803d025fa727e484ed205b9537
                  https://redmine.pfsense.org/issues/9634
                  Not sure is it related, but you can try to revert those changes...

                  Reverting the patch appears to have fixed the problem. The gateway is online. I'll kick it around a bit for a bit and report back.

                  1 Reply Last reply Reply Quote 0
                  • B
                    bimmerdriver
                    last edited by

                    I used wireshark to capture icmpv6 and dhcpv6 packets on the wan interface.

                    With the patch uninstalled, the sequence is the following:

                    send dhcpv6 solicit
                    receive dhcpv6 advertise
                    send dhcpv6 request
                    receive dhcpv6 reply
                    send icmpv6 router solicitation
                    receive icmpv6 router advertisement

                    With the patch installed, the sequence is the following:

                    send dhcpv6 solicit
                    receive dhcpv6 advertise
                    send dhcpv6 request
                    receive dhcpv6 reply

                    The router never sends the icmpv6 router solicitation, so it never receives the router advertisement.

                    I hope that helps.

                    1 Reply Last reply Reply Quote 1
                    • w0wW
                      w0w
                      last edited by

                      I suggest to write about all the finds on the redmine
                      I hope somebody will fix this bug soon.

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        bimmerdriver @w0w
                        last edited by

                        @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

                        I suggest to write about all the finds on the redmine
                        I hope somebody will fix this bug soon.

                        I already did. Thanks for the help.👍

                        B 1 Reply Last reply Reply Quote 0
                        • B
                          bimmerdriver @bimmerdriver
                          last edited by

                          @bimmerdriver said in WAN_DHCP6 Stuck Pending / Unknown:

                          @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

                          I suggest to write about all the finds on the redmine
                          I hope somebody will fix this bug soon.

                          I already did. Thanks for the help.👍

                          @jimp Should I open a new issue in Redmine for this problem?

                          1 Reply Last reply Reply Quote 0
                          • B
                            bimmerdriver
                            last edited by

                            A fix for this issue is in the latest snapshot and I confirm it works.

                            Thanks @jimp . 👍

                            1 Reply Last reply Reply Quote 0
                            • T
                              tbclark3
                              last edited by

                              I just upgraded to 2.4.5-release-p1 and I have exactly the same problem. The ipv6 gateway is stuck on status unknown. I made no other configuration changes, nor any other changes.

                              1 Reply Last reply Reply Quote 0
                              • F
                                fragged
                                last edited by

                                My WAN interface is still showing:
                                WAN_DHCP6
                                ~ Pending Pending Pending Unknown

                                On:
                                2.5.0-DEVELOPMENT (amd64)
                                built on Thu Jul 16 01:02:54 EDT 2020
                                FreeBSD 12.1-STABLE

                                Previous posts indicate that the issue was fixed, but mine's still not working since whichever update broke dhcpv6. Any ideas how to solve this? System Logs / DHCP shows nothing for v6 just v4.

                                1 Reply Last reply Reply Quote 0
                                • M
                                  monroe
                                  last edited by

                                  I'm seeing the same issue since updating to 2.4.5p1. My ISP is Comcast/Xfinity, and I'm using their native dual-stack IPv4/IPv6 service. The v4 status shows correctly, but v6 just shows Pending/Unknown.

                                  If I go into System > Routing > Gateways, edit the IPv6 gateway, and disable/re-enable gateway monitoring for that interface, it seems to fix the problem temporarily, but at some point it recurs (I haven't determined exactly what causes it to recur yet.)

                                  1 Reply Last reply Reply Quote 0
                                  • w0wW
                                    w0w
                                    last edited by

                                    You can revert those patches one by one with help of "System patches" package.

                                    1. Install package "System patches"
                                    2. Create two patches, using the commit ID's provided in https://redmine.pfsense.org/issues/9634
                                      the first one should be
                                      19fe32b0fe32faf290ea2b74c005c165579277bf
                                      and the second
                                      8788b0613a66e48ff4da45f4228bda481c37f7a9
                                      When creating fill commit ID and enter any description for the patch and press "SAVE" button.
                                      bla-bla1.jpg
                                      When patches are created you will see fetch button in the patch list, press fetch and then after patch is downloaded,
                                      fetch.jpg
                                      you will see that Revert button is appeared on one of them,
                                      revert.jpg
                                      press it and you will get Revert button on the second patch also, press it also and you should have original 2.4.5 non p1 version of file.
                                      Check it and if you have some new information report it back 😊
                                    F T 2 Replies Last reply Reply Quote 0
                                    • F
                                      fragged @w0w
                                      last edited by

                                      @w0w Thanks for the reply. In my case it seems like with changes done to pfSense I now need to check the "Do not wait for a RA" setting on DHCP6 Client Configuration. After enabling that option I get IPv6 on the interface again status is shown correctly without reverting the patches.

                                      1 Reply Last reply Reply Quote 1
                                      • T
                                        tbclark3 @w0w
                                        last edited by

                                        @w0w, I backed up the configuration, reverted both patches, and rebooted. The WAN_DHCP6 status was slow to update but eventually correctly showed "Online"; however, and radvd was correctly advertising the route. However, I had no ipv6 connectivity from clients. I reverted to the saved configuration, rebooted, and this time the WAN_DHCP6 status immediately said "Online" and I have ipv6 connectivity from clients. The "System patches" package got uninstalled by the restoration of the configuration, and as best I can tell, the patch reversions did too. Nevertheless, it has been working correctly for several hours now.

                                        w0wW 1 Reply Last reply Reply Quote 0
                                        • w0wW
                                          w0w @tbclark3
                                          last edited by

                                          @tbclark3
                                          I do not think it is reverting the patches, when you uninstall package or restore configuration that does not use this package, you can just test it by installing package again, see what happens and report back.
                                          May be it just needed reboot to complete reload of those un-patched files.

                                          You can also test this "Do not wait for a RA" setting, that was found by @fragged as working solution.

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            bimmerdriver @w0w
                                            last edited by

                                            @w0w said in WAN_DHCP6 Stuck Pending / Unknown:

                                            @tbclark3
                                            I do not think it is reverting the patches, when you uninstall package or restore configuration that does not use this package, you can just test it by installing package again, see what happens and report back.
                                            May be it just needed reboot to complete reload of those un-patched files.

                                            You can also test this "Do not wait for a RA" setting, that was found by @fragged as working solution.

                                            The "Do not wait for a RA" setting causes pfsense to send the DHCP solicit before the RS. If your ISP gateway requires this, it will not delegate a prefix you use the setting. If your ISP gateway doesn't require this, pfsense may or may get a prefix. Some gateways don't care about the order. The best way to determine if this setting is required is to use wireshark to watch sequence of messages.

                                            T 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post