ping: Destination host unreachable.

two computers, arrakis and caladan, are connected
with a crossover cable. why does ping give a
"destination host unreachable" error, please?


I'm referencing /usr/share/doc/initscripts-7.93.7/sysconfig.txt
to configure eth1 on arrakis.

here's the /etc/sysconfig/network-scripts/ifcfg-eth1 file
for arrakis:

# D-Link System Inc RTL8139 Ethernet
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HOSTNAME=arrakis
HWADDR=00:0D:88:37:FA:22
NETMASK=255.255.255.0
IPADDR=192.168.10.255
USERCTL=yes
PEERDNS=yes
TYPE=Ethernet
IPV6INIT=yes


here are the results from running system-config-network
on arrakis:

device says: eth 1 is active
hardware says:
eth1 is described as D-Link System Inc RTL8139 Ethernet
DNS says:
hostname: localhost.localdomain
Primary DNS: 192.168.2.1
DNS search path: localdomain


this is actually from gnome -> system settings -> network

and then cd /etc/init.d and "./network restart" gives:


[root@localhost init.d]# ./network restart
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... failed; no link present. Check
cable?
[FAILED]
Bringing up interface eth1: [ OK ]
[root@localhost init.d]#


all of the above applies to a computer named "arrakis".


from caladan,


Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ping 192.168.10.255

Pinging 192.168.10.255 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 192.168.10.255:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CALADAN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-50-DA-68-8C-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.49.37
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\>



links

<http://www.thesourcecc.com/estore/Product.aspx?language=en-CA&catalog=Online&category=Network_Cable&product=2 608030>
crossover cable
<http://www.ecsusa.com/downloads/manual_k7s.html> arrakis mother board
<http://usa.asus.com/prog/spec.asp?m=WL-330g&langs=09> wi-fi adapter
<http://www.dlink.ca/product.php?PID=124> eth1 NIC on arrakis


thanks,

Thufir

<(E-Mail Removed)> schrieb
> two computers, arrakis and caladan, are connected
> with a crossover cable. why does ping give a
> "destination host unreachable" error, please?
>
> [...]
> IPADDR=192.168.10.255
I wouldn't take .255 as an ip address. Isn't this a broadcast
address?

>
> [...]
> all of the above applies to a computer named "arrakis".
>
You seem to have eth0 and eth1 on "arrakis". Are you
sure the cable on eth1 is connected to "caladan"?

>
> from caladan,
>
>
> Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
>
> C:\>ping 192.168.10.255
>
> Pinging 192.168.10.255 with 32 bytes of data:
>
> Destination host unreachable.
>
The computer is known to "caladan", but it does not seem
to be up or is unreachable (as opposed to unknown hosts,
or a router in between refuses to transport packets).

>
> C:\>ipconfig /all
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : CALADAN
> Primary DNS Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> [...]
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Autoconfiguration IP Address. . . : 169.254.49.37
This is not a 196.168.0.0/255.255.255.0 address

Do the lamps at the adapter cards light up?
If you ping, do they blink?
What says ifconfig on "arrakan"?

HTH
Martin

Martin Blume wrote:
....
> What says ifconfig on "arrakan"?
....

forgot to run ifconfig. however, some progress


the following static IP addresses give mixed results:
arrakis eth0 192.168.10.123
arrakis eth1 192.168.10.124
caladan 192.168.10.125


pinging caladan from arrakis eth0 gave good results.
pinging caladan from arrakis eth1 gave poor results.

I made sure to run "./network restart" on arrakis
between attempts. when the network script was restarted
on arrakis a message would pop up on caladan saying
"network unplugged" and then "network connected".

I'm 99.99999999% sure that eth0 refers to the built-in
jack and eth1 refers to the D-Link NIC.


so, why is eth1 not working as well as eth0?
when the crossover cable is plugged into the arrakis
eth1 jack and arrakis pings caladan the red light
on arrakis eth1 flickers.


grr. forgot to run ifconfig on arrakis. anyhow,
here's some data:

[root@arrakis init.d]#
[root@arrakis init.d]#
[root@arrakis init.d]# ./network restart
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
[root@arrakis init.d]# ping 192.168.10.125
PING 192.168.10.125 (192.168.10.125) 56(84) bytes of data.
>From 192.168.10.123 icmp_seq=1 Destination Host Unreachable
>From 192.168.10.123 icmp_seq=2 Destination Host Unreachable
>From 192.168.10.123 icmp_seq=3 Destination Host Unreachable

--- 192.168.10.125 ping statistics ---
7 packets transmitted, 0 received, +3 errors, 100% packet loss, time
5999ms
, pipe 4
[root@arrakis init.d]# ./network restart
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
[root@arrakis init.d]# ./network restart
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
[root@arrakis init.d]#
[root@arrakis init.d]#
[root@arrakis init.d]#
[root@arrakis init.d]# ping 192.168.10.125
PING 192.168.10.125 (192.168.10.125) 56(84) bytes of data.
64 bytes from 192.168.10.125: icmp_seq=0 ttl=128 time=1.30 ms
64 bytes from 192.168.10.125: icmp_seq=1 ttl=128 time=0.257 ms
64 bytes from 192.168.10.125: icmp_seq=2 ttl=128 time=0.259 ms
64 bytes from 192.168.10.125: icmp_seq=3 ttl=128 time=0.255 ms
64 bytes from 192.168.10.125: icmp_seq=4 ttl=128 time=0.261 ms

--- 192.168.10.125 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.255/0.468/1.308/0.420 ms, pipe 2
[root@arrakis init.d]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# built-in
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
HOSTNAME=arrakis
#HWADDR=00:0D:88:37:FA:22
NETMASK=255.255.255.0
IPADDR=192.168.10.123
USERCTL=yes
PEERDNS=yes
TYPE=Ethernet
IPV6INIT=yes

[root@arrakis init.d]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# D-Link System Inc RTL8139 Ethernet
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HOSTNAME=arrakis
HWADDR=00:0D:88:37:FA:22
NETMASK=255.255.255.0
IPADDR=192.168.10.124
USERCTL=yes
PEERDNS=yes
TYPE=Ethernet
IPV6INIT=yes
[root@arrakis init.d]#




thanks,

Thufir

<(E-Mail Removed)> schrieb
>
> the following static IP addresses give mixed results:
> arrakis eth0 192.168.10.123
> arrakis eth1 192.168.10.124
> caladan 192.168.10.125
>
>
> pinging caladan from arrakis eth0 gave good results.
> pinging caladan from arrakis eth1 gave poor results.
>
I am not sure that using the same network on two cards
is a good idea.

If caladan has only one network connector, then a ping
must go through the cross-over cable.

HTH
Martin

Martin Blume wrote:
....
> > the following static IP addresses give mixed results:
> > arrakis eth0 192.168.10.123
> > arrakis eth1 192.168.10.124
> > caladan 192.168.10.125
> >
> >
> > pinging caladan from arrakis eth0 gave good results.
> > pinging caladan from arrakis eth1 gave poor results.
> >
> I am not sure that using the same network on two cards
> is a good idea.
>
> If caladan has only one network connector, then a ping
> must go through the cross-over cable.
....

yes, caladan has only one network connector.
arrakis has two ethernet jacks. I don't follow
this implication.

should arrakis eth0 and eth1 have new and different
ip address'?


ping from caladan with the connection to
arrakis eth0:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>cd ..

C:\Documents and Settings>cd ..

C:\>ping 192.168.10.123

Pinging 192.168.10.123 with 32 bytes of data:

Reply from 192.168.10.123: bytes=32 time<10ms TTL=64
Reply from 192.168.10.123: bytes=32 time<10ms TTL=64
Reply from 192.168.10.123: bytes=32 time<10ms TTL=64
Reply from 192.168.10.123: bytes=32 time<10ms TTL=64

Ping statistics for 192.168.10.123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ping 192.168.10.124

Pinging 192.168.10.124 with 32 bytes of data:

