Gigaclear & ip6 - lose of connectivity after *exactly* 5 minutes
-
Hi -
Running 24.11 of pfSense Plus with all available patches applied.
My (UK) ISP, Gigaclear, has recently enabled v6 (they assign us a /48) across their network. Exactly 5 minutes after v6 is brought up all v6 traffic stops. If I go to Interfaces > WAN and hit 'save', 'apply', v6 works again. For exactly 5 minutes. Rinse and repeat.
I see a fellow customer experiencing the exact same issue here: https://www.ispreview.co.uk/talk/threads/anyone-noticed-if-gigaclear-have-deployed-ipv6.43168/post-411379
Notably, it doesn't matter which options I select in WAN > DHCP6 Configuration, the issue remains. Here are what I believe the relevant parts from my pfSense log. If I have missed any other logs, or outputs which could be helpful, please let me know and I will supply them.
I'm (trying) to raise this up to Gigaclear, will report back if I hear from them.
Is this a BSD / Sense issue, or a 'my ISP' issue?Mar 28 21:20:59 dhcp6c 14051 advertise contains no address/prefix Mar 28 21:20:59 dhcp6c 14051 server ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00, pref=-1 Mar 28 21:20:59 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:20:59 dhcp6c 14051 status code: no addresses Mar 28 21:20:59 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:20:59 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:20:59 dhcp6c 14051 get DHCP option identity association, len 59 Mar 28 21:20:59 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:20:59 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:20:59 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:20:59 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:20:59 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:20:59 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:20:59 dhcp6c 14051 receive advertise from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:20:59 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=7, retrans=117984 Mar 28 21:20:59 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:20:59 dhcp6c 14051 set option request (len 4) Mar 28 21:20:59 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:20:59 dhcp6c 14051 set identity association Mar 28 21:20:59 dhcp6c 14051 set client ID (len 14) Mar 28 21:20:59 dhcp6c 14051 Sending Solicit Mar 28 21:19:58 dhcp6c 14051 advertise contains no address/prefix Mar 28 21:19:58 dhcp6c 14051 server ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00, pref=-1 Mar 28 21:19:58 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:19:58 dhcp6c 14051 status code: no addresses Mar 28 21:19:58 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:19:58 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:19:58 dhcp6c 14051 get DHCP option identity association, len 59 Mar 28 21:19:58 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:19:58 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:19:58 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:19:58 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:19:58 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:19:58 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:19:58 dhcp6c 14051 receive advertise from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:19:58 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=6, retrans=60644 Mar 28 21:19:58 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:19:58 dhcp6c 14051 set option request (len 4) Mar 28 21:19:58 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:19:58 dhcp6c 14051 set identity association Mar 28 21:19:58 dhcp6c 14051 set client ID (len 14) Mar 28 21:19:58 dhcp6c 14051 Sending Solicit Mar 28 21:19:26 dhcp6c 14051 advertise contains no address/prefix Mar 28 21:19:26 dhcp6c 14051 server ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00, pref=-1 Mar 28 21:19:26 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:19:26 dhcp6c 14051 status code: no addresses Mar 28 21:19:26 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:19:26 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:19:26 dhcp6c 14051 get DHCP option identity association, len 59 Mar 28 21:19:26 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:19:26 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:19:26 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:19:26 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:19:26 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:19:26 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:19:26 dhcp6c 14051 receive advertise from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:19:26 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=5, retrans=31512 Mar 28 21:19:26 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:19:26 dhcp6c 14051 set option request (len 4) Mar 28 21:19:26 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:19:26 dhcp6c 14051 set identity association Mar 28 21:19:26 dhcp6c 14051 set client ID (len 14) Mar 28 21:19:26 dhcp6c 14051 Sending Solicit Mar 28 21:19:10 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=4, retrans=16549 Mar 28 21:19:10 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:19:10 dhcp6c 14051 set option request (len 4) Mar 28 21:19:10 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:19:10 dhcp6c 14051 set identity association Mar 28 21:19:10 dhcp6c 14051 set client ID (len 14) Mar 28 21:19:10 dhcp6c 14051 Sending Solicit Mar 28 21:19:02 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=3, retrans=8250 Mar 28 21:19:02 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:19:02 dhcp6c 14051 set option request (len 4) Mar 28 21:19:02 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:19:02 dhcp6c 14051 set identity association Mar 28 21:19:02 dhcp6c 14051 set client ID (len 14) Mar 28 21:19:02 dhcp6c 14051 Sending Solicit Mar 28 21:18:57 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=2, retrans=4286 Mar 28 21:18:57 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:18:57 dhcp6c 14051 set option request (len 4) Mar 28 21:18:57 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:57 dhcp6c 14051 set identity association Mar 28 21:18:57 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:57 dhcp6c 14051 Sending Solicit Mar 28 21:18:55 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=1, retrans=2114 Mar 28 21:18:55 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:18:55 dhcp6c 14051 set option request (len 4) Mar 28 21:18:55 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:55 dhcp6c 14051 set identity association Mar 28 21:18:55 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:55 dhcp6c 14051 Sending Solicit Mar 28 21:18:54 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=0, retrans=1091 Mar 28 21:18:54 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:18:54 dhcp6c 14051 set option request (len 4) Mar 28 21:18:54 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:54 dhcp6c 14051 set identity association Mar 28 21:18:54 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:54 dhcp6c 14051 a new XID (3e2a43) is generated Mar 28 21:18:54 dhcp6c 14051 Sending Solicit Mar 28 21:18:54 dhcp6c 14051 got an expected reply, sleeping. Mar 28 21:18:54 dhcp6c 14051 removing server (ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00) Mar 28 21:18:54 dhcp6c 14051 removing an event on igb0, state=REQUEST Mar 28 21:18:54 dhcp6c 14051 script "/var/etc/dhcp6c_wan_script.sh" terminated Mar 28 21:18:54 dhcp6c 12849 dhcp6c RELEASE, REQUEST or EXIT on igb0 running rc.newwanipv6 Mar 28 21:18:54 dhcp6c 14051 executes /var/etc/dhcp6c_wan_script.sh Mar 28 21:18:54 dhcp6c 14051 reset a timer on igb0, state=INIT, timeo=0, retrans=192 Mar 28 21:18:54 dhcp6c 14051 remove an IA: NA-0 Mar 28 21:18:54 dhcp6c 14051 IA NA-0 is invalidated Mar 28 21:18:54 dhcp6c 14051 status code for NA-0: no addresses Mar 28 21:18:54 dhcp6c 14051 make an IA: NA-0 Mar 28 21:18:54 dhcp6c 14051 add an address 2a06:61c1:ba35:30:6662:66ff:fe21:6b75/64 on igb1.20 Mar 28 21:18:54 dhcp6c 14051 add an address 2a06:61c1:ba35:20:6662:66ff:fe21:6b75/64 on igb1.30 Mar 28 21:18:54 dhcp6c 14051 add an address 2a06:61c1:ba35:10:6662:66ff:fe21:6b75/64 on igb1 Mar 28 21:18:54 dhcp6c 14051 create a prefix 2a06:61c1:ba35::/48 pltime=86400, vltime=86400 Mar 28 21:18:54 dhcp6c 14051 make an IA: PD-0 Mar 28 21:18:54 dhcp6c 14051 nameserver[1] 2a02:fb8:3:300::3 Mar 28 21:18:54 dhcp6c 14051 nameserver[0] 2a02:fb8:2:200::3 Mar 28 21:18:54 dhcp6c 14051 dhcp6c Received REQUEST Mar 28 21:18:54 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:18:54 dhcp6c 14051 IA_PD prefix: 2a06:61c1:ba35::/48 pltime=86400 vltime=39466454569344 Mar 28 21:18:54 dhcp6c 14051 get DHCP option IA_PD prefix, len 25 Mar 28 21:18:54 dhcp6c 14051 IA_PD: ID=0, T1=43200, T2=69120 Mar 28 21:18:54 dhcp6c 14051 get DHCP option IA_PD, len 41 Mar 28 21:18:54 dhcp6c 14051 status code: no addresses Mar 28 21:18:54 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:18:54 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:18:54 dhcp6c 14051 get DHCP option identity association, len 59 Mar 28 21:18:54 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:18:54 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:18:54 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:18:54 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:18:54 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:18:54 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:18:54 dhcp6c 14051 receive reply from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:18:54 dhcp6c 14051 reset a timer on igb0, state=REQUEST, timeo=0, retrans=955 Mar 28 21:18:54 dhcp6c 14051 send request to ff02::1:2%igb0 Mar 28 21:18:54 dhcp6c 14051 set IA_PD Mar 28 21:18:54 dhcp6c 14051 set IA_PD prefix Mar 28 21:18:54 dhcp6c 14051 set option request (len 4) Mar 28 21:18:54 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:54 dhcp6c 14051 set identity association Mar 28 21:18:54 dhcp6c 14051 set status code Mar 28 21:18:54 dhcp6c 14051 set server ID (len 26) Mar 28 21:18:54 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:54 dhcp6c 14051 a new XID (277b97) is generated Mar 28 21:18:54 dhcp6c 14051 Sending Request Mar 28 21:18:54 dhcp6c 14051 picked a server (ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00) Mar 28 21:18:53 dhcp6c 14051 reset timer for igb0 to 0.871864 Mar 28 21:18:53 dhcp6c 14051 server ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00, pref=-1 Mar 28 21:18:53 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:18:53 dhcp6c 14051 IA_PD prefix: 2a06:61c1:ba35::/48 pltime=86400 vltime=39466454569344 Mar 28 21:18:53 dhcp6c 14051 get DHCP option IA_PD prefix, len 25 Mar 28 21:18:53 dhcp6c 14051 IA_PD: ID=0, T1=43200, T2=69120 Mar 28 21:18:53 dhcp6c 14051 get DHCP option IA_PD, len 41 Mar 28 21:18:53 dhcp6c 14051 status code: no addresses Mar 28 21:18:53 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:18:53 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:18:53 dhcp6c 14051 get DHCP option identity association, len 59 Mar 28 21:18:53 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:18:53 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:18:53 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:18:53 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:18:53 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:18:53 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:18:53 dhcp6c 14051 receive advertise from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:18:53 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=1, retrans=2075 Mar 28 21:18:53 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:18:53 dhcp6c 14051 set IA_PD Mar 28 21:18:53 dhcp6c 14051 set option request (len 4) Mar 28 21:18:53 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:53 dhcp6c 14051 set identity association Mar 28 21:18:53 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:53 dhcp6c 14051 Sending Solicit Mar 28 21:18:52 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=0, retrans=1025 Mar 28 21:18:52 dhcp6c 14051 send solicit to ff02::1:2%igb0 Mar 28 21:18:52 dhcp6c 14051 set IA_PD Mar 28 21:18:52 dhcp6c 14051 set option request (len 4) Mar 28 21:18:52 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:52 dhcp6c 14051 set identity association Mar 28 21:18:52 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:52 dhcp6c 14051 a new XID (91e251) is generated Mar 28 21:18:52 dhcp6c 14051 Sending Solicit Mar 28 21:18:52 dhcp6c 14051 reset a timer on igb0, state=INIT, timeo=0, retrans=118 Mar 28 21:18:52 dhcp6c 14051 removing an event on igb0, state=SOLICIT Mar 28 21:18:52 dhcp6c 14051 restarting Mar 28 21:18:51 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=1, retrans=2083 Mar 28 21:18:51 dhcp6c 14051 transmit failed: Network is down Mar 28 21:18:51 dhcp6c 14051 set IA_PD Mar 28 21:18:51 dhcp6c 14051 set option request (len 4) Mar 28 21:18:51 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:51 dhcp6c 14051 set identity association Mar 28 21:18:51 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:51 dhcp6c 14051 Sending Solicit Mar 28 21:18:50 dhcp6c 14051 reset a timer on igb0, state=SOLICIT, timeo=0, retrans=1091 Mar 28 21:18:50 dhcp6c 14051 transmit failed: Network is down Mar 28 21:18:50 dhcp6c 14051 set IA_PD Mar 28 21:18:50 dhcp6c 14051 set option request (len 4) Mar 28 21:18:50 dhcp6c 14051 set elapsed time (len 2) Mar 28 21:18:50 dhcp6c 14051 set identity association Mar 28 21:18:50 dhcp6c 14051 set client ID (len 14) Mar 28 21:18:50 dhcp6c 14051 a new XID (7ed935) is generated Mar 28 21:18:50 dhcp6c 14051 Sending Solicit Mar 28 21:18:49 dhcp6c 14051 reset a timer on igb0, state=INIT, timeo=0, retrans=891 Mar 28 21:18:49 dhcp6c 12104 called Mar 28 21:18:49 dhcp6c 12104 called Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[16] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-len] (7) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[48] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-id] (6) Mar 28 21:18:49 dhcp6c 12104 <3>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <5>[igb1.20] (7) Mar 28 21:18:49 dhcp6c 12104 <3>[prefix-interface] (16) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[16] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-len] (7) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[32] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-id] (6) Mar 28 21:18:49 dhcp6c 12104 <3>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <5>[igb1.30] (7) Mar 28 21:18:49 dhcp6c 12104 <3>[prefix-interface] (16) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[16] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-len] (7) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[16] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[sla-id] (6) Mar 28 21:18:49 dhcp6c 12104 <3>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <5>[igb1] (4) Mar 28 21:18:49 dhcp6c 12104 <3>[prefix-interface] (16) Mar 28 21:18:49 dhcp6c 12104 <13>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <13>[0] (1) Mar 28 21:18:49 dhcp6c 12104 <13>[pd] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[id-assoc] (8) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <13>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <13>[0] (1) Mar 28 21:18:49 dhcp6c 12104 <13>[na] (2) Mar 28 21:18:49 dhcp6c 12104 <3>[id-assoc] (8) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>end of closure [}] (1) Mar 28 21:18:49 dhcp6c 12104 <3>comment [# we'd like some nameservers please] (35) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>["/var/etc/dhcp6c_wan_script.sh"] (31) Mar 28 21:18:49 dhcp6c 12104 <3>[script] (6) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[domain-name] (11) Mar 28 21:18:49 dhcp6c 12104 <3>[request] (7) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[domain-name-servers] (19) Mar 28 21:18:49 dhcp6c 12104 <3>[request] (7) Mar 28 21:18:49 dhcp6c 12104 <3>comment [# request prefix delegation] (27) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[0] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[ia-pd] (5) Mar 28 21:18:49 dhcp6c 12104 <3>[send] (4) Mar 28 21:18:49 dhcp6c 12104 <3>comment [# request stateful address] (26) Mar 28 21:18:49 dhcp6c 12104 <3>end of sentence [;] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[0] (1) Mar 28 21:18:49 dhcp6c 12104 <3>[ia-na] (5) Mar 28 21:18:49 dhcp6c 12104 <3>[send] (4) Mar 28 21:18:49 dhcp6c 12104 <3>begin of closure [{] (1) Mar 28 21:18:49 dhcp6c 12104 <5>[igb0] (4) Mar 28 21:18:49 dhcp6c 12104 <3>[interface] (9) Mar 28 21:18:49 dhcp6c 12104 skip opening control port Mar 28 21:18:49 dhcp6c 12104 failed initialize control message authentication Mar 28 21:18:49 dhcp6c 12104 failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory Mar 28 21:18:49 dhcp6c 12104 extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74
Mar 28 21:24:56 php-fpm 42926 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Mar 28 21:24:56 php-fpm 42926 /rc.newwanipv6: rc.newwanipv6: Info: starting on igb0.
Mar 28 21:25:15 dhcp6c 14051 got an expected reply, sleeping. Mar 28 21:25:15 dhcp6c 14051 removing server (ID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00) Mar 28 21:25:15 dhcp6c 14051 removing an event on igb0, state=REQUEST Mar 28 21:25:15 dhcp6c 14051 script "/var/etc/dhcp6c_wan_script.sh" terminated Mar 28 21:25:15 dhcp6c 45988 dhcp6c RELEASE, REQUEST or EXIT on igb0 running rc.newwanipv6 Mar 28 21:25:15 dhcp6c 14051 executes /var/etc/dhcp6c_wan_script.sh Mar 28 21:25:15 dhcp6c 14051 reset a timer on igb0, state=INIT, timeo=0, retrans=726 Mar 28 21:25:15 dhcp6c 14051 remove an IA: NA-0 Mar 28 21:25:15 dhcp6c 14051 IA NA-0 is invalidated Mar 28 21:25:15 dhcp6c 14051 failed to update an address :: Mar 28 21:25:15 dhcp6c 14051 failed to remove an address on igb0: Can't assign requested address Mar 28 21:25:15 dhcp6c 14051 remove an address :: Mar 28 21:25:15 dhcp6c 14051 create an address :: pltime=0, vltime=34359738368 Mar 28 21:25:15 dhcp6c 14051 make an IA: NA-0 Mar 28 21:25:15 dhcp6c 14051 nameserver[1] 2a02:fb8:3:300::3 Mar 28 21:25:15 dhcp6c 14051 nameserver[0] 2a02:fb8:2:200::3 Mar 28 21:25:15 dhcp6c 14051 dhcp6c Received REQUEST Mar 28 21:25:15 dhcp6c 14051 get DHCP option DNS, len 32 Mar 28 21:25:15 dhcp6c 14051 status code: no addresses Mar 28 21:25:15 dhcp6c 14051 get DHCP option status code, len 43 Mar 28 21:25:15 dhcp6c 14051 IA_NA address: :: pltime=0 vltime=0 Mar 28 21:25:15 dhcp6c 14051 get DHCP option IA address, len 71 Mar 28 21:25:15 dhcp6c 14051 IA_NA: ID=0, T1=0, T2=0 Mar 28 21:25:15 dhcp6c 14051 get DHCP option identity association, len 87 Mar 28 21:25:15 dhcp6c 14051 unknown or unexpected DHCP6 option opt_20, len 0 Mar 28 21:25:15 dhcp6c 14051 get DHCP option opt_20, len 0 Mar 28 21:25:15 dhcp6c 14051 DUID: 00:02:00:00:05:83:34:63:3a:36:64:3a:35:38:3a:38:37:3a:31:37:3a:66:38:00:00:00 Mar 28 21:25:15 dhcp6c 14051 get DHCP option server ID, len 26 Mar 28 21:25:15 dhcp6c 14051 DUID: 00:01:00:01:2f:75:c3:80:64:62:66:21:6b:74 Mar 28 21:25:15 dhcp6c 14051 get DHCP option client ID, len 14 Mar 28 21:25:15 dhcp6c 14051 receive reply from fe80::4e6d:58ff:fe87:1017%igb0 on igb0 Mar 28 21:25:15 dhcp6c 14051 reset a timer on igb0, state=REQUEST, timeo=0, retrans=959 Mar 28 21:25:15 dhcp6c 14051 send request to ff02::1:2%igb0 Mar 28 21:25:15 dhcp6c 14051 set option request (len 4)
-
I took a tcpdump of the window (after 5 minutes) where v6 connectivity breaks. Is this potentially a result of a Liveness Check at the head end that is disconnecting me as Sense is failing to send advertisements back in response to the solicits of the head end? My ISP is IPoE not PPoE if that is of relevance.
I dumped both WAN and LAN when v6 connectivity breaks. ISP says they're not receiving neighbour advertisements back from their solicits, that's what is causing the breakage.
WAN dump: https://pastebin.com/PyEsinPC
LAN dump: https://pastebin.com/D5H3905g -
Your problem may be related to this FreeBSD bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701.
That bug report is lengthy as there is a lot of "discussion" in the thread. I'm not sure that everything discussed in the thread is fully fixed yet in all the FreeBSD branches. I am pretty sure the OPNsense guys did some custom patching of their own to partially address this. At one time there was a long-running thread on their forum site about the issue. I think this became a problem there first probably because IPv6 is more widely deployed and used in European countries where OPNsense is based. IPv6 is not as widely deployed in the U.S. where pfSense is based.
Here are a couple of links to Github referencing the custom patches on the OPNsense side:
https://github.com/opnsense/src/issues/242
https://github.com/opnsense/src/commit/2640600509de99cf6d75d588a6c27461d15809e6The changes required are in the guts of FreeBSD (inside the
pf
code), and thus cannot be fixed without releasing an updated FreeBSD kernel. I am not sure if all of the required fixes are in pfSense Plus now as that source is proprietary. I do see some icmpv6 fixes in the FreeBSD kernel source used for pfSense CE (specifically in the tree for the not-yet-available 2.8 DEVEL snapshot):https://github.com/pfsense/FreeBSD-src/commit/5ab1e5f7e5585558a73b723f07528977a82cee82
-
@bmeeks Many thanks. Yes, I remember this original issue. I'll raise a Redmine later this week to see if I can start some formal investigation on this. I know of multiple pfSense users impacted by this here.
-
Thanks @bmeeks.
A good test would be to upgrade to 25.03-BETA since that includes the fixes and try to reproduce.
-
@marcosm I'll update it when I'm in front of the firewall in late May - hopefully GA is finalised by then. Though, I looked at the release notes for 25.03 and don't see many v6 / RA fixes at all?
-
The release notes for pfSense don't usually include upstream changes/fixes.
-
@marcosm said in Gigaclear & ip6 - lose of connectivity after *exactly* 5 minutes:
Thanks @bmeeks.
A good test would be to upgrade to 25.03-BETA since that includes the fixes and try to reproduce.
Forgot to add, another Gigaclear user is running BSD-14 without seeing these issues when plugged directly to ONT. If it’s an upstream issue, wouldn’t their 14 kernel be impacted?
-
Depends on how recently it's been updated I suppose. If the commits are indeed related to the issue then I'd expect it to be resolved in an updated FreeBSD system.
-
@marcosm another GC customer is on 25.03. Doesn’t fix the issue. We have a real problem here impacting every Gigaclear pfsense customer in GBR.
BTW - Reached out to TAC. Closed as I'm a TAC Lite customer. SIGH. I pay a yearly subscription for pfSense and still receive ZERO support when reporting a bug despite being a paying customer.
-
I can recreate this.
pfSense does not respond to incoming Neighbor Solicitation messages when the source IPv6 GUA is outside any local subnet and not link-local.
In this case, it leads to the ISP ceasing IPv6 traffic after approximately 5 minutes of no response to multiple solicitation requests. DHCPv6 re-solicitation restarts this timer; interface restart temporarily resolves.
pfSense appears to be filtering or not processing Neighbor Solicitations based on the source IP address not being link-local or within the target's subnet, despite the target address frield contained within the ICMPv6 packet being the link-local address. This behavior may be exacerbated by multi-WAN configurations where the interface is not the default route.
When the source IP is a known subnet or link-local, pfSense does correctly process the Neighbor Solicitation and respond.
-
I beleive the root cause of this is when no GUA is provided for the WAN, so it is left with only a link-local address and a deligated prefix. But the key here is, it has no GUA bound to its interface.
When pfsense attempts to respond with a neighbor advertisement, it picks a LAN GUA address and not the WAN link-local address.
A way to recreate this is to have two IPv6 WANs, ensure no GUA on WAN1 and do not delegate any IPv6 suvbets from WAN1 to any LAN. In other words, give all LAN's a subnet outside any deligated range of WAN1 but inside the delegated range of WAN2. It means WAN1 is somewhat pointless at this point, but that is ok for this test.
On WAN1, when a neighbour soliciation request is received from a GUA address to WAN1 local-link address - pfsense attempts to reply with an advertisement but instead of using the local-link address of WAN1 as the source, it picks one of the LAN's interface addresses (remember this is nothing to do with WAN1) and sends an advertisement from this souce IP.
What happens to that neighbor advertisment varies depending on other firewall/routing.static route rules, i've managed to see it attempt to send out WAN2 for example. Hence WAN1 never see's it.
When a WAN only has a local-link IPv6 address, pfsense should be using this as the source address of neighbor advertisement messages, not picking a random LAN interface as the source address.
I beleive this to be the root cause and a bug.
A workaround is to add a IP Alias on the WAN for a /128 GUA from somewhere within the /48 delegated prefix. However, there should not be a need for a router to have a GUA with IPv6 .