Re: Re: Can't transmit with new kernel

I could not get tulip-diag to compile, it complained about undefined 
functions like inb and outb and such.  /proc/net/dev shows nothing but 
485 bytes received in 5 packets, with 3241 sent in 26 packets.  
Everything else is 0.  How can I check the firewall settings? ipfwadm 
says that it's not installed, and ipchains says that it is incompatible 
with the kernel.  iptables says that it can't locate module ip_tables 
and then fails.  I could not find anything else that looked like a 
firewall, but I don't know what to look for.  Thanks,
Steven

On Feb 3, 2004, at 9:38 AM, Donald Becker wrote:

> On Fri, 30 Jan 2004, Steven Schlansker wrote:
>
>> I am having exactly the same trouble.  It seems that the card can
>> receive but not transmit.  I also have tried multiple kernels; it 
>> seems
>> that the last time that it worked was 2.4.17, and before that 2.2.20.
>
> Please include the output of running 'tulip-diag -a' and
> 'cat /proc/net/dev'.
>
> A common problem is the firewall settings:  it may be that the system 
> is
> blocking all packets from being sent.
>
> The advantage of using the cross-version-compatible driver set is that
> the driver should work on all kernel version, or not work at all.  The
> only problem that might occur is if the driver interface changes 
> between
> minor kernel versions.  (That should never occur, but has occured in 
> the
> past.)
>
> -- 
> Donald Becker				[email protected]
> Scyld Computing Corporation		http://www.scyld.com
> 914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster systems
> Annapolis MD 21403			410-990-9993
>
>
>
>
------------------

Steven Schlansker

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip