mokkan
asked on
Linux network quesiton
I can ping to my physical Linux box which is 192.168.0.10 it is directly connected to my internet route (192.168.0.1), but from my physical linux machine I can't ping 192.168
[root@localhost ~]# ip route
192.168.72.0/24 dev eth0 proto kernel scope link src 192.168.72.143
default via 192.168.72.2 dev eth0
[root@localhost ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.72.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.72.2 0.0.0.0 UG 0 0 0 eth0
[root@localhost ~]# ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 192.168.0.10: icmp_seq=1 ttl=128 time=5.12 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=128 time=2.53 ms
64 bytes from 192.168.0.10: icmp_seq=3 ttl=128 time=2.50 ms
^C
--- 192.168.0.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2546ms
rtt min/avg/max/mdev = 2.506/3.388/5.124/1.228 ms
Physical machine output
[root@localhost(phy) ~]#ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.10 metric 1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
default via 192.168.0.1 dev eth0 proto static
[root@localhost (phy)~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Isn't it suppose to work? What am I doing wrong here?
[root@localhost ~]# ip route
192.168.72.0/24 dev eth0 proto kernel scope link src 192.168.72.143
default via 192.168.72.2 dev eth0
[root@localhost ~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.72.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.72.2 0.0.0.0 UG 0 0 0 eth0
[root@localhost ~]# ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10) 56(84) bytes of data.
64 bytes from 192.168.0.10: icmp_seq=1 ttl=128 time=5.12 ms
64 bytes from 192.168.0.10: icmp_seq=2 ttl=128 time=2.53 ms
64 bytes from 192.168.0.10: icmp_seq=3 ttl=128 time=2.50 ms
^C
--- 192.168.0.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2546ms
rtt min/avg/max/mdev = 2.506/3.388/5.124/1.228 ms
Physical machine output
[root@localhost(phy) ~]#ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.10 metric 1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
default via 192.168.0.1 dev eth0 proto static
[root@localhost (phy)~]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Isn't it suppose to work? What am I doing wrong here?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I found the problem, if my explanation is or assumption is wrong, please correct me.
From vmware default gateway is 192.168.72.2, and if there is no traffic within this subnet it will routed to 192.168.0.1, and then it will reach my 192.168.0.10 physical box, but from physical box when it wants to reach to 192.168.72.143, in needs to go to default gatway 192.168.0.1, and it doesn't know about 192.168.72.2 gateway. Am I right? Please correct me.
From vmware default gateway is 192.168.72.2, and if there is no traffic within this subnet it will routed to 192.168.0.1, and then it will reach my 192.168.0.10 physical box, but from physical box when it wants to reach to 192.168.72.143, in needs to go to default gatway 192.168.0.1, and it doesn't know about 192.168.72.2 gateway. Am I right? Please correct me.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you 192.168.72.143 it's a VM and located in my Vmware Workstation. I'm running VMware workstation from my laptop.
ASKER
Anyone can help ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This one is virtual network adapter? I may be missing the network fundamental here. If I am wrong correct me
Because our internet router 192.168.0.1 doesn't know about 192.168.72.1, but 192.168.72.1 know about 192.168.0.1. Am I right?
Because our internet router 192.168.0.1 doesn't know about 192.168.72.1, but 192.168.72.1 know about 192.168.0.1. Am I right?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you guys. I fixed it.
ASKER