Answer the question
In order to leave comments, you need to log in
VmWare Workstation 9: does one mac address resolve for different interfaces?
Good night, Habr!
I encountered such a situation with a VM on VmWare Workstation 9.
Networks are configured as follows:
The problem VM uses vmnet1, which, as you can see from the screen, is tied to eth1 of the host machine. The host machine is GNU/Debian Linux.
This is how the first interface looks in the VM settings:
This interface in the VM itself is visible as eth0 c mac 00:0c:29:b4:0d:f2
And this is how the second interface is configured:
Inside the VM it is eth1 c mac 00:0c:29:b4: 0d:fc.
Clearing the ARP table on the host we are pinging
This is what happens when we try to ping first one, then the other.
Ping to eth0 (101.1.1.22) fails because
101.1.1.22 00:0c:29:b4:0d:fc appears in arp
00:0c:29:b4:0d:fc is mac eth1 Ping to eth1 (101.1.1.23) passes, because the orthodox entry
101.1.1.23
appears in arp 00:0c:29:b4:0d:fc
Here is the screen :
Question: where to dig further?
UPD0: changing mac-addresses does not help. Everything is the same, only mac is different.
UPD1: deleting and creating a new network adapter doesn't help either.
UPD2:
Conducted such a test.
Now I tried to add one more network card for the internal network.
Was eth3 192.168.8.8 00:0c:29:b4
:
0d
:
10 and eth4 are connected to the same vmnet8 network (host-only network)
Ping from a machine in the
same vmnet8 goes to both ip, but in arp such a “beauty”
:
0d:10[ether] on eth0
That is the same problem as with external cards.
UPD3: same problem on VirtualBox
UPD4: same problem on physical machine too.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question