WAN NIC losing link

TieT

In a way :) I tried a different box.. (same hardware config)

Hmmm, then i would say telenet modem :)

I don't have the problem on 2.2 anymore.
Strange though…

heper

have the same issue on 1 location, also Telenet ISP (i do have multiple other sites also on >2.2 that don't have the issue but they are VM's)

odd to say the least … in my situation, a powercycle of the modem solves it.

xtofh

@heper:

have the same issue on 1 location, also Telenet ISP (i do have multiple other sites also on >2.2 that don't have the issue but they are VM's)

odd to say the least … in my situation, a powercycle of the modem solves it.

Thanks for the info. Modem reboot does not help here, I have to reboot the pfsense box. (non VM)

We have several (including my home, residential, Telenet connection) that work on 2.2 without a problem. the one that has the issue is a Telenet Business. (with static IP that gets assigned via dhcp)

I have reverted to 2.1.5 since a few weeks now for my office connection because losing our connection became too annoying.

sandern

Could be a coincidence but I had the same issue today, also Telenet Business with a fixed ip. I'm also running 2.2

xtofh

@sandern:

Could be a coincidence but I had the same issue today, also Telenet Business with a fixed ip. I'm also running 2.2

I never had the issue on other type of internet subscriptions. You could try upgrading to 2.2.3 ? Did the issue reoccur since last time?

I hope to find the time to try this (upgrade to 2.2.3) in the next few weeks. Feel free to keep us posted..

cmb

Split this to its own thread since the other thread had 5 pages of unrelated history and ended up being caused by a dead hard drive.

@xtofh:

Apr 23 10:42:43 pfsense kernel: em1: Watchdog timeout -- resetting
Apr 23 10:42:43 pfsense kernel: em1: Queue(0) tdh = 817, hw tdt = 786
Apr 23 10:42:43 pfsense kernel: em1: TX(0) desc avail = 31,Next TX to Clean = 817
...

This looks to match this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199174

which should be worked around if you disable MSI and MSIX.
https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#MSI.2FMSIX

heper

@cmb

i've experienced the same/very similar issue on a crappy dlink nic (sk0 driver) that worked fine before upgrading from 2.1.x –> 2.2.x .... so in my case very similar situation with a non-intel nic. (haven't found the time to swap nics)
currently i'm rebooting the firewall every morning at 5am and haven't received any reports like "please fix my internets"

cmb

@heper:

@cmb

i've experienced the same/very similar issue on a crappy dlink nic (sk0 driver) that worked fine before upgrading from 2.1.x –> 2.2.x .... so in my case very similar situation with a non-intel nic. (haven't found the time to swap nics)
currently i'm rebooting the firewall every morning at 5am and haven't received any reports like "please fix my internets"

Could be the same solution for that, try disabling MSI and MSIX.

In the Intel case, it appears the new driver wants to enable things that don't work on some small minority of cards. Could be a similar cause, though completely different root problem given different hardware and driver.

xtofh

@cmb:

Split this to its own thread since the other thread had 5 pages of unrelated history and ended up being caused by a dead hard drive.

New thread: https://forum.pfsense.org/index.php?topic=96325

Harvy66

@cmb:

@heper:

@cmb

i've experienced the same/very similar issue on a crappy dlink nic (sk0 driver) that worked fine before upgrading from 2.1.x –> 2.2.x .... so in my case very similar situation with a non-intel nic. (haven't found the time to swap nics)
currently i'm rebooting the firewall every morning at 5am and haven't received any reports like "please fix my internets"

Could be the same solution for that, try disabling MSI and MSIX.

In the Intel case, it appears the new driver wants to enable things that don't work on some small minority of cards. Could be a similar cause, though completely different root problem given different hardware and driver.

Some rebranded cards, like the HP i350s, may have MSIX disabled in the firmware, but still identify as an Intel i350, which can cause issues. Nothing like saving $10 on a $140 card just to have driver issues or reduced performance because they've disabled or otherwise customized the card.