On Fri, Oct 16, 2026 at 02:03:30PM +0100, Stuart Henderson wrote:
On 2026/10/16 14:49, Henning Brauer wrote:
* void <[email protected]> [2026-10-16 13:46]:
> A suggestion: have you tried 'nailing up' the speeds on either side?
> Instead of auto-negotiation. If you can't set both, then at least set the
> openbsd side. (by that I mean set the speed and duplex explicitly)
> then test again.
that is like the worst advice possible.
this comes from a distant past, where some vendors (hello cisco) had
royally screwed up autoneg implementations. that's like 3 decades ago
tho and just history now.
to be fair, the cisco bug responsible for most of this "advice" wouldn't
have been much of a problem without the matching OS driver bug (I think
it was dcphy claiming to support 100baseT4 when it didn't) alongside...
Yes, sorry it was a bad suggestion; it was made in good faith.
You are correct in that the information was from a couple of decades
ago, and yes this was when I was working with cisco kit (on leased lines)
I also didn't twig that in 1000base-T auto-neg was *mandatory* but I see
802.3ab says it is. Sorry about that. TIL.
--
