Post

I think I figured out a fix (pending confirmation). I'm not sure what is causing the link downs, probably some hardware reliability issues at 10G, but I'm fine with it as long as it can recover, which it failed to do. The fail state was link up with only an IPv6 address. I present to you the fix:

IS2511@is2511.com

It was not in fact the motherboard port... :( Ok, the warnings are because of the WinBox itself. But what is up with all the link up and downs? This is after switching to an SFP28 port on a ConnectX-4 PCIe NIC.

1/6/26, 11:00 am0 reposts1 like

IS2511

@is2511.com

1 June

Maybe I should set a static IPv4 address... The DHCP lease is static anyway. The IPv6 recovery seemed quick (SLAAC perhaps), especially compared to an IPv4 re-acquisition, probably bc of all the DHCP yap. I think the instant IPv6 re-acquisition made it skip IPv4, causing permanent connectivity loss.

IS2511

@is2511.com

1 June

> But why do you have IPv6 enabled if you ISP doesn't even support it? I like having stuff enabled if it's supported, ok? My LAN is IPv6-capable, even if I don't use it. Maybe I should. Maybe 50 years from now we will all finally migrate to IPv6 and I'll get some practice with it...