Michael C. Toren on 7 Nov 2003 11:55:04 -0500 |
On Wed, Nov 05, 2003 at 06:33:50PM -0500, kaze wrote: > I pulled the 3COM NIC and put the LNE-100TX in, RH detected the new hardware > [root@sa root]# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:A0:FF:FF:9E:B6 > inet addr:10.10.10.50 Bcast:10.10.10.255 Mask:255.255.255.0 An internal network of 10.10.10/24; okay. > [root@sa root]# ping 10.10.10.50 > PING 10.10.10.50 (10.10.10.50) 56(84) bytes of data. > 64 bytes from 10.10.10.50: icmp_seq=1 ttl=64 time=0.066 ms And you're able to ping yourself, which is good -- just remember that pinging yourself actually uses the loopback interface, not the network interface, and has nothing to do with your network driver. > [root@sa root]# ping 10.10.10.211 > PING 10.10.10.211 (10.10.10.211) 56(84) bytes of data. > From 10.10.10.50 icmp_seq=1 Destination Host Unreachable When attempting to ping a locally connected IP address and an ICMP host unreachable message such as this one is generated, with a source address of your local address, it generally indicates that you aren't able to arp for the destination address. What does "arp -an" say for the 10.10.10.50 address -- "incomplete", or does it return a valid MAC address? On Wed, Nov 05, 2003 at 06:43:30PM -0500, Paul wrote: > That IP address looks a little strange, doesn't it? Nope, it's perfectly valid. Both 10.10.10.50 and 10.10.10.211 are in the same subnet 10.10.10/24. The 10.10.10.211 address should be reachable from 10.10.10.50 even with no default route. -mct ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|