homelab connectivity issues b/w virtual and physical

[MJL]

I’m having problems getting virtual switches to communicate with a mgmt VM on a flat networks 192.168.56.0/24

Router – 56.253
ESXIhost – 56.100
Mgmt VM – 56.252
Macbook en0 (wifi) – 56.36
Virtual switch VM – 56.10 & 56.19 (management1 interface)
Current network Adapter settings
Adapter 1 – enable network adapter (ticked)
- Attached to: Bridged Adapter
- Name: en0: Wifi
- Advanced
Intel PRO/1000 MT Server
Allow VMs
Cabled Connect - ticked

My goal is to have the Mgmt VM (56.252) to reach 56.10 and 56.19

ml:MacOS $ ifconfig
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 98:01:a7:a1:21:91
inet6 fe80::9a01:a7ff:fea1:2191%en0 prefixlen 64 scopeid 0x4
inet 192.168.56.36 netmask 0xffffff00 broadcast 192.168.56.255
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00
inet 192.168.56.1 netmask 0xffffff00 broadcast 192.168.56.255


From terminal (56.36) - when virtual switch adapter 1 int is set to host-only int.
I can ping
192.168.56.252 - VM
192.168.56.253 – Gateway router
192.168.56.100 – ESXi host
Can’t ping
192.168.56.10 – virtual switch – management1 (vboxnet0)
192.168.56.19 – virtual switch – management1 (vboxnet0)


Test results from changing the Adapter1 interface on the virtual switches :

1. Bridged en0 – wifi – virtual switches could ping .36 (en0 wifi int on macbook) but not .100, .252 or .253
however, from x.y.56.10 I can ping x.y.56.19, so b/w the virtual switches over the management1 interface there is connectivity.
Also from either of the virtual switches I can ping my mac on 56.36.

2. Host-only vboxnet0 settings in virtualbox for adapter 1

ml:MacOS mlandy$ vboxmanage list hostonlyifs
Name: vboxnet0
GUID: 786f6276-656e-4074-8000-0a0027000000
DHCP: Disabled
IPAddress: 192.168.56.1
NetworkMask: 255.255.255.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:00
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-vboxnet0


ml:MacOS $ arp -a
? (10.95.0.213) at 2:50:41:0:1:1 on gpd0 ifscope permanent [ethernet]
? (172.16.19.131) at 0:c:29:49:80:f8 on vmnet8 ifscope [ethernet]
? (192.168.56.10) at (incomplete) on en0 ifscope [ethernet]
? (192.168.56.19) at (incomplete) on en0 ifscope [ethernet]
? (192.168.56.36) at 98:1:a7:a1:21:91 on en0 ifscope permanent [ethernet]
? (192.168.56.100) at b8:ae:ed:76:2f:c3 on en0 ifscope [ethernet]
? (192.168.56.252) at 0:c:29:f7:37:1e on en0 ifscope [ethernet]
? (192.168.56.253) at c0:25:6:91:40:34 on en0 ifscope [ethernet]
? (192.168.56.255) at (incomplete) on en0 ifscope [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]
ml:MacOS $

virtual switches can ping b/w eachother but NOT 56.36 or .100, .252 or .253

3. NAT – both virtual switches .10 and .19 can’t ping .36 or .100, .252. or .253

can sometime please help with creating a homelab on a single flat subnet ? where you've got a combination of virtual and physical device that need to communicate over this flat network.

[MJL]

Here is some more info re: homelab

192.168.56.0/24
----------------------
Intel NUC
56.252 (Mgmt VM, monitoring)
56.100 (ESXi Host)
|
|_______Wired_________ Router (56.253)
|
|---en0(Wifi), 56.36
Macbook
Virt switch_1 (ma1, 56.10)-------|--vboxnet0 (56.1)
Virt switch_2 (ma1, 56.19)