[EMAIL PROTECTED] wrote:
> On 15 Feb, [EMAIL PROTECTED] scribbled:
> -> Ian Tester <[EMAIL PROTECTED]>
> -> > If I work up the courage, I'll take back the D-link and get some nice
> -> > Intel EtherExpress-100 or Tulip cards from someone else!
> ->
> -> I've got a "thing" about the Intel Etherexpress cards after all
> -> the trouble we had with them at work. I've rabbited on before
> -> about them, we now only use 3COM 905B 10/100 cards now and
> -> have never had a problem (connecting to Cisco gear). The reason
> -> I bought the Dlink instead is it's way cheaper, I am happy
> -> with the Dlink 650-TXD pcmcia card I bought for my laptop and I
> -> don't need top performance for my home network.
>
> as a matter of fact the eepro "problems" basically resulted in intel
> pointing a finger at cisco for generating malformed ehternet packets...
> and sicso pointing a finger at intel saying its a perfectly fine packet
> and that intle just dont handle all proper packets right.
i think I heard something like that was the problem as apparently
the eepro cards work ok with other brand switches/hubs.
If there's a disagreement in the "standard" I think I'll believe
Cisco over Intel.
> in the ned theres patches in the kernel now that fix the eepro problem
> - draga (one of the guys here at va) fixed it.
this was solaris x86, not linux, but we had the same problems with
an NT PC with eepro card being unable to connect to a Cisco switch
until we set the switch port config to force it to 10Mb. The 3COM
cards I mentioned above handle the auto-negotiation to 100Mb fine.
Dave.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
