Darrell D. Mobley wrote: > Here's ifconfig output: > > eth0 Link encap:Ethernet HWaddr 00:0B:CD:41:1B:DE > inet addr:208.77.219.98 Bcast:208.77.219.111 > Mask:255.255.255.240 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:953043 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1191134 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:142255854 (135.6 MiB) TX bytes:1067211233 (1017.7 MiB) > Interrupt:193 Memory:f7df0000-f7e00000
The above confirms that your network is running clean at the physical layer. Your datacenter can also confirm that by viewing their switchport metrics on the drop to your equipment, looking for incrementing errors and/or collisions. (Here I am both confirming and mentioning.) :) Steve H's advice may be dead on, although I'm not sure what the cause would be. It's possible that the eth0:0 being a duplicate IP of the eth0 may have gotten tangled in there somehow, but I couldn't speculate as to the why. -- Chris Gebhardt VIRTBIZ Internet Services Access, Web Hosting, Colocation, Dedicated www.virtbiz.com | toll-free (866) 4 VIRTBIZ _______________________________________________ Blueonyx mailing list [email protected] http://www.blueonyx.it/mailman/listinfo/blueonyx
