This is a retread of https://reviews.freebsd.org/D34449 which I think will fix the issue for the remote side not supporting autoneg.
Details
Details
- Reviewers
franco_opnsense.org fbsd_opal.com - Group Reviewers
Restricted Owners Package (Owns No Changed Paths)
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
@franco_opnsense.org can you please see if you can find some users to test this that had the colo setups.
@fbsd_opal.com please retest.
Comment Actions
Glad to see this is back under consideration. It will be useful for cases where it is needed.
When D34449 was reverted, we puled a new CAT6 cable where we had had this problem and therefore eliminated our need for this patch.
I am actually at the location in question at the moment, for a few days. I will try to set up a test of this revised patch this weekend.
Comment Actions
Were you able to test, or perhaps can you explain how I can replicate the issue to confirm it is fixed from your perspective?
Comment Actions
My apologies for not following up.
Unfortunately, when I went to do this test that weekend, I discovered that the equipment on that link has been replaced and there is no longer an e1000 controller there, it is all RealTek on that line now.
I have been unable to find the e1000 equipment. I've been told that it failed and was likely sent for recycling.
I've looked for other equipment, but don't seem to have anything suitable.
Sorry.
Replication should be something like setting the local end to a fixed 100bTX full-duplex and confirming that the other end also negotiates to full-duplex.
The problem before was that since we did not support negotiation, the other end chose half-duplex.
My comments in D34449 said to set:
media 100baseTX mediatype full-duplex
on the emX end and then verify that the other end also selects the same.