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

Re: Network connections breaking after bootup



On Tue, May 15, 2007 at 09:15:22 +0000, Tim Johnson wrote:
> On Tuesday 15 May 2007 16:13, Florian Kulzer wrote:
> > On Tue, May 15, 2007 at 07:32:11 +0000, Tim Johnson wrote:

[...]

> > I would also like to see the output of:
> >
> > /sbin/ifconfig
>   ## ----------------------------------------------------------
> eth0      Link encap:Ethernet  HWaddr 00:80:AD:79:35:E1  
>           inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::280:adff:fe79:35e1/64 Scope:Link
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:28 errors:248 dropped:0 overruns:0 frame:0
>           TX packets:26 errors:6 dropped:0 overruns:0 carrier:6
>           collisions:0 txqueuelen:1000 
>           RX bytes:3055 (2.9 KiB)  TX bytes:2492 (2.4 KiB)
>           Interrupt:217 Base address:0xbc00 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:50 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:5152 (5.0 KiB)  TX bytes:5152 (5.0 KiB)
> ## ----------------------------------------------------------------------
> > lsmod | egrep 'tulip|de2104x|de4x5'
>    
> tulip 	    57120       0
> > cat /etc/udev/rules.d/z25_persistent-net.rules
> on one line between '*'
> ************************************************************
> SUBSYSTEM=="net", DRIVERS=="?*",
>  ATTRS{address}=="00:80:9d:79:35:e1", NAME="eth"
                          ^                      ^
> ************************************************************

"address" does not match "HWaddr" in the ifconfig output and NAME should
be assigned as "eth0". I am afraid that these are just transcription
errors again, though.

You seem to have many errors, especially for RX packets. This might
indicate a general problem with the driver or a flaky ethernet cable. 

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |



Reply to: