Adding Speed Parameters to X550 Config

[spetrillo]

Yes swapping the cables fixed the issue. The switch log shows the connection and negotiation to 100M. Nothing abnormal.

If the switch is fully 802.3bz compliant it could have ran next/fext for alien noise and decided to accept the lower speed. I wonder what the switch would accept of 100M was not available from the x550? If say 2.5G was the only speed allowed in auto-neg would it accept that or not link at all? For me I would be curious and test it, but since your setup is working that's up to you.

Were your bad cables new and labeled as CAT6?

They were labeled as Cat6 and prolly no more than a year old. I am going to end up swapping out all cables for new ones, when I build my mini rack.

[spetrillo]

So some interesting driver info for FreeBSD. If I look at the Intel website it tells me the latest FreeBSD driver version is 3.4.31, however when I run sysctl -a | grep dev.ix.0.iflib.driver_version it tells me I am running 4.0.1-k on my OPNsense server. Not sure where this driver came from bc the Intel 30.4.2 pkg only shows the 3.4.31 version.

I just did a standard OPNsense install. Its just running 25.7. I ran sysctl -a | grep dev.ix.0.iflib.driver_version. It shows the version as 4.0.1-k. I thought this was the driver version for ix.

Well, the ix ko shows 4.0.1-k
How it's loaded in? It's not in as klm
strings /boot/kernel/if_ix.ko | grep "4.0.1"

kldstat -v |grep ix
it's #146 on my OPNsense.
ix is in the kernel, I suspect the ko is the same code that's in the kernel. Edit: which is the case, v14.3 src code ID's ix driver as 4.0.1-k. Version numbers between freeBSD code and Intel code will be different, because it's different vendors numbering in different ways.

Why have a ko and in the kernel? Well, it is possible to unbind the static ix and then kldload the ko, which gives you flexibility, and ability to load your own compiled ko driver.

So then dont worry about this for my build.