[vortex] Strange issues with 3COM cards on Linux - DHCP oddities.

[Raymond Lillard]

Shawn,

A related possibility is that the switch might be mishandling
the auto-negotiation when connected directly to the 3com
card.  Although we don't use DHCP here, we have experienced
communication problems due to auto-negotation failures when
connected directly to a Catalyst 2980G that dissapeared when
connected through a D-Link 8-port switch (DSS-8+).

Cisco has an app-note on this.  If Joe's advice below doesn't
help look at the negotiated media and duplex settings with
vortex-daig.

Best
Ray



> -----Original Message-----
> From: vortex-admin@scyld.com [mailto:vortex-admin@scyld.com]On Behalf Of
> Joe Rouvier
> Sent: Tuesday, August 28, 2001 5:31 PM
> To: Shawn Starr; vortex@scyld.com
> Subject: Re: [vortex] Strange issues with 3COM cards on Linux - DHCP
> oddities.
>
>
> That sounds like a problem with the switch not starting to
> forward traffic to
> your box fast enough after the link gets reset.  Try adding the PortFast
> option to your cisco config.
>
> Also, see this doc:
> http://www.cisco.com/warp/public/473/12.html
>
> On Tuesday 28 August 2001 16:55, Shawn Starr wrote:
> > Hello, I've been experiencing strange issues with DHCP and 3COM cards on
> > Linux kernels 2.2, and 2.4 using RedHat 6.1 and 7.1 respectively, here's
> > the strange part.
> >
> > When connecting the 3Com card directly to a Switch (Catyalst 3548)
> > DHCP times out on the system.
> > When connecting the card to a Hub which is connected to the Switch (via
> > the Uplink port), DHCP works fine and the card functions normally.
> >
> > What is happening? Is this a driver issue or something else?
> >
> > Thank you,
> >
> > Shawn.
>
> _______________________________________________
> vortex mailing list
> vortex@scyld.com
> http://www.scyld.com/mailman/listinfo/vortex
>