DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208
-
Not grabbing the bunting just yet but the short-lived 0606 beta booted ok and without all the noise the interface allegedly having issues. It did have 1 cycle of reacting to a non-existent interface issue when running but the improvement at boot was quite a change.
Now running the 0610 beta and still no issues at boot and no false interface issues for 30 hours+.
Did a bug get caught and shot?
️ -
No not as far as I know. Which is interesting! Hmmm
-
@stephenw10 said in DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208:
No not as far as I know. Which is interesting! Hmmm
It could be a big coincidence of course but my last hotplug event:
2025-06-11 15:35:26.596764+01:00 php-fpm 5667 /rc.linkup: HOTPLUG: Configuring interface opt3 2025-06-11 15:35:26.596749+01:00 php-fpm 5667 /rc.linkup: DEVD Ethernet attached event for opt3 2025-06-11 15:35:26.596686+01:00 php-fpm 5667 /rc.linkup: Hotplug event detected for LAN(opt3) dynamic IP address (4: 10.0.1.1, 6: track6) 2025-06-11 15:35:26.596176+01:00 check_reload_status 648 Reloading filter...was over 52 hours ago.
I'll keep monitoring.
️ -
The fix for VIPs on PPPoE went into that beta. But I'm not sure how that would affect LAN...
-
Over 72 hrs since my last boot and zero issues with the false interface errors. Packages are happy and DNS resolver has a healthy cache again. Looking like a fix.
@stephenw10 said in DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208:
The fix for VIPs on PPPoE went into that beta. But I'm not sure how that would affect LAN...
Well it didn't really look like a genuine LAN issue from the start. Multiple DACs, vendors and different physical interfaces all showed the same issue.
Regress to v24.11 and the issue went away. Simple DHCP on the WAN to another router and the issue went away again. Remove IPv6 and the issue went away. Use v25.03b with the old PPPoE and the issue went away.
With v25.03b + PPPoE + IPv6 and the problem exerted itself, perhaps with the odd unsolicited RA in the mix, producing the loose periodicity noted. That and perhaps the new SFP28 driver.
Anyway, I am just a sample size of one but so far it all looks good with beta 0610.
I've got logs pre and post fix if required.
️ -
Nice. More fixes are incoming for various things.
If you're able to test this patch that would be good: https://forum.netgate.com/post/1218007
It works fine everywhere I've tested it but, as we are finding, there are significant differences in pppoe connections.
-
@stephenw10
This one?https://nc.netgate.com/nextcloud/s/bt2fWWjdzT4KFHy
What should it do?
It does not work for me though:
Patch does not apply cleanly (detail) Patch does not revert cleanly (detail) Debug Result: Fail This patch does not apply or revert cleanly. The patch settings may be incorrect, the patch content may not be relevant to this version, or the patch may depend upon another separate patch which must be applied first.️ -
Oh it's probably for 2.8 and you're on the latest 25.03-beta. I'll get a diff for that tomorrow.
It allows for ISPs that don't send RAs. Otherwise the gateway is never populated. But we need to be sure it doesn't break anything in the process! (I'm pretty sure it doesn't
). -
-
@stephenw10 said in DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208:
Oh it's probably for 2.8 and you're on the latest 25.03-beta. I'll get a diff for that tomorrow.
Any news about diff for 25.03, @stephenw10?
-
Checking...
-
OK try this. It should apply against the June 10th 25.03 build.
-
@stephenw10
Awesome, I applied the patch and testing. -
@stephenw10 said in DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208:
OK try this. It should apply against the June 10th 25.03 build.
Applied and testing.
2025-06-17 08:48:44.587745+01:00 php-fpm 64902 System Patches: Patch applied successfully (ID: 685080088725a, DESCR: PPPoE IPv6 RA Changes 685080088725a for 25.03.b.20250610.1659)Well, presuming 'applied successfully' means no reboot required?
️ -
Yup you shouldn't need a reboot there. The scripts get run at interface events and will have changed after applying the patch.
-
Probably this is not related to the current patch, ... I think this issue has been present since the early 23.05 versions, but I’ve only recently started to understand what’s going on. Sometimes, but not always, when PPPoE disconnects and reconnects, I receive an IPv6 address on the WAN interface, but nothing is assigned on the LAN interface, which is configured as a track interface. After some time, the IPv6 address on the WAN interface also disappears. I’ll try to collect logs later.
-
-
@RobbieTT said in DNS resolver exiting when loading pfblocker 25.03.b.20250409.2208:
net.inet6.ip6.rfc6204w3
Hmm, does it reflected in pfSense GUI somewhere? I don't have this option at all when listing sysctl net.inet6.ip6, I can add it via tunables anyway, but…
-
Check it at the command line:
[2.8.0-RELEASE][admin@t70.stevew.lan]/root: sysctl -d net.inet6.ip6.rfc6204w3 net.inet6.ip6.rfc6204w3: Accept the default router list from ICMPv6 RA messages even when packet forwarding is enabled [2.8.0-RELEASE][admin@t70.stevew.lan]/root: sysctl net.inet6.ip6.rfc6204w3 net.inet6.ip6.rfc6204w3: 1It should be
1by default. You'll only see it in the tunables list if it's been added as a custom value. -
@stephenw10
Now I havenet.inet6.ip6.rfc6204w3=1Nothing has changed. Manually disconnecting and reconnecting can result in no IPv6 on WAN, or IPv6 being present on both WAN and LAN, and sometimes it initially appears on WAN but disappears from WAN later.
I am not sure it pfSense, it can be my ISP. I see nothing helpful in the logs currently.
BTW, sometimes the uptime is also missing, and clients have no internet access — they cannot ping external sites by name or IP, also directly can not ping from pfSense. However, I can resolve names using DNS lookup on the pfSense, so Unbound is somehow working. But when I check the routes, it looks like the default route is missing — there is no 0.0.0.0 route at all.
This is happening often when playing manual disconnect and connect after.
