Big issue from 2.5.2 to 2.6. NIC stop working
-
Are they all Intel NICs? All using the igb driver? There's a good chance the ordering has changed if you have some newer igb NIC in there.
Does
ifconfig igb1show the NIC as UP and linked? -
@stephenw10 @Gertjan
nic are all the same
during startup boot everything is ok nothing strange
ifconfig show correct ip
i'am able to ping during boot
But if i open a web browser to 192.168.1.1 for web gui, ping stop responding and NIC stop working
that's the issue
If i not open browser ping keeps working
I'm using ZFS -
If you reassign LAN to one of the other NICs does the issue follow it?
Can you test a 2.7.2 install?
-
@stephenw10 same issue if i change LAN interface
-
Hmm and it still shows as up and linked after it stops responding?
And then it fails to respond to anything until you reboot?
I would test 2.7.2 if you can because this may well be a bug that's fixed there already.
-
@stephenw10
Exactly.
I am testing 2.7.2 memstick serial, i downloaded iso.
I'm installing via usb
It says lo0 link state changed to up.
But at this point installation stops it seems freezed -
On the serial console? When using the memstick-serial image?
Where exactly does it stop?
-
@stephenw10
Exactly.
It stops when discovers / test interface,
It says igb1 link state changed to up ok
It says lo0 link state changed to up (suppose loopback interface)
At this point installation stop and does not keep going on.
It stops very early in the process -
Can you copy/paste that output here for review?
It sounds like that's the output from the wrong console. The last thing you see on both consoles are interface state changes. So you wold see that if you used the memstick image or ISO instead of the memstick-serial image.
-
@stephenw10 said in Big issue from 2.5.2 to 2.6. NIC stop working:
Can you copy/paste that output here for review?
It sounds like that's the output from the wrong console. The last thing you see on both consoles are interface state changes. So you wold see that if you used the memstick image or ISO instead of the memstick-serial image.
ok i updated to 2.7.2 maybe i choosed bad iso.
But i have the same issue
When i try to start GUI via HTTP it stops responding until reboot -
@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
