VMware Communities
fourthaki
Contributor
Contributor

Packet from VM is redirected by host machine

Environment
Host IP:192.168.100.53/16 GW192.168.0.254  OS:Windows Server2012R2
GuesVM IP:192.168.100.48/16 GW192.168.0.254  OS:CentOS7, network=Bridge

Worksation Version Pro 14 Virtual network editer

vmnet0 status:blank (Bridge)

vmnet1 status:connected (host only adapter)

vmnet8 status:connected (NAT)

Issue
My VM can get correct IP address by DHCP and connect host machine and external network.
But VM is not directly communicate external device
It looks like host machine is routing, and host redirect packet to default gateway
I think host machine should be only bridging , not routing.
this issue is not seen on communication between VM and Host Machine
Also when I use virtualbox i didn't have this problem.

Question

Is it correct vmnet0(bridge) status is blank
Please let me know the cause(by design or depend on configuration)
if this is not by design , how can I fixed this?

# ping 192.168.100.53
PING 92.168.100.53 (192.168.100.53) 56(84) bytes of data.
64 bytes from 192.168.100.53: icmp_seq=1 ttl=128 time=0.241 ms
64 bytes from 192.168.100.53: icmp_seq=2 ttl=128 time=0.245 ms
64 bytes from 192.168.100.53: icmp_seq=3 ttl=128 time=0.216 ms

# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.100.53 icmp_seq=1 Redirect NetworkFrom 192.168.100.53: icmp_seq=1 Redirect Network(New nexthop: 192.168.0.254)
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=9.73 ms
From 192.168.100.53 icmp_seq=2 Redirect NetworkFrom 192.168.100.53: icmp_seq=2 Redirect Network(New nexthop: 192.168.0.254)
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=8.39 ms
From 192.168.100.53 icmp_seq=3 Redirect NetworkFrom 192.168.100.53: icmp_seq=3 Redirect Network(New nexthop: 192.168.0.254)
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=8.40 ms

Reply
0 Kudos
1 Reply
pwilk
Hot Shot
Hot Shot

Can you post the screenshot of your virtual switch configuration in Windows control panel and network configuration in Workstation's settings?

This seems like a wrongly configured bridge interface or some other minor error in configuration. It would be easiest to identify what's the issue with above mentioned screenshots at hand.

Cheers, Paul Wilk
Reply
0 Kudos