I've run into stuff like this from time to time with various interfaces
FreeBSD. I've also run into it with ethernet connections under Windows.
I've also run into it with Cisco-to-Cisco gear. For example if you dig
on Cisco conneciton online, you will find a known bug about connecting
Cisco 2800's to Cisco 2950 switches - Cisco had to come out with a
firmware update for the 2950 after releasing the 2800 due to ethernet
The smart-aleck answer is like the old "Doctor it hurts when I do this"
"well don't do that" but it is also the right answer. Don't use a crossover
cable in this application.
I know it looks weird when you have a $7.95 hub you got from Goodwill
that is plugged in between a $3K Catalyst switch and a $5K 2800 but when
the customer won't pay for service on the switch to get the latest firmware
for it, that's what you have to do to keep things running for them.
I did leave the Goodwill price tag prominently on the hub, by the way.
----- Original Message -----
From: "Dave Raven" <[EMAIL PROTECTED]>
Sent: Monday, August 21, 2006 6:11 AM
Subject: Cisco/BSD auto-negotiation
> Hi all,
> I'm currently looking into a problem with a Cisco 3640 router and a
> FreeBSD 4.9 unit, connected via a crossover cable, that are not
> If you force the media setting to full or half duplex it has constant
> collisions on the interface, and if you let both autonegotiate the cisco
> keeps resetting (every ~20 seconds) its network card.
> Are there known issues with this, or any known fixes?
> Ps. Please copy me on replies as I am off the list.
> email@example.com mailing list
> To unsubscribe, send any mail to
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"