I enabled promiscuous mode on a VM NIC to use containers in Solaris and Linux, I’m noticing with this enabled the router VMWare creates has a duplicate IPV6 address of a VM I created. When I invoke the DHCP client on the Linux VM DAD (duplicate address detection) finds a duplicate IPV6 address and network configuration fails. Does anyone know why there is a duplicate MAC address and the solution to this?
I’m suspecting its something specific to MacOS.
I’m creating two VMs on the same network segment (bridgeX and vmnetX). VM containers use multiple MAC addresses on the same NIC, therefore for one of the solutions to this it’s a requirement to enable promiscuous mode for a NIC in the VM server and VM OS, so other VMs can see the VM container’s MAC addresses. Yes, I know it’s a performance hit. I’m running VMWare Fusion on MacOS Ventura, a network in private host only mode and a DHCP server running in a VM OS container using a VNIC with virtual MAC. VMWare has (in network settings) the DHCP server disabled and IPV6 enabled. I did notice, this issue isn’t present in IPV4. My Linux VM correctly gets an IP address using dhcplient -4 and arp-scan shows no duplicate MACs.
I thought of a couple solutions and curious if there are more.
- Disable promiscuous mode for NIC, in VM server create new NIC for each container to use. This would require one to create some pool of NICs when playing with containers.
- Create a bridged network, use an external IPV6 router.
