24.03 -> 24.11 Auto-Negotiation Issue
-
Hi all,
After upgrading from v24.03 to v24.11, pfsense is no longer able to auto negotiate with my network tap (dualcomm branded) at 1000baseT <full-duplex>; instead it now negotiates to 100baseTX <full-duplex>. I do understand that such a drop can be caused by cable issues, but I was able to find an an temporary tap to test it out with the exact same cables and it negotiated correctly to gigabit. Direct connection to switch, removing any network tap, also negotiates correctly to gigabit as expected. Is there any way to troubleshoot what change could have caused this or suggestions for settings I can try? Thanks.
-
What NIC are you using in pfSense?
If you reassign the interface to a different NIC does the fault follow it?
-
@stephenw10 I believe its Intel 2.5Gb (pfsense is on a Negate 6100). I have tried multiple of the 2.5Gb ports and the auto negotiation has ended with 100Mb. I will try with the gigabit ports and report back shortly.
-
I can confirm that the physically 1Gb interfaces on the 6100 negotiated with the TAP to 1Gb, only the physically 2.5Gb interface are negotiating to 100Mb, instead of the expected 1Gb.
-
Hmm, well there shouldn't be any significant difference to the igc driver between 24.03 and 24.11. In both though the igc driver will only link to auto-negotiated connections.
You can set 1G as the only speed it can negotiate.
-
@stephenw10 When I manually set to 1000baseT full-duplex on the 2.5Gb NICs, it does not successfully negotiate to 1Gb with the TAP inline, but will negotiate correctly with backend at 1Gb when TAP is removed. This is regardless of network device behind the TAP. When set to 1000baseT full-duplex on the 1Gb interfaces, TAP is auto negotiated to 1000baseT full-duplex correctly. It seems to be specific to the 2.5Gb interface after 24.11 and this TAP.
I am open to testing a revert of the firmware to 24.03 if that helps, but that will have to be a late next week item.
-
Yes rolling back to 24.03 to confirm the state there would be my next test.
-
@stephenw10 thank you, is there a repo location I can get the 24.03 version of pfsense plus? The shopify link only allows the latest version and I could not find a downgrade option directly within the pfsense console.
-
The Net Installer available in the store allows installing several versions including 24.03 and 24.11.
However if you're using ZFS you should have a BE from 24.03 you can just roll back to. Check System > Boot Environments. You can just boot one time back into a 24.03 BE and then reboot back to 24.11.
-
@stephenw10 I could only find options of architecture types, not version on the store. The email link is only for latest version as well.
ZFS is not an option on my appliance.
-
The latest version of the Net Installer can install many different versions of pfSense. The image linked in the store will allow installing both 24.03 and 24.11. You just select it during the install.
See: https://docs.netgate.com/pfsense/en/latest/install/install-walkthrough.html#version-selection
-
@stephenw10 Sorry for the delay, I did the reinstall to the pervious version and things get even more strange. One port now negotiates to 100MB and the other to 10Mb. Thanks for the assistant.
-
Ok, so it fails to negotiate to 1G in either 24.03 or 24.11? At least that rule out some obscure driver issue. It should be the same in both versions.
So that really does seem like a hardware issue somewhere. If not the cable and you've tried multiple ports then it can only be the connected device.
-
@stephenw10 Both 24.03 and 24.11 are the same it after the rollback:
2.5 Gb physical interfaces on pfsense: only auto negotiates to 10/100Mb full duplex with TAP
1 Gb physical interfaces pfsense: auto negotiates to 1000Mb full duplex with TAPAt this point, I am just a bit puzzled what changed I might have done. The TAP has been in use since like late 2021 and until like a month ago everything was working at gigabit on the same 2.5Gb physical ports on the pfsense.