Reply from 192.168.10.124: bytes=32 time<10ms TTL=64
Reply from 192.168.10.124: bytes=32 time<10ms TTL=64
Reply from 192.168.10.124: bytes=32 time<10ms TTL=64
Reply from 192.168.10.124: bytes=32 time<10ms TTL=64

Ping statistics for 192.168.10.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CALADAN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI
For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-50-DA-68-8C-B2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.125
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\>


same setup, from arrakis:

[root@arrakis init.d]#
[root@arrakis init.d]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:E6:A0:24:27
inet addr:192.168.10.123 Bcast:192.168.10.255
Mask:255.255.255.0
inet6 addr: fe80::20a:e6ff:fea0:2427/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:170 errors:2 dropped:0 overruns:0 frame:2
TX packets:107 errors:0 dropped:0 overruns:0 carrier:0
collisions:4 txqueuelen:1000
RX bytes:21444 (20.9 KiB) TX bytes:7086 (6.9 KiB)
Interrupt:5 Base address:0xd400

eth1 Link encap:Ethernet HWaddr 00:0D:88:37:FA:22
inet addr:192.168.10.124 Bcast:192.168.10.255
Mask:255.255.255.0
inet6 addr: fe80::20d:88ff:fe37:fa22/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:888 (888.0 b) TX bytes:3708 (3.6 KiB)
Interrupt:5 Base address:0xd000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:108 errors:0 dropped:0 overruns:0 frame:0
TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8528 (8.3 KiB) TX bytes:8528 (8.3 KiB)

[root@arrakis init.d]# ping 192.168.10.125
PING 192.168.10.125 (192.168.10.125) 56(84) bytes of data.
64 bytes from 192.168.10.125: icmp_seq=0 ttl=128 time=0.476 ms
64 bytes from 192.168.10.125: icmp_seq=1 ttl=128 time=0.468 ms
64 bytes from 192.168.10.125: icmp_seq=2 ttl=128 time=0.473 ms
64 bytes from 192.168.10.125: icmp_seq=3 ttl=128 time=0.470 ms
64 bytes from 192.168.10.125: icmp_seq=4 ttl=128 time=0.472 ms
64 bytes from 192.168.10.125: icmp_seq=5 ttl=128 time=0.460 ms

--- 192.168.10.125 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5001ms
rtt min/avg/max/mdev = 0.460/0.469/0.476/0.028 ms, pipe 2
[root@arrakis init.d]#


thanks,

Thufir

<(E-Mail Removed)> schrieb
> Martin Blume wrote:
> ...
> > > the following static IP addresses give mixed results:
> > > arrakis eth0 192.168.10.123
> > > arrakis eth1 192.168.10.124
> > > caladan 192.168.10.125
> > >
> > >
> > > pinging caladan from arrakis eth0 gave good results.
> > > pinging caladan from arrakis eth1 gave poor results.
> > >
> > I am not sure that using the same network on two cards
> > is a good idea.
> >
> > If caladan has only one network connector, then a ping
> > must go through the cross-over cable.
> ...
>
> yes, caladan has only one network connector.
> arrakis has two ethernet jacks. I don't follow
> this implication.
>
If there is only one cable between caladan and arrakis,
any connection between the two must go thru this cable
(assuming these are not wireless interfaces).
So, having the cable in eth0, the interface eth1 does not
serve any useful purpose.

> should arrakis eth0 and eth1 have new and different
> ip address'?
They should be in different networks, IMHO.

>
>
> ping from caladan with the connection to
> arrakis eth0:
>
> [pings snipped]
>
You should be able to ping .123 and .124 from caladan, both
pings go through eth0 (assuming that is where the cable is).

Also, reverse you should be able to ping .125 from either
..123 or .124, both pings leave through the cable and its
associated ethX.

If you exchange the cable, the pings should resume working
after a certain timeout (IIRC, I'm not so sure about that,
might be that they work only after you initiate the
connection from the dual-interface box).

What do you want to achieve?

HTH
Martin

