Update to 23.01 switched LAN port settings?
-
I have my WAN and my primary LAN (NAT'd). Very simple configuration. Netgate 3100.
When I upgraded from 22.05 to 23.01, for some reason, my LAN1 port switched its speed and duplex settings. The interface was effectively off (no lights).
After troubleshooting literally everything else in the house (switches, WiFi routers), I realized LAN1's interface lights were off. Switched cables, nothing.
Finally, went into the Interfaces -> Switches -> Ports and saw that LAN1 showed "No Carrier" even though it had worked just fine under 22.05.
I switched it over to "Default" which says "no preference, typically autoselect" and the interface came up fine.
So, the question is: what changed between 22.05 and 23.01? Did the default setting change under the Interfaces/Switches/Ports?
I also have my basement workstation (adjacent to the firewall appliance) directly connected to LAN3, and that interface either didn't change, or nothing noticed.
I do know that LAN1 is an uplink to a Netgear GS108T managed switch, which services the rest of the devices in the house, while LAN3 is just a direct cable that goes to an Intel NUC workstation. Throughout this, the Intel NUC workstation's connection to the Netgate was not interrupted.
I'm asking this question partially to figure out what went wrong, so I can make sure this doesn't happen again, but also to warn folks who have a configuration as simple as mine to CHECK to make sure the LAN and WAN port lights are on, and everything is happy. If the lights are off, something is wrong. And if the cable worked before the upgrade, it is likely not the cable, or anything else. Check the settings.
-
Hmm, no nothing should have changed in the switch config there.
What was the LAN1 port set to before you set it to 'default'?
How is the port configured in the GS108T it's connected to?
Steve
-
I’m not quite sure what it was set to before the update. Is there a way for me to go into the logs and see?
As far as the port settings, it’s just a regular gigabit Ethernet port, and it worked since Day One of the 3100 installation. It was only after the update today that it flaked out. So weird.
-
@amarand said in Update to 23.01 switched LAN port settings?:
I switched it over to "Default" which says "no preference, typically autoselect" and the interface came up fine.
But what did you do here exactly? Switched it to something else then back again?
The change should be in the config history in Diag > Backup > Config History if you have not made more than 30 changes since.
-
I can see, in the configuration backup, the last update entry:
"(system): Overwrote previous installation of sudo."
Then 15 minutes later, I started troubleshooting (poorly) by fiddling with DHCPv6 (disabled it):
"(Local Database): DHCPv6 server settings saved"
And interfaces:
"(Local Database): Interfaces settings changed"
(I disabled ipv6, because it was throwing errors in the log and I don't use ipv6)
And IPv6 router advertisement settings:
"(Local Database): Router Advertisements settings saved"
But it wasn't until I saw that the interface was down (no lights, "No carrier") that I started fiddling with the switch port settings:
"Updating switch port settings"
When I diff the previous configuration and the first change:
-<media>1000baseT <full-duplex,master></media>
So I guess I had it manually set to that before? And then I changed it to "no preference, typically autoselect" which removed the entry from the config.xml file?
-
My main point was, all I did today was perform the update, that's it. I made no configuration changes whatsoever, and the interface went down, likely due to a behavior in the new version of pfSense that caused the interface to negotiate differently, or interpret whatever setting I had before differently. Everything worked, I did the update, the interface went down. I rarely make changes on this firewall, and those I do make are very incremental - not a port-level change. That type of change would be memorable.
-
I understand. It's unexpected to see any change in behaviour across an upgrade.
Having the port set to 1G fixed is odd though. Although the switch allows it Gigabit Ethernet actually requires auto link negotiation. Either way the switch config only sets the switch IC registers, available link modes did not change. Additonally I would expect the upstream switch to link to it in either mode so I'm not really sure what happened there.
Steve
-
Good news is, I now have one more quick thing to add to my post-update checklist. Thanks for the assist!
