I can't figure this one out. There's a Belken USB->Ethernet adapter as eth2 on my server. After a reboot it doesn't communicate with anything ever though it's up:
ipaddress is 68.15.6.136 gateway is 68.15.6.129
# ifconfig eth2 eth2 Link encap:Ethernet HWaddr 00:05:1B:00:52:BF inet addr:68.15.6.136 Bcast:68.15.6.191 Mask:255.255.255.192 inet6 addr: fe80::205:1bff:fe00:52bf/64 Scope:Link UP BROADCAST MULTICAST MTU:1536 Metric:1 RX packets:208 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13540 (13.2 KiB) TX bytes:0 (0.0 b)
it can ping itself:
# ping 68.15.6.136 PING 68.15.6.136 (68.15.6.136) 56(84) bytes of data. 64 bytes from 68.15.6.136: icmp_seq=0 ttl=64 time=0.056 ms 64 bytes from 68.15.6.136: icmp_seq=1 ttl=64 time=0.021 ms
--- 68.15.6.136 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.021/0.038/0.056/0.018 ms, pipe 2
can't ping the gateway:
# ping 68.15.6.129 PING 68.15.6.129 (68.15.6.129) 56(84) bytes of data. From 68.15.6.136 icmp_seq=0 Destination Host Unreachable
bounce the interface:
# ifconfig eth2 down # ifconfig eth2 up
now it works:
# ping 68.15.6.129 PING 68.15.6.129 (68.15.6.129) 56(84) bytes of data. 64 bytes from 68.15.6.129: icmp_seq=0 ttl=64 time=64.4 ms 64 bytes from 68.15.6.129: icmp_seq=1 ttl=64 time=12.3 ms 64 bytes from 68.15.6.129: icmp_seq=2 ttl=64 time=12.3 ms
Any ideas?
Jack
On 16/03/06, Jack Bailey jack@internetguy.net wrote:
I can't figure this one out. There's a Belken USB->Ethernet adapter as eth2 on my server. After a reboot it doesn't communicate with anything ever though it's up: bounce the interface:
# ifconfig eth2 down # ifconfig eth2 up
now it works:
I don't know anything about how the USB->Ethernet dongle's setup (kernel modules etc.) but does it require something to be started that's not being run until after S10network in the init scripts?
Are there any errors in /var/log/messages or dmesg for ethernet or USB devices?
Will.
I can't figure this one out. There's a Belken USB->Ethernet adapter as eth2 on my server. After a reboot it doesn't communicate with anything ever though it's up: bounce the interface:
# ifconfig eth2 down # ifconfig eth2 up
now it works:
I don't know anything about how the USB->Ethernet dongle's setup (kernel modules etc.) but does it require something to be started that's not being run until after S10network in the init scripts?
Are there any errors in /var/log/messages or dmesg for ethernet or USB devices?
No errors that I can see. CentOS saw the device when I plugged it in, and after configuring it, it worked. It stops working after a reboot, but will come up and begin working once again after I bounce the interface.
Jack
On Thu, 2006-03-16 at 02:16 -0800, Jack Bailey wrote:
I can't figure this one out. There's a Belken USB->Ethernet adapter as eth2 on my server. After a reboot it doesn't communicate with anything ever though it's up: bounce the interface:
# ifconfig eth2 down # ifconfig eth2 up
now it works:
I don't know anything about how the USB->Ethernet dongle's setup (kernel modules etc.) but does it require something to be started that's not being run until after S10network in the init scripts?
Are there any errors in /var/log/messages or dmesg for ethernet or USB devices?
No errors that I can see. CentOS saw the device when I plugged it in, and after configuring it, it worked. It stops working after a reboot, but will come up and begin working once again after I bounce the interface.
I had a similar issue the other day. Appareantly the nic and the switch did not agree on things. Check with ethtool if the nic is set to the right speed etc. If you see 10Mbit/s & half duplex it's likely they messed up negotiating something sensible. Set/force the right settings on either the nic or the switch. Iirc it's best pratice to not use autonegotiate on e.g. a switch to prevent these things from happening.
Hope this helps.
Regards, Patrick
-
Jack Bailey -
Patrick -
Will McDonald