[SOLVED] Periodic NIC issues (?) with Protectli Vault, Intel i226-V

[fornax]

Ok, it's been 2 weeks without incident, so I'm going to (cautiously) call this resolved by the switch from coreboot BIOS to AMI. I did update Protectli; they indicated there's no plan for a patch to coreboot for the VP3200 series at this time. The support person mentioned they wanted to talk to the dev team about it, but I haven't heard anything in the week since, so I'm assuming nothing further is forthcoming. I'll update this if that changes.

Thanks to everyone who pitched in with troubleshooting help and suggestions!

[OPNenthu]

The support person mentioned they wanted to talk to the dev team about it, but I haven't heard anything in the week since, so I'm assuming nothing further is forthcoming. I'll update this if that changes.

Just wanted to leave a thanks for making upstream aware of these issues.  Maybe some more updates (or at least clarity) will trickle down into coreboot eventually.

[franco]

There are some patches in 26.7.2 that should improve stability of igc regardless of firmware version.


Cheers,
Franco

[OPNenthu]

@franco would those changes have any bearing on TLS handshake hangups?  For example in Firefox I'd see this in the lower left corner very often and it would take seconds to resolve, or sometimes require a refresh:

You cannot view this attachment.

Currently on 26.7.2 and no lie, I'm not seeing this yet.

I'll temper my excitement but should I be cautiously optimistic, or is this placebo?

EDIT:  I had already ruled out an MTU issue.  My DOCSIS gateway and WAN interface use the default 1500 and I confirmed with ping from my Linux client that I can send up to 1472 bytes of ICMP payload with the "don't fragment" flag set:

Code Select Expand

$ ping -c 3 -M do -s 1472 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1472(1500) bytes of data.
1480 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=32.3 ms
1480 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=39.2 ms
1480 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=36.2 ms


Code Select Expand

$ ping -c 3 -M do -s 1473 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 1473(1501) bytes of data.
ping: local error: message too long, mtu=1500
ping: local error: message too long, mtu=1500
ping: local error: message too long, mtu=1500