[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Linux Routing Problem



They're Kingston KNE110TX cards (DEC Tuplip Chipset).  I've thought of
hardware failure, but am wondering why the card still seems functional
(from ifconfig's info, anyway) and can be pinged when the situation
arises.  The link light is also on, and still seems to be flickering with
data when this happens.  *shrug*  I may try swapping NICs.

Koree
____________________________________
Koree A. Smith  | Ameth Technologies
koree@koree.net | koree@ameth.org
     http://www.koree.net/

...as we enjoy great advantages from the inventions of others, we should
be glad of an opportunity to serve others by any invention of ours; and
this we should do freely and generously.
						--Benjamin Franklin

On Tue, 20 Mar 2001, Sean /The RIMBoy/ wrote:

> On Tue, 20 Mar 2001, KoReE wrote:
> 
> > I was just curious if anyone has ever run across this probelm.  I use a
> > Linux box to do some routing in my office.  It has two ethernet cards in
> > it, and routes between the two.  For the past few days, it has been doing
> > what appears to be losing ipv4 forwarding.  I will be able to ping both
> > ethernet cards themselves, but none of the machines on the far end
> > (network routed to eth1), even though eth1 is reachable and pingable.  I
> > checked /proc/sys/net/ipv4_fowarding, and it was set to 1, which I believe
> > is correct.  So, anyone ever seen this?  If so, anyone have an idea of
> > what could be happening?
> 
> I've not seen it before, and I don't ever recall hearing of this
> problem.  Curious, what kind of NIC's?
> 
> Sean...
> 
> -- 
> A flute with no holes is not a flute.  A donut with no hole is a danish.
> 	--Chevy Chase, Caddyshack
> _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> www.rimboy.com		<-- Your source for the crap you know you need.
> www.rimboy.com/rimdistro/rimiradio  <-- Icecast server on a floppy! (i486+)
> 
> -
> To unsubscribe, send email to majordomo@silug.org with
> "unsubscribe silug-discuss" in the body.
> 

-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.