Unbound is using more than 50% of the CPU after connecting to the LAN.

[0x44]

Hi all, Sorry for my crappy English.
I am observing an anomaly after updating to version 2.8.0. I'm confused why this is happening.

After running pfSense for about a week, sometimes two days, when I plug my laptop into LAN, it seems like LAN goes down.
I am unable to access any websites, the internet connection is not working. I can't access the admin console by domain, just by ip address. However, this is what I see in the monitoring: system utilization increases by 25%, screenshot below.

The PCH chipset temperature is skyrocketing, screenshot below.

If check the system activity: Unbound is using more than 50% of the WCPU.

Logs:

Aug 12 12:04:40 pfsense php-fpm[42210]: /status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1754993080] unbound[68976:0] error: bind: address already in use [1754993080] unbound[68976:0] fatal error: could not open ports'
Aug 12 12:11:21 pfsense php-fpm[33437]: /status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1754993481] unbound[90442:0] error: bind: address already in use [1754993481] unbound[90442:0] fatal error: could not open ports'
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80758a00, 0) error 1
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80758ab0, 0) error 1
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80758b60, 0) error 1
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff807781d0, 0) error 1
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80778280, 0) error 1
Aug 12 12:13:00 pfsense kernel: module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80778330, 0) error 1

sockstat -4 | grep ':53'

unbound  unbound    78696 3   udp4   *:53                  *:*
unbound  unbound    78696 4   tcp4   *:53                  *:*

I think the old socket is not properly closed when I plug the laptop into the LAN, causing Unbound to consume more CPU resources, and a new socket is not opened.
Helps to resolve the issue by rebooting pfSense or restarting Unbound.

Can anyone help me resolve this issue?
Thanks.

[SteveITS]

@0x44 If you are actually plugging a cable into the pfSense LAN port (or turning a PC on etc) that will trigger restarting services because of the “new” interface. Can you put a switch between the PC and pfSense?

Your English is just fine. :)

[0x44]

Yes, I can, but that would mean adding one more device to the setup :). I'm afraid the same issue might happen over Wi-Fi as well. I'm looking for standard ways to fix this.

[0x44]

Any idean? :)

[tinfoilmatt]

@0x44 Router interfaces don't typically 'change' (i.e., unplug/replug, link up/down) that regularly. In order to have Wi-Fi even, you'd need to somehow get an AP on at least the same management broadcast domain as the LAN interface without directly connecting it... because how else would you expect to be able to connect to and manage it?

Directly connecting a network host like a PC or a server to a router interface is a somewhat unsual setup. @SteveITS's advice to connect a switch to the LAN interface—and then properly test connectivity of any/all devices that will connect to the switch, plus assess overall network stability with that topology—is the right advice.