> Also, reverse you should be able to ping .125 from either
> .123 or .124, both pings leave through the cable and its
> associated ethX.
Not likely, because there will be only one routing table entry.

>>should arrakis eth0 and eth1 have new and different
>>ip address'?
> They should be in different networks, IMHO.

Yes. To see what is going on, run "route -n" (or "ip route show") on
arrakis.

Martin Blume wrote:
....
> If there is only one cable between caladan and arrakis,
> any connection between the two must go thru this cable
> (assuming these are not wireless interfaces).
> So, having the cable in eth0, the interface eth1 does not
> serve any useful purpose.
>
> > should arrakis eth0 and eth1 have new and different
> > ip address'?
> They should be in different networks, IMHO.

arrakis ip address 192.168.10.123
caladan ip address 192.168.11.124

like that? I don't know what a network is in
this context.

....
> You should be able to ping .123 and .124 from caladan, both
> pings go through eth0 (assuming that is where the cable is).
>
> Also, reverse you should be able to ping .125 from either
> .123 or .124, both pings leave through the cable and its
> associated ethX.

yes, that's basically the case.

....
> What do you want to achieve?
....


both computers connected to the internet simultaneously.

these computers can only access the internet wirelessly,
with an asus wi-fi adapter (wl-330g). at the moment
the wl-330g only works in caladan.

so, I need to get the wl-330g working in arrakis.
I want to set up IP masquerading on arrakis. first
I need to get both NIC's in arrakis working, though.


thanks,

Thufir

"Allen McIntosh" schrieb
> > Also, reverse you should be able to ping .125 from either
> > .123 or .124, both pings leave through the cable and its
> > associated ethX.
> Not likely, because there will be only one routing table
> entry.
Yes, you're right. Actually, IIRC, you can't specify what
interface to take (for ping or any other service), the
routing tables will specify.

>
> >>should arrakis eth0 and eth1 have new and different
> >>ip address'?
> > They should be in different networks, IMHO.
>
> Yes. To see what is going on, run "route -n" (or "ip route
> show") on arrakis.

<(E-Mail Removed)> schrieb
> Martin Blume wrote:
> ...
> > If there is only one cable between caladan and arrakis,
> > any connection between the two must go thru this cable
> > (assuming these are not wireless interfaces).
> > So, having the cable in eth0, the interface eth1 does not
> > serve any useful purpose.
> >
> > > should arrakis eth0 and eth1 have new and different
> > > ip address'?
> > They should be in different networks, IMHO.
>
> arrakis ip address 192.168.10.123
> caladan ip address 192.168.11.124
>
> like that?
No. I meant, that if you have different network adapters
in a computer, each one should be in a different network
(unless you know what you're doing and how you'd do it,
but then you wouldn't be asking here).
I meant that arrakis eth0 and eth1 should be different
networks.

> I don't know what a network is in this context.
>
In this context it is a local network: Computers that have
the same internet addresses (net part) and same netmask,
such as e.g. 192.168.0.x / 255.255.255.0, where 192.168.0
is the net part of the internet address and x is the
unique identifier for each computer (actually its network
interface).
Furthermore, they are all connected directly to each other,
so no routing takes place and all traffic passes directly
from sender to destination.


>
> ...
> > You should be able to ping .123 and .124 from caladan,
> > both pings go through eth0 (assuming that is where the
> > cable is).
> > [...]
>
>
> yes, that's basically the case.
>
> ...
> > What do you want to achieve?
> ...
>
>
> both computers connected to the internet simultaneously.
>
> these computers can only access the internet wirelessly,
> with an asus wi-fi adapter (wl-330g). at the moment
> the wl-330g only works in caladan.
>
> so, I need to get the wl-330g working in arrakis.
> I want to set up IP masquerading on arrakis. first
> I need to get both NIC's in arrakis working, though.
>
No we get yet another network interface in here: wireless.

arrakis (linux) has eth0 and eth1, with both interfaces
cable, yes?
caladan (w2k) has eth0, cable, yes?

Do both computers have wireless?
Do you have a wireless access point?
Or do you to the internet via cable?

Regards
Martin