Here's somebody on the web who had a very similar problem, with a similar solution.
http://msgs.securepoint.com/cgi-bin/get/netfilter-0211/37/1.html I wonder if your cable modem is using a larger MTU than ethernet has, and is repacketizing your TCP stream along the way. That would allow it to send back-to-back packets out the Ethernet interface, which would be the easiest way to confuse the NIC. But repacketizing IP is evil. Just for a grin, before you shell out for a new NIC, why not try a different release, such as KNOPPIX? You can download it real fast using Windows. (-: Redhat may have introduced a driver bug. Horst wrote: > On Wed, 18 Dec 2002, Jacob Meuser wrote: > > > On Wed, Dec 18, 2002 at 03:14:09AM -0800, Horst wrote: > > > > > ... kernel: http://www.scyld.com/network/ne2k-pci.html > > > > Did you read that? > > Now I did. > > Wow, if even the *author* of the kernel module says the following I may > have to go NIC shopping: "PCI NE2000 clones are a bad idea ... This trend > has continued to the PCI bus. A NE2000 design makes little sense here. " > Certainly, it fits my observations; previous installations all used the > same kernel module (but Win doesn't). The NIC worked fine in a local > 10Mbps network, but cable modem may require something faster... > > Thanks man! ........................ Horst > > Mike, also thanks for the tip, but given the gravity of the statement > above I may just waste time with kernel and/or IRQ tweaking at each new > installation. > > > ... > > _______________________________________________ > Eug-LUG mailing list > [EMAIL PROTECTED] > http://mailman.efn.org/cgi-bin/listinfo/eug-lug -- Bob Miller K<bob> kbobsoft software consulting http://kbobsoft.com [EMAIL PROTECTED] _______________________________________________ Eug-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
