LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Ping Problem "Destination Host Unreachable" (https://www.linuxquestions.org/questions/linux-networking-3/ping-problem-destination-host-unreachable-784268/)

jia786 01-23-2010 04:52 PM

Ping Problem "Destination Host Unreachable"
 
I have 2 machines ebdb1 (Oracle VM machine) and aasbanas (Openfiler). ebdb1 has 3 interfaces and aasbanas has 2. Following are contents of /etc/hosts file on both

192.168.1.81 ebas1
192.168.1.61 ebdb1
192.168.1.62 ebdb2
192.168.1.30 aasbanas
192.168.2.11 ebdb1-priv
192.168.2.12 ebdb2-priv
192.168.1.71 ebdb1-vip
192.168.1.72 ebdb2-vip
192.168.2.31 aasbanas-priv

Now I can ping ebdb1 and aasbanas from both machines but can't ping ebdb1-priv and aasbanas-priv from eachother and get error "Destination Host Unreachable". Following is some dianostic data.

/etc/resolv.conf on both machine has following line.
nameserver 192.168.1.1

[root@ebdb1 ~]# cat /etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=ebdb1
GATEWAY=192.168.1.1

[root@aasbanas ~]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=aasbanas
GATEWAY=192.168.1.1
NETWORKING_IPV6=no

[root@aasbanas ~]# ping ebdb1-priv
PING ebdb1-priv (192.168.2.11) 56(84) bytes of data.
.... HANGS here.

[root@ebdb1 ~]# ping aasbanas-priv
PING aasbanas-priv (192.168.2.31) 56(84) bytes of data.
From ebdb1-priv (192.168.2.11) icmp_seq=1 Destination Host Unreachable
From ebdb1-priv (192.168.2.11) icmp_seq=2 Destination Host Unreachable

[root@ebdb1 ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

[root@aasbanas ~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0


[root@ebdb1 ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:3E:1D:97:2F
inet addr:192.168.1.61 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe1d:972f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:14550 errors:0 dropped:0 overruns:0 frame:0
TX packets:2103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2736590 (2.6 MiB) TX bytes:243681 (237.9 KiB)

eth1 Link encap:Ethernet HWaddr 00:16:3E:0A:4E:DA
inet addr:192.168.2.11 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:3eff:fe0a:4eda/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:8502 (8.3 KiB)

eth2 Link encap:Ethernet HWaddr 00:16:3E:38:A2:A0
BROADCAST 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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:74 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9520 (9.2 KiB) TX bytes:9520 (9.2 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[root@aasbanas ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:50:43:00:45:3E
inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:43ff:fe00:453e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:5883 errors:0 dropped:0 overruns:0 frame:0
TX packets:3853 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:438269 (427.9 Kb) TX bytes:257501 (251.4 Kb)
Interrupt:16

eth1 Link encap:Ethernet HWaddr 00:0A:E4:8B:B3:6D
inet addr:192.168.2.31 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:fe8b:b36d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:4369 errors:0 dropped:0 overruns:0 frame:0
TX packets:1081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:347549 (339.4 Kb) TX bytes:35678 (34.8 Kb)
Interrupt:16

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:1058 errors:0 dropped:0 overruns:0 frame:0
TX packets:1058 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19460 (19.0 Kb) TX bytes:19460 (19.0 Kb)

nimnull22 01-23-2010 05:09 PM

Where do you connect eth1 of the "ebdb1" to? And where do you connect eth1 of the "aasbanas" to?

jia786 01-23-2010 05:43 PM

I'm sorry if I mis-understood your question. ebdb1 is VM on server connected to router and aasbanas is also connected to same router.

jia786 01-24-2010 11:36 AM

Any help on this issue will be really appreciated.

nimnull22 01-24-2010 12:11 PM

Can you ping 192.168.2.31 on aasbanas and 192.168.2.11 on ebdb1

jia786 01-24-2010 12:15 PM

Just to add to my first message, I can ping to outside world (e.g. google.com)

[root@ebdb1 ~]# ping -a 209.85.135.104
PING 209.85.135.104 (209.85.135.104) 56(84) bytes of data.
64 bytes from 209.85.135.104: icmp_seq=1 ttl=50 time=117 ms
64 bytes from 209.85.135.104: icmp_seq=2 ttl=50 time=126 ms
64 bytes from 209.85.135.104: icmp_seq=3 ttl=50 time=114 ms
64 bytes from 209.85.135.104: icmp_seq=4 ttl=50 time=114 ms


[root@aasbanas ~]# ping 209.85.135.104
PING 209.85.135.104 (209.85.135.104) 56(84) bytes of data.
64 bytes from 209.85.135.104: icmp_seq=0 ttl=50 time=127 ms
64 bytes from 209.85.135.104: icmp_seq=1 ttl=50 time=123 ms
64 bytes from 209.85.135.104: icmp_seq=2 ttl=50 time=115 ms
64 bytes from 209.85.135.104: icmp_seq=3 ttl=50 time=117 ms
64 bytes from 209.85.135.104: icmp_seq=4 ttl=50 time=113 ms

nimnull22 01-24-2010 12:20 PM

Ok, I ask again:
Can you ping 192.168.2.31 on aasbanas?

jia786 01-24-2010 02:41 PM

Quote:

Originally Posted by nimnull22 (Post 3838840)
Ok, I ask again:
Can you ping 192.168.2.31 on aasbanas?

Yes I can.

[root@aasbanas ~]# ping 192.168.2.31
PING 192.168.2.31 (192.168.2.31) 56(84) bytes of data.
64 bytes from 192.168.2.31: icmp_seq=0 ttl=64 time=0.110 ms
64 bytes from 192.168.2.31: icmp_seq=1 ttl=64 time=0.063 ms
64 bytes from 192.168.2.31: icmp_seq=2 ttl=64 time=0.056 ms
64 bytes from 192.168.2.31: icmp_seq=3 ttl=64 time=0.057 ms
^C
--- 192.168.2.31 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3012ms
rtt min/avg/max/mdev = 0.056/0.071/0.110/0.023 ms, pipe 2
[root@aasbanas ~]#

nimnull22 01-24-2010 02:53 PM

Do please on aasbanas:
arp -n -i eth1

Post output.

Thanks.

jia786 01-24-2010 03:03 PM

Quote:

Originally Posted by nimnull22 (Post 3838956)
Do please on aasbanas:
arp -n -i eth1

Post output.

Thanks.

[root@aasbanas ~]# arp -n -i eth1
arp: in 2 entries no match found

Thanks.

nimnull22 01-24-2010 03:06 PM

Do please on aasbanas:
arp -n -i eth0

Post output.

Thanks.

jia786 01-24-2010 05:10 PM

Quote:

Originally Posted by nimnull22 (Post 3838966)
Do please on aasbanas:
arp -n -i eth0

Post output.

Thanks.

From console I get following

[root@aasbanas ~]# arp -n -i eth0
Address HWtype HWaddress Flags Mask Iface
192.168.1.103 ether 00:13:02:5d:8c:d0 C eth0

And from win xp using putty I get following. 192.168.1.103 is IP address of my win xp laptop.

[root@aasbanas ~]# arp -n -i eth0
Address HWtype HWaddress Flags Mask Iface
192.168.1.103 ether 00:13:02:5d:8c:d0 C eth0
192.168.1.1 ether 00:16:b6:da:f4:08 C eth0

nimnull22 01-24-2010 05:45 PM

Try to do on aasbanas:

ping -b 192.168.2.255

Post output please.

jia786 01-24-2010 06:00 PM

It hangs on following

[root@aasbanas ~]# ping -b 192.168.2.255
WARNING: pinging broadcast address
PING 192.168.2.255 (192.168.2.255) 56(84) bytes of data.

and I get same behaviour on ebdb1 too.

nimnull22 01-24-2010 06:03 PM

You know, I would say that interface eth1 doesn't connect to anything. Because it doesn't see anything.
But I have no idea about WM and hope that others from this forum help you.


All times are GMT -5. The time now is 02:57 AM.