Big issue from 2.5.2 to 2.6. NIC stop working
-
@stephenw10
Maybe psu issues?
I noted that i need 12V 5A, but psu actually in use is 12 V 2.5A -
Unlikely to be a significnat power draw difference between 2.5.2 and 2.6/2.7.2 IMO. But that is pretty small for a device with 6 NICs.
Try running a packet capture on that NIC and see if it's still seeing any packets incoming after it stops responding.
I assume the console still responds after that?
Other NICs still work?
-
@stephenw10 yes console still works. How can i make packet capture? With Shell? I have never done It.
-
-
And it's only the NIC you're trying to connect to that appears to stop passing traffic? I.e. a NIC/driver issue or soemthing in the network stack.
-
@stephenw10 with tcpdump I noted that NIC stop receiving traffic.
It happens on every NIC -
Ah so it appears to lock up the NIC/driver somehow.
Do you mean it causes all NICs to stop passing traffic at the same time?
Or just that any NIC you connect to will fail the same way?
-
@stephenw10 i connected at two nics with two devices and two ip addresses. When i try access gui everything crash on all nics. All crash at same time. I tried also opnsense. Samd resulta. I enter ip in web i press enter and nic crash. After some time crash everything also console. I need tò reboot
-
OK so:
It stops responding at all on all NICs. Even to ping.
The console remains responsive.
Can you ping out from the console? To something via the WAN perhaps?
And nothing is logged when that happens?
I really expect to see some error.
-
@stephenw10 Yes
At first NIC responds to ping
If i enter 192.168.1.1 in browser and i press enter it stops working an all NICs even PING
Device is able to ping itself
So appliance is able to ping 192.168.1.1. It responds
Console remain responsive
Nothing is logged, but maybe i do not able to find some log.
In shell i can not see anything.I tried to replace RAM and PSU but the issue persists
-
Literally nothing is logged or just nothing that appears related?
Does
dmesgreturn anything different?You could also check the mac stats for the NIC using:
sysctl dev.igb.1
See if anything there is throwing a load of errors. -
@stephenw10 no error i think
it says driver version 2.5.19-fbsd and other info but no error are displayed.
Same problem if i try to make ssh access -
@reynold said in Big issue from 2.5.2 to 2.6. NIC stop working:
Same problem if i try to make ssh access
For SSH to work, you need a working interface first.
Console access is your friend.
If you know you're way around, go look here : /var/log/
You'll find all the logs files there.
Check what's been log lines were added to the most recent updated files. -
@Gertjan I have different log system filter boot.log...
What kinds of logs should I check?
How can i display log from the most recent updated?thank you
-
@Gertjan system log says transmit failed network is down
-
Errors in the sysctls might look like:
dev.igb.0.watchdog_timeouts: 0 dev.igb.0.rx_overruns: 0 dev.igb.0.dropped: 0 dev.igb.0.mac_stats.coll_ext_errs: 0 dev.igb.0.mac_stats.alignment_errs: 0 dev.igb.0.mac_stats.crc_errs: 0 dev.igb.0.mac_stats.recv_errs: 0 dev.igb.0.mac_stats.sequence_errors: 0 dev.igb.0.mac_stats.symbol_errors: 0 dev.igb.0.mac_stats.collision_count: 0Anything bigger than 0 there could be a clue.
Also interesting would be if the stats stop increasing at all when the NIC stop responding.
-
@stephenw10 no errors.
I noted only ring state pidx tail 027 idle
no errors
Replace psu mini stata disk and ram.
Issue persists. -
@stephenw10
obviously if i downgrade to 2.5.2 everythings return working again.
I also tried installing different filesystem ufs and zfs but issue persists -
@reynold said in Big issue from 2.5.2 to 2.6. NIC stop working:
system log says transmit failed network is down
What's the actual log entry there? And any surrounding it from the same time period?
-
The dmesg.boot file might also contain important info.
