Re: Strange network performance
On Sunday 23 September 2001 05:34 pm, Charles Franks wrote:
> Generally in a network environment you want to 'strap' ports to
> speed/duplex settings and avoid autonegotiate as this can cause problems...
> when both ends are set to 'auto' it almost always causes problems such as
> links re-negotiating out of the blue.. this kinda sounds like what you are
> experiencing.
I had a problem like that with a NetGear router I was plugging into. I
couldn't force full duplex on the router, so I was stuck with half duplex
even with full forced on the cards themselves. It was pretty slow. You
pretty much had to get a cup of coffee if you wanted to copy a 10MB file.
> I don't know what the commands are but if possible I would 'strap' both
> nics to 100/full. I have also found that some nic's (drivers) don't really
> support 100/full all that well (in general not just under linux) and they
> actually perform better when set to 100/half.
>
> Charles
>
>
>
>
>
> ----- Original Message -----
> From: "Matthew Sackman" <matthew@sackman.co.uk>
> To: "Noah Meyerhans" <noahm@debian.org>; "Debian User List"
> <debian-user@lists.debian.org>
> Sent: Sunday, September 23, 2001 2:12 PM
> Subject: Re: Strange network performance
>
> Well, that's all gone through and worked - not quite as simple as I
> thought, but I got there. Network performance seems a little faster
> than before but still a little slow compared with what I thought
> would have been possible with a 100TX crossover network. Must be
> a limitation of the cheap cards.
>
> Thanks for your help.
>
> Matthew
>
> On Sun, Sep 23, 2001 at 06:56:31PM +0100, Matthew Sackman wrote:
> > Yes, it's a 2.4.9 kernel on both machines with the included natsemi
> > driver.
> >
> > dmesg reports much the same for both machines:
> >
> > eth0: link is back. Enabling watchdog.
> > eth0: Setting full-duplex based on negotiated link capability.
> > eth0: Link changed: Autonegotiation advertising 05e1 partner 0000.
> > eth0: no link. Disabling watchdog.
> > eth0: Link changed: Autonegotiation advertising 05e1 partner 45e1.
> > eth0: link is back. Enabling watchdog.
> >
> >
> > I'll replace the driver with the one from scyld.com - it's just a matter
> > of physically over writing /usr/src/linux/drivers/net/natsemi.c with the
> > new one right?
> >
> > Thanks,
> >
> > Matthew
> >
> > On Sun, Sep 23, 2001 at 01:41:59PM -0400, Noah Meyerhans wrote:
> > > On Sun, Sep 23, 2001 at 06:36:05PM +0100, Matthew Sackman wrote:
> > > > I've just set up a 100TX network with 2 computer both running debian.
> > > > Netgear FA311 cards and a single cross-over cable.
> > >
> > > What version of the kernel are you running? If it's 2.4, are you
> > > running the natsemi driver included with the kernel, or did you
> > > download it from scyld.com? If you're running the version that came
> > > with the kernel, try replacing it with the one from
> > > http://www.scyld.com/network/netsemi.html. The one in the kernel is
> > > based on that driver, but has been modified. You may have more success
> > > with the original.
> > >
> > > Also, use dmesg and see if anything is being logged by the kernel
> > > relating to these issues. I've seen some IRQ problems with the
> > > natsemi-based cards.
> > >
> > > noah
> > >
> > > --
> > > _______________________________________________________
> > >
> > > | Web: http://web.morgul.net/~frodo/
> > > | PGP Public Key: http://web.morgul.net/~frodo/mail.html
> >
> > --
> >
> > Matthew Sackman
> > Nottingham,
> > ENGLAND
> >
> > Using Debian/GNU Linux
> > Enjoying computing
> >
> > It said 'Required Windows XP or better.'
> > So I installed Linux.
Reply to: