You have a serious problem there. You should never see that many errors. You ether have a bad or crappy ethernet cable, bad NIC/HUB/SWITCH, or you are trying to run full duplex on a half-duplex network.
Originally posted by omnius
I figured out a bandaid fix. It turns out that as long as I bring eth0 back up before the transfer's timeout happens, it picks it right back up and keeps on transfering. So I just wrote a little shell script that checks every 10 seconds to see if eth0 is up or not, and brings it back up if its down.
This is a question for you gurus out there. Is there a possible reason besides a troubled network connection for ifconfig to be reporting this many errors on eth0?
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29184 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:87535478 dropped:58115 overruns:1 carrier:0 coll:0
Thats showing 0 packets transmitted but a whole crapload of errors and drops. Is that perhaps a bug and its switching the transmitted packects with the errors? Since I'm sending large files from the tivo to my computer, there should be a heck of a lot more than 0 transmitted packets.
SpongeBob is not a contraceptive - Bart S.
A tabloid, is that one of those really strong mints? - Homer S.