| LinHES Forums http://forum.linhes.org/ |
|
| Destination Host not Reachable http://forum.linhes.org/viewtopic.php?f=2&t=11091 |
Page 1 of 2 |
| Author: | basketcase [ Sun Aug 06, 2006 4:29 pm ] |
| Post subject: | Destination Host not Reachable |
Okay, I've tried the latest release of Knoppmyth, Knoppix and Ubuntu 6.06 LTS. Computer is an Shuttle XPC SN41G2 Nvidia gforce 2 chipset AMD 1800+ Processor 512 DDR333 40gb HDD Using Onboard Vid and Nic PCI slot has a PVR-350 Tuner Card I want to run Mythtv....Knoppmyth is great, really love it, but I cannot get a network connection. Using the onboard NIC, I am able to run 'netcardconfig' assign a static IP address, able to ping 127.0.0.1 and the IP addreass of the NIC (192.168.1.250)..Successful replys....but I cannot ping the router (Linksys WRT54G). I know the ports on the router are good, because I can use them with my notebook. I know the cable is good because I use it on one of the other desktops in the house. When I try and ping the router (or any other address for that matter) I get a reply from the computer's IP address 'destination host unreachable'. I get the same reply in Knoppmyth, Knoppix and Ubuntu Dapper. Also I cannot ping the myth box with any other computer in the house. So I have a USB to Cat5 adapter (Linksys USB100M -- supported in Linux) -- Operating systems recognize it, able to assign an IP address to it, and ping it. When trying to ping the router, I will get 'destination host unreachable'. I disabled the onboard NIC and just used the USB NIC, same issue. Why do I not have any network connectivity on this box? The box is used, recently purchased from a coworker. Was running Windows XP SP2 on it. Said he had a few issues with the NIC when he bought it, but he just put in a NIC in the PCI slot and didn't worry about it. I need the available PCI slot for the PVR-350 card. Any ideas, suggestions, etc. would be greatly appreciated, as I'm considering e-baying the box, the card and anything else I have and just buying a Tivo. Thanks!! My biggest question is I can understand that the Onboard NIC might be dead, and so be it, but why isn't the USB one working? Thanks again! |
|
| Author: | mjl [ Mon Aug 07, 2006 6:36 am ] |
| Post subject: | |
Hi, The usb setup stuff isn't very complete so mileage will vary. As for the netcardconfig, save yourself some grief and try doing a dhcp first. If your router is enabled for it as then you will get the dns servers ip. Then try a ping to some other box. If it all works, then re-run netcardconfig and set your preferred ip, check gateway ip (it defaults to 254) while the dns will be retained 
Be sure it is turned on in the bios also. Mike |
|
| Author: | basketcase [ Mon Aug 07, 2006 1:59 pm ] |
| Post subject: | |
mjl wrote: Hi,
The usb setup stuff isn't very complete so mileage will vary. As for the netcardconfig, save yourself some grief and try doing a dhcp first. If your router is enabled for it as then you will get the dns servers ip. Then try a ping to some other box. If it all works, then re-run netcardconfig and set your preferred ip, check gateway ip (it defaults to 254) while the dns will be retained Be sure it is turned on in the bios also. Mike I have 6 other computers (lan and wifi) connected to the router. 3 are dhcp, 3 are staticly assigned. It is turned on in the BIOS. When trying to do a dhclient, it says that it cannot find any dhcp offers when it does it dhcpdiscover -- like it is not seeing the router. |
|
| Author: | mjl [ Mon Aug 07, 2006 2:57 pm ] |
| Post subject: | |
Hi, Ok, if dhcp doesn't work, give it a static, use the router gw for the dns also. When you plug in the cable, does the light come on? Had a issue once where the switch and the nic wouldn't talk nice, 100mb only sw with a cat3 cable to a 10mb nic. Look for stuff that may not match. Had mobo nic thjat was stupid once, found the auto power control in bios enabled. In general, carefully check everything. Best of luck. Mike |
|
| Author: | basketcase [ Mon Aug 07, 2006 4:17 pm ] |
| Post subject: | |
mjl wrote: Hi,
Ok, if dhcp doesn't work, give it a static, use the router gw for the dns also. When you plug in the cable, does the light come on? Had a issue once where the switch and the nic wouldn't talk nice, 100mb only sw with a cat3 cable to a 10mb nic. Look for stuff that may not match. Had mobo nic thjat was stupid once, found the auto power control in bios enabled. In general, carefully check everything. Best of luck. Mike I'm at work for another night. I do get link lights and even flashing link lights. The cable that I am using, I pulled off of another machine as it was the longest in the house. I have bulk Cat6 cable at the house, so I went and bought RJ-45 ends and made a new cable. Cables are good. I'll go through each page/option in the BIOS to see what is available. Appreciate your guy's help!! |
|
| Author: | mac [ Tue Aug 08, 2006 7:08 am ] |
| Post subject: | |
What shows up /var/log/messages when you unplug and replug the usb nic? after you get yourself setup with a static IP address and run a few ping tests to the router - post the output of "ifconfig" , "route -n" and "cat /proc/net/arp" also open a seperate xterm from the one that running the ping in and run the command "tcpdump -n" as root while you doing the ping. Post that output as well. If its not easy for post this info this is what I am looking for: ifconfig: TX and RX lines. Are there incomming or outgoing packets? Errors? etc. route -n: Is there a host route for that interface? cat /proc/net/arp: Does the router ip address have a valid arp entry? tcpdump -n: What traffic are you seeing? Arp requests? ICMP ping packets? debugging network stuff under linux is fairly strait forward -- though I have no experence with the usb to cat5 dodad.. or dig up and old ISA nic and use it if all you need the net connection for is to pull listings. Quote: I'm considering e-baying the box, the card and anything else I have and just buying a Tivo.
whatever.. get yourself 99% of way there and toss in the towel at the first minor bump. |
|
| Author: | basketcase [ Tue Aug 08, 2006 1:09 pm ] |
| Post subject: | |
mac wrote: What shows up /var/log/messages when you unplug and replug the usb nic?
after you get yourself setup with a static IP address and run a few ping tests to the router - post the output of "ifconfig" , "route -n" and "cat /proc/net/arp" also open a seperate xterm from the one that running the ping in and run the command "tcpdump -n" as root while you doing the ping. Post that output as well. If its not easy for post this info this is what I am looking for: ifconfig: TX and RX lines. Are there incomming or outgoing packets? Errors? etc. route -n: Is there a host route for that interface? cat /proc/net/arp: Does the router ip address have a valid arp entry? tcpdump -n: What traffic are you seeing? Arp requests? ICMP ping packets? debugging network stuff under linux is fairly strait forward -- though I have no experence with the usb to cat5 dodad.. or dig up and old ISA nic and use it if all you need the net connection for is to pull listings. Quote: I'm considering e-baying the box, the card and anything else I have and just buying a Tivo. whatever.. get yourself 99% of way there and toss in the towel at the first minor bump. Here is what I found out.... ifconfig eth0: RX: Packets 0 Errors 49 Dropped 0 Overrun 0 Frame 49 TX: Packets 91 Errors 0 Dropped 0 Overrrun 0 Carrier 0 route -n 192.168.1.0 Gateway 0.0.0.0 Netmask 255.255.255.0 0.0.0.0 Gateway 192.168.1.1 Netmask 0.0.0.0 cat /proc/net/arp 192.168.1.1 Hardware Address 00:00:00:00:00:00 When trying to do a tcpdump -n, I get a command not found error. As far as /var/log/messages regarding when I unplug and replug the usb nic...The computer will lock up if I unplug or plug the nic in. Hot swapping via USB doesn't work too well. I also had the USB nic and I got a kernel panic when booting. Unplugged it, and all is well. As far as using an ISA nic, this computer has 1 AGP slot and 1 PCI slot. The PCI slot is being used by the PVR-350 card. |
|
| Author: | mjl [ Tue Aug 08, 2006 2:51 pm ] |
| Post subject: | |
Hi, Running the Ubuntu live, did the network function properly? You may have a marginal or bad burn and ended up with an improper install... Are there other items not seeming to work properly? Rerun the KM install with the boot: knoppmyth testcd to see if all checks (you can abort the actual install) Mike |
|
| Author: | basketcase [ Tue Aug 08, 2006 3:40 pm ] |
| Post subject: | |
mjl wrote: Hi,
Running the Ubuntu live, did the network function properly? You may have a marginal or bad burn and ended up with an improper install... Are there other items not seeming to work properly? Rerun the KM install with the boot: knoppmyth testcd to see if all checks (you can abort the actual install) Mike Did not work with Ubuntu live or Knoppix 5.0.1 Live CD. Same results with all 3 distros |
|
| Author: | mac [ Wed Aug 09, 2006 8:11 pm ] |
| Post subject: | |
do a lsmod and see if it using the the rtl8150 module. Quote: RX: Packets 0 Errors 49 Dropped 0 Overrun 0 Frame 49 Frame errors are usually because of a faulty cable -- But because you have ruled out the cable we need to look at the adapter itself. Are any of contacts bent in the female rj45 connector? Use the USB nic adapter on a windows box to verify that it works correctly. There may also be duplex mismach or a problem with the MTU setting. I don't think that it is the mtu though. Watch /var/log/messages as you unplug the ethernet cable. maybe also try dropping the MTU, you can use ifconfig to this like so "ifconfig <your usb-eth interface> mtu 1400" Quote: When trying to do a tcpdump -n, I get a command not found error.
An apt-get install tcpdump should not cause any problem. Try it, if it only wants to get the tcpdump and pcap debs your safe. |
|
| Author: | basketcase [ Wed Aug 09, 2006 8:19 pm ] |
| Post subject: | |
mac wrote: do a lsmod and see if it using the the rtl8150 module.
Quote: RX: Packets 0 Errors 49 Dropped 0 Overrun 0 Frame 49 Frame errors are usually because of a faulty cable -- But because you have ruled out the cable we need to look at the adapter itself. Are any of contacts bent in the female rj45 connector? Use the USB nic adapter on a windows box to verify that it works correctly. There may also be duplex mismach or a problem with the MTU setting. I don't think that it is the mtu though. Watch /var/log/messages as you unplug the ethernet cable. maybe also try dropping the MTU, you can use ifconfig to this like so "ifconfig <your usb-eth interface> mtu 1400" I don't think that this has anything to do with the dead onboard nic.. The above troubleshooting was done with the on-board NIC. When I tried to book the computer with the USB NIC in it, I got a Kernel panic. I unplugged the USB NIC and it booted. I do know that when it will boot, it is using the rtl8150 module, as I see it pop up during boot sequence. I'll look at the /var/log/messsages and see what happens. I'll also adjust the MTU and see what I can come up with. Appreciate your help, if anything this is great experience for future endeavors. |
|
| Author: | mac [ Wed Aug 09, 2006 8:58 pm ] |
| Post subject: | |
Quote: The above troubleshooting was done with the on-board NIC. When I tried to book the computer with the USB NIC in it, I got a Kernel panic. I unplugged the USB NIC and it booted.
I do know that when it will boot, it is using the rtl8150 module, as I see it pop up during boot sequence. lets take the on-board nic out of equation and just look at the usb thing. If the RX frame errors were with the on-board nic and you suspect that it is bad, well that explains that. Does booting with the USB nic kernel panic sometimes and not other times? This would be very troubling and could point to hardware issue.. maybe bad RAM? heat issues? When you boot without usb nic and then plug it in, does it kernel panic? Are you seeing errors on that interface after running some ping tests? shutdown your on-board network interface with "ifconfig eth0 down" before doing any tests with the usb nic. |
|
| Author: | basketcase [ Wed Aug 09, 2006 9:04 pm ] |
| Post subject: | |
mac wrote: Quote: The above troubleshooting was done with the on-board NIC. When I tried to book the computer with the USB NIC in it, I got a Kernel panic. I unplugged the USB NIC and it booted. I do know that when it will boot, it is using the rtl8150 module, as I see it pop up during boot sequence. lets take the on-board nic out of equation and just look at the usb thing. If the RX frame errors were with the on-board nic and you suspect that it is bad, well that explains that. Does booting with the USB nic kernel panic sometimes and not other times? This would be very troubling and could point to hardware issue.. maybe bad RAM? heat issues? When you boot without usb nic and then plug it in, does it kernel panic? Are you seeing errors on that interface after running some ping tests? shutdown your on-board network interface with "ifconfig eth0 down" before doing any tests with the usb nic. I want to say it only kernel panics when the USB NIC is plugged in, but no network cable is plugged into it. But I'll have to confirm that when I get home. I know if the computer is on, and I unplug the USB NIC, the computer will lock up. I can't remember if I ever plugged the NIC in while the computer was on, and what its response was. I'll shut down the onboard NIC, and do the above troubleshooting with the USB NIC. I do know that if I boot off of the CD and do the Install, it finds the USB NIC, but w/o booting off the CD, I think that is when I have issues. I'll be home in 3 hours, I can confirm. Thanks again for the advice. |
|
| Author: | basketcase [ Thu Aug 10, 2006 3:01 am ] |
| Post subject: | |
Kernel paniced when I turned the computer on...moved the usb nic to the usb port below it, restarted computer..loaded. Shutdown all eth* devices except eth1 (usb nic) ifconfig: RX: Packets 0 Errors 0 Dropped 0 Overrun 0 Frame 0 TX: Packets 114 Errors 0 Dropped 0 Overrun 0 Carrier 0 Route -n 192.168.1.0 GW = 0.0.0.0 NM = 255/24 0.0.0.0 GW = 192.168.1.1 NM = 0.0.0.0 /proc/net/arp 192.168.1.1 HW Address: 00:00:00:00:00:00 I did the ifconfig eth1 mtu 1400 Ran them again, same results Still when trying to ping Router -- destination host unreachable Restarted Computer Entered BIOS Loaded 'Safe Defaults' Disabled: FDC 1394 Onboard NIC Onboard AC97 Parallel Serial Rebooted -- kernel panic Moved USB Nic to Port above -- kernel panic Rebooted -- started up dhclient -- failed netcardconfig -- manually assigned addresses attempted to ping router -- destination host unreachable per Loading and shutting down drivers/usb/net/rtl8150 |
|
| Author: | basketcase [ Thu Aug 10, 2006 3:10 am ] |
| Post subject: | |
I telnetted into my router... Code: ------------------------------------------ Sveasoft Firmware for Wireless Routers Talisman USE OF THIS FIRMWARE IS AT YOUR OWN RISK http://www.sveasoft.com ------------------------------------------ BusyBox v1.01 (2005.10.16-13:59+0000) Built-in shell (ash) Enter 'help' for a list of built-in commands. SVEASOFT:~#ping 192.168.1.111 PING 192.168.1.111 (192.168.1.111): 56 data bytes --- 192.168.1.111 ping statistics --- 9 packets transmitted, 0 packets received, 100% packet loss SVEASOFT:~#ping 192.168.1.121 PING 192.168.1.121 (192.168.1.121): 56 data bytes SVEASOFT:~#exit telnetted back in Code: ------------------------------------------ Sveasoft Firmware for Wireless Routers Talisman USE OF THIS FIRMWARE IS AT YOUR OWN RISK http://www.sveasoft.com ------------------------------------------ BusyBox v1.01 (2005.10.16-13:59+0000) Built-in shell (ash) Enter 'help' for a list of built-in commands. SVEASOFT:~#ping 192.168.1.252 PING 192.168.1.252 (192.168.1.252): 56 data bytes 64 bytes from 192.168.1.252: icmp_seq=0 ttl=64 time=2.3 ms 64 bytes from 192.168.1.252: icmp_seq=1 ttl=64 time=1.9 ms 64 bytes from 192.168.1.252: icmp_seq=2 ttl=64 time=1.9 ms 64 bytes from 192.168.1.252: icmp_seq=3 ttl=64 time=1.9 ms 64 bytes from 192.168.1.252: icmp_seq=4 ttl=64 time=1.9 ms --- 192.168.1.252 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 1.9/1.9/2.3 ms SVEASOFT:~#route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0 68.64.8.0 0.0.0.0 255.255.248.0 U 0 0 0 vlan1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 68.64.8.1 0.0.0.0 UG 0 0 0 vlan1 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 br0 SVEASOFT:~#cat /proc/net/arp IP address HW type Flags HW address Mask Device 68.64.8.1 0x1 0x2 00:50:57:01:31:DE * vlan1 192.168.1.100 0x1 0x2 00:11:95:17:4A:F7 * br0 192.168.1.103 0x1 0x2 00:11:09:D2:16:68 * br0 192.168.1.102 0x1 0x2 00:0C:F1:B9:BB:9F * br0 192.168.1.252 0x1 0x2 00:18:39:69:F0:C8 * br0 192.168.1.111 0x1 0x2 00:10:60:E9:CB:21 * br0 192.168.1.121 0x1 0x0 00:00:00:00:00:00 * br0 If you look above...when I did the 'cat /proc/net/arp' it shows 192.168.1.111 and gives it a Hardware Address.... tcpdump -n didn't work on the router either. Code: SVEASOFT:~#ifconfig
br0 Link encap:Ethernet HWaddr 00:13:10:F8:CB:A4 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21056153 errors:0 dropped:0 overruns:0 frame:0 TX packets:20059537 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3583192103 (3.3 GiB) TX bytes:984268960 (938.6 MiB) eth0 Link encap:Ethernet HWaddr 00:13:10:F8:CB:A4 UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:28097809 errors:4 dropped:0 overruns:4 frame:4 TX packets:20823856 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1759745868 (1.6 GiB) TX bytes:3940676872 (3.6 GiB) Interrupt:5 Base address:0x2000 eth1 Link encap:Ethernet HWaddr 00:13:10:F8:CB:A6 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21502671 errors:17 dropped:0 overruns:0 frame:3337426 TX packets:20543671 errors:2359 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:4104682646 (3.8 GiB) TX bytes:1378432731 (1.2 GiB) Interrupt:4 Base address:0x1000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MULTICAST MTU:16436 Metric:1 RX packets:322 errors:0 dropped:0 overruns:0 frame:0 TX packets:322 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:24616 (24.0 KiB) TX bytes:24616 (24.0 KiB) vlan0 Link encap:Ethernet HWaddr 00:13:10:F8:CB:A4 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:468 errors:0 dropped:0 overruns:0 frame:0 TX packets:36621 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:35408 (34.5 KiB) TX bytes:5001670 (4.7 MiB) vlan1 Link encap:Ethernet HWaddr 00:11:09:D2:16:68 inet addr:68.64.14.81 Bcast:68.64.15.255 Mask:255.255.248.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28097330 errors:0 dropped:0 overruns:0 frame:0 TX packets:20787235 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1253949348 (1.1 GiB) TX bytes:3935675202 (3.6 GiB) wds0.4915 Link encap:Ethernet HWaddr 00:13:10:F8:CB:A6 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) I don't really know what I'm looking at, but I figure I'll get as much information as I can, and go from there. Thanks!! |
|
| Page 1 of 2 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|