hotplug causes pfsense to become unresponsive 2.4.4
-
I had a overnight firmware update of my modem that caused pfsense to go into a loop of "hotplug" events and "unbound bind: address already in use" events and became unresponsive.
This was no big deal, as modem rarely gets restarted so I can live with this, not convenient to have to manually restart pfSense.Then there was a firmware update for my main switch and again the loop of "hotplug" events and "unbound bind: address already in use" errors. No big deal, another force restart.
Then I turned off ssh on my main switch and caused it to restart. Again the same problem, rinse and repeat.
As you can see this is annoying.
Can anyone else reproduce this issue or am I alone in this one?
edit: upgraded to dev version and still same issue
edit2: intel igb nics on supermicro atom based motherboard, powerd disabled, tso disabled, link negotiation set to defaul, eee disabled, Issue persists. -
Do you have a DHCP WAN? Might be this: https://redmine.pfsense.org/issues/8507#note-23
-
@jimp i eventually fixed the issue and it no longer goes into a loop of hotplug events, I set mtu/mss for each interface in addition to other stuff I mentioned above.
But clicking save on any of the interfaces still makes pfsense unresponsive and goes into loop of renumbering vlans.
But that is not big as I rarely touch those settings.
-
See my previous comment above. If you have a DHCP WAN and have the advanced option set it might be taking an invalid MTU from your ISP and applying it to the interface, leading to the interface flapping problem. There is a workaround in the link above.
-
@jimp do i need to apply the patch if my /etc/inc/interfaces.inc lines 4990 and 5096 match the patch?
-
@strangegopher said in hotplug causes pfsense to become unresponsive 2.4.4:
@jimp do i need to apply the patch if my /etc/inc/interfaces.inc lines 4990 and 5096 match the patch?
No because that would mean you already applied the patch or made the edits manually.
The change on line 4990 and around it were made well before 2.4.4-RELEASE. The change on line 5096 was just put in two days ago.
-
@jimp okay i am on latest snapshot, that is probably why its not looping anymore.
