25.03.b.20250306.0140 - IPv6 issues
-
First impression from 25.03.b.20250306.0140
Between the first 25.03 beta and the 25.03.b.20250306.0140 that just got pushed out something broke IPv6
All instances that use pppoe show gateway status "pending". Restarting dpinger does not resolve it. Putting in an external monitoring IP such as 2001:4860:4860::8844 makes it work
Other instances that do not use pppoe fail to request prefix delegation from upstream. Overall 25.03.b.20250306.0140 seems to break a bunch of IPv6 stuff.
-
Same for me… also my PPPoE and dpinger are spamming logs with
2025-03-25 06:01:32.991776+02:00 dpinger 97674 exiting on signal 15 2025-03-25 06:01:32.851597+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:01:32.350803+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:01:31.818882+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:01:31.312600+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:01:30.810837+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:01:30.279345+02:00 dpinger 97674 WAN_PPPOE 8.8.4.4: sendto error: 65 2025-03-25 06:00:24.456992+02:00 dpinger 97674 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 999ms loss_alarm 20% alarm_hold 10000ms dest_addr 8.8.4.4 bind_addr xx.52.x1.91 identifier "WAN_PPPOE " 2025-03-25 06:00:24.445960+02:00 dpinger 88209 exiting on signal 15 2025-03-25 06:00:24.205425+02:00 dpinger 88209 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 999ms loss_alarm 20% alarm_hold 10000ms dest_addr 8.8.4.4 bind_addr xx.52.x1.91 identifier "WAN_PPPOE " 2025-03-25 06:00:24.193451+02:00 dpinger 32042 exiting on signal 15 2025-03-25 06:00:23.910031+02:00 dpinger 32042 WAN_PPPOE 8.8.4.4: sendto error: 13 2025-03-25 06:00:00.826550+02:00 dpinger 32042 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 999ms loss_alarm 20% alarm_hold 10000ms dest_addr 8.8.4.4 bind_addr xx.52.x1.91 identifier "WAN_PPPOE " 2025-03-25 06:00:00.817699+02:00 dpinger 46268 exiting on signal 15 2025-03-25 05:59:59.016492+02:00 dpinger 46268 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 999ms loss_alarm 20% alarm_hold 10000ms dest_addr 8.8.4.4 bind_addr xx.52.x1.91 identifier "WAN_PPPOE " 2025-03-25 05:59:59.007333+02:00 dpinger 10592 exiting on signal 15
05:57:55 MONITOR: WAN_PPPOE has packet loss, omitting from routing group failOVERWANS xx.7.29.246|xx.52.x1.91|WAN_PPPOE|0ms|0ms|100%|down|highloss 05:57:56 MONITOR: WAN_PPPOE is available now, adding to routing group failOVERWANS xx.7.29.246|xx.52.x1.91|WAN_PPPOE|0.238ms|0.005ms|0.0%|online|none
-
I'm seeing the same (non pppoe connection)
Ping command works tho (so seams normal IPv6 traffic from clients)
Not seeing any dpinger logs for "WAN_DHCP6"
Reverted back to the previous beta for now
-
Thanks for testing! It's an issue with the php module - it will be fixed with the next build.
-
@marcosm
Any patch available or new build will be available soon? -
Can't be patched as normal unfortunately. I'm hoping the next build is available soon but can't say when for certain.
-
@marcosm said in 25.03.b.20250306.0140 - IPv6 issues:
Can't be patched as normal unfortunately. I'm hoping the next build is available soon but can't say when for certain.
Whatever was changed in
25.03-BETA (amd64)
built on Wed Apr 9 22:08:00 UTC 2025broke everything related to IPv6 for us. PPPoE sites show gateway up but can't ping anyone.
DHCP6 sites show gateway down and no default route installed for ::/0
-
25.03-BETA (amd64)
built on Mon Apr 14 18:38:00 UTC 2025
FreeBSD 15.0-CURRENTseems to have resolved some of this.