"igb1: link state changed to UP/DOWN" is it benign ?
-
I need to keep my eye on this, so far I didn’t see any related problems, or at least did not register them as such
Don’t see much lights issues but I’m not watching my switch all the time
Run all standard packages
No errors in last ~4 h
Interesting...
-
Update - I see no link state changed messages on LAN since yesterday.
What changed? I reinstalled all packages after seeing some warnings in the log.
However I see now this on WG:
Feb 28 09:09:40 kernel wg0: link state changed to UP Feb 28 09:09:40 kernel wg0: link state changed to DOWN Feb 28 09:09:39 kernel wg0: link state changed to UP Feb 28 09:09:39 kernel wg0: link state changed to DOWN Feb 28 09:09:38 kernel wg0: link state changed to DOWN Feb 27 12:03:52 kernel igb1: link state changed to UPThe fact that this is on wg0 makes me think it maybe s/w related not cables etc.
-
You're running Wireguard and OpenVPN?
-
@jknott said in "igb1: link state changed to UP/DOWN" is it benign ?:
You're running Wireguard and OpenVPN?
Yes
-
Still see them:
Mar 20 07:20:31 check_reload_status 378 Reloading filter Mar 20 07:20:31 check_reload_status 378 rc.newwanip starting igb1 Mar 20 07:20:31 php-fpm 74793 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.90.1 ) Mar 20 07:20:30 kernel igb1: link state changed to UP Mar 20 07:20:30 check_reload_status 378 Linkup starting igb1 Mar 20 07:20:27 check_reload_status 378 Reloading filter Mar 20 07:20:27 php-fpm 71393 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.90.1 ) Mar 20 07:20:26 kernel igb1: link state changed to DOWN Mar 20 07:20:26 check_reload_status 378 Linkup starting igb1 Mar 20 06:52:21 arpwatch 79456 bogon 10.10.10.1 00:0e:c4:d1:6f:28 Mar 20 06:52:20 check_reload_status 378 Reloading filterand nothing else ...
:( ??? -
Try swapping the LAN to a different port. Something other than igb1.
Steve
-
Yeah that's probably only an option left.
Current assignment:
LAN - igb1I do have igb3 NIC/port available.
Would you assign a new LAN2 -> igb3 (and then copy all FW rules to it)
or
is it safe simply change LAN -> igb3 ?and connect an Ethernet cable to a new port after...
PS: Trying to make sure not to do anything stupid :)
Thx
-
Just reassign LAN as igb3 and all your existing rules etc will follow it.
-
What can I tell?!
What was going to be a simple step, turned out to be not so easy :(Changed LAN -> igb3, system after save does not show igb3, still shows igb1. No usual apply setting banner/button or Interface has been changed etc. Everything seems broken. I maybe pushing too hard enough, but was not able to make a new assignment to work.
Restored back to the previous configuration via Auto Config Setup.
I guess "link state changed to UP/DOWN" does not sound too bad after whole system is down :) that's a good output.
But still scratching my head WTH ? ...
-
Mmm, hard to say. I wouldn't expect an issue as long as the LAN was reconnected to the new NIC correctly.
-
I think I could not change LAN -> igb3 because it was seeing by pfSense as "disabled".
Not sure why pfSense did show it in the drop down as available network port. Maybe there is some point, but actually feels like a bug to me.
Anyway, meanwhile added new LAN2 -> igb3 and setup with DHCP and one open to all FW rule. Will watch this for awhile and then will switch:
LAN2 -> igb1
LAN -> igb3 -
Update:
Assigned a new interface LAN2 -> igb3 (Logged a bug )
Connected only one laptop to it
Every time when laptop tuns on I see:
ligb3: ink state changed to UPand when powered off -
igb3: link state changed to DOWNThis laptop connected by a long 20-30 cable, so it's possible some issues and it's not easy to replace. But overall troubleshooting was helpful.
It's still possible that my router box is faulty (which is unlikely) or pfSense throws false errors sometimes. Hard to say.
Thx for your help @stephenw10
-
Looks like igb3 works exactly as expect there then.
