[nylug-talk] odd network dying problem

[David Blackman]

it was dhcp, but I've been just configuring it statically lately. When
I was doing dhcp, renewing the lease didn't help. Ifdown/Ifup doesn't
help matters, neither does ifdown/rmmod/insmod/ifup. 

still no idea, very frustrating.

--dave

On Tue, May 13, 2003 at 04:34:29AM -0400, Steven Kreuzer wrote:
> Do you have a static or dynamic address on this box? If you get an
> address from DHCP, I am going to go out on a limb and say that the lease
> on the address expired and you never got a new one?
> 
> What happens if you stop your network services and restart them?
> 
> SK
> 
> On Tue, 2003-05-13 at 03:22, David Blackman wrote:
> > hey all-
> > 
> > 	I've been having this random problem since I've gotten to
> > stanford with the network connectivity on my linux box.
> > 
> > 	After about 2 - 4 days of uptime, my box gets what I like to
> > call "the tcp/ip plague".
> > 
> > 	-I cannot get outside the stanford network over tcp/ip (ssh,
> > web, pop3, aim all timeout).
> > 	-Inside the stanford network is fine (ssh-ing to a stanford
> > shell server, web to a stanford website).
> > 	-I can ssh/ftp in to my box from the outside world.
> > 	-I can resolve names just fine
> > 	-I can ping sites just fine
> > 	*THE WIERDEST PART*
> > 	-the windows box that this computer is NAT-ing has perfectly
> > fine internet connectivity. *Perfect*. It's *wierd*.
> > 	-a reboot fixes all this
> > 
> > 	This happened in both 2.4.18 and 2.4.20. Flushing my iptables
> > doesn't fix it. Both an eepro and a tulip card exhibit these symptoms.
> > 
> > --dave
> > 
> > _______________________________________________
> > The nylug-talk mailing list is at nylug-talk at nylug.org
> > To subscribe or unsubscribe: http://herzl.nylug.org/mailman/listinfo/nylug-talk
> 
> 
> _______________________________________________
> The nylug-talk mailing list is at nylug-talk at nylug.org
> To subscribe or unsubscribe: http://herzl.nylug.org/mailman/listinfo/nylug-talk