Unbound stops listening on Interface #2

DaddyGo

Is this now resolved or what is the current status?

https://forum.netgate.com/topic/161400/unbound-stops-listening-on-interface?loggedin=true

@viktor_g
https://redmine.pfsense.org/issues/11547

I have not come across this so far, I recently connected to a "free PHY" I350 (igb(4)) interface on pfS box with an Ubuntu Desktop 20.04 and every morning I have to restart "unbound"

The Dell Wyse 5060 is connected directly to a port on the pfSense box and indeed after a "break - idle" (at night) in the morning there is no DNS res. from the box, DHCP works fine.

None of this would have happened if my wife's 4G access hadn't been taken back by her company, saying COVID is over, hihihi :), of course she can't work with me when using Citrix, Jabber, etc., so she got a new WAN public IP (only for her) and a separate interface (igb), but I've been struggling with this DNS issue ever since

in the morning after coffee

Ubuntu start (no res.):

Unbound after restart:

+++edit:

DaddyGo

UPDATE:

This is a fundamental problem on this NGFW , since, if I keep the port alive with say WOL , I don't have this Unbound stop problem

of course, it's not mind-blowing, but it's damn confusing when only one device is directly connected to a pfS port (eth)

solution on Ubuntu Focal Fossa (in short):

sudo apt install ethtool
sudo ethtool enp4s0
sudo ethtool --change enp4s0 wol g

sudo systemctl daemon-reload
sudo systemctl enable wol.service

+++edit:
this was an unpleasant discovery (on pfSense) :(