network goes down after a period of time

Stephen Kalpin skalpin at gmail.com
Thu Dec 31 11:02:29 UTC 2009


This only started occurring after I upgraded from Ubuntu 9.04.  I used 
to be able to leave my computer on for days, without a problem.  After 
upgrading to 9.10, I wasn't able to use my samba shares, or ssh.  I 
could still connect to the internet, and browse the web without a 
problem.  I then read a few forums which hinted that I should install 
resolvconf, and bind9.  I installed those and now my servers work great 
for about 20 min, but then everything goes down.  I shouldn't say it 
goes down,  I can still ssh from my os X machine, but it's much slower 
and almost unusable.  The only thing I can really do is sudo su, and 
then reboot.  I tried disabling ipv6 by editing the grub menu (I'm using 
grub 2) with no help.  I also tried to edit the /etc/network/interfaces 
file.  It now looks like...

steve at FRED:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
#iface eth0 inet dhcp

auto eth1
#iface eth1 inet dhcp

auto eth2
#iface eth2 inet dhcp

auto ath0
#iface ath0 inet dhcp

auto wlan0
#iface wlan0 inet dhcp

iface eth0 inet dhcp
#       post-up iptables-restore < /etc/iptables.up.rules
#       address 192.168.1.4
#       netmask 255.255.255.0
#       gateway 192.168.1.1


Heres a list of pings before a reboot (sshed from osX, and it's really 
sluggish)

steve at FRED:~$ ping -c4 localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from  (127.0.0.1): icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from  (127.0.0.1): icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from  (127.0.0.1): icmp_seq=3 ttl=64 time=0.083 ms
64 bytes from  (127.0.0.1): icmp_seq=4 ttl=64 time=0.084 ms

--- localhost ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.076/0.081/0.084/0.003 ms

steve at FRED:~$ ping -c4 www.google.com
PING www.l.google.com (74.125.95.104) 56(84) bytes of data.
64 bytes from iw-in-f104.1e100.net (74.125.95.104): icmp_seq=1 ttl=45 
time=30.8 ms
64 bytes from iw-in-f104.1e100.net (74.125.95.104): icmp_seq=2 ttl=45 
time=31.3 ms
64 bytes from iw-in-f104.1e100.net (74.125.95.104): icmp_seq=3 ttl=45 
time=31.7 ms
64 bytes from iw-in-f104.1e100.net (74.125.95.104): icmp_seq=4 ttl=45 
time=32.2 ms

--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 30.836/31.544/32.214/0.551 ms

(this is my router)
steve at FRED:~$ ping -c4 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.60 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.64 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.60 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.31 ms

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 1.609/2.292/3.601/0.805 ms

(the machine on my local network I'm sshed from)
steve at FRED:~$ ping -c4 192.168.1.3             
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=6.92 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=2.70 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=2.55 ms
64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=2.05 ms

--- 192.168.1.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.053/3.558/6.920/1.956 ms









After a reboot they look like this(i'm sshed in, and everything is 
working great, x11 forwarding, samba, and ftp)

steve at FRED:~$ ping -c4 localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from  (127.0.0.1): icmp_seq=1 ttl=64 time=0.075 ms
64 bytes from  (127.0.0.1): icmp_seq=2 ttl=64 time=0.076 ms
64 bytes from  (127.0.0.1): icmp_seq=3 ttl=64 time=0.076 ms
64 bytes from  (127.0.0.1): icmp_seq=4 ttl=64 time=0.083 ms

--- localhost ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.075/0.077/0.083/0.009 ms

steve at FRED:~$ ping -c4 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.33 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.23 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.32 ms

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 1.327/1.567/2.234/0.386 ms

steve at FRED:~$ ping -c4 www.google.com
PING www.l.google.com (74.125.95.103) 56(84) bytes of data.
64 bytes from iw-in-f103.1e100.net (74.125.95.103): icmp_seq=1 ttl=45 
time=33.5 ms
64 bytes from iw-in-f103.1e100.net (74.125.95.103): icmp_seq=2 ttl=45 
time=31.4 ms
64 bytes from iw-in-f103.1e100.net (74.125.95.103): icmp_seq=3 ttl=45 
time=31.7 ms
64 bytes from iw-in-f103.1e100.net (74.125.95.103): icmp_seq=4 ttl=45 
time=32.0 ms

--- www.l.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 31.488/32.220/33.526/0.794 ms

steve at FRED:~$ ping -c4 192.168.1.3
PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=5.20 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=1.53 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=1.56 ms
64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=1.56 ms

--- 192.168.1.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 1.535/2.466/5.205/1.581 ms

I would post more information, but I don't know what would be helpful.

Thanks for your help in advance





More information about the ubuntu-users mailing list