Hello Heinrich,
as another hack you can setup virtual switches (separate ones for any given
link between two VMs )
eg vm1--vswitch2---vm2---vswitch3--vm4
so if you have promiscuous enabled and you only have two vms attached to
the vswitch is not so bad...
but if you have 100x vms on a port with
Hello Tom,
Thank you very much for your in-depth explanations.
Actually enabling mac changes and forged transmits did the trick. A HUGE trick:
While A was pinging R, I tried to look at the icmp requests and replies on B’s
vmx1 interface. But they did not show. Neither bridge0 or vmx0 showed
Hello Heinrich,
it is not OpenBSD it is a Vmware issue ...
virtualnets / vswitches in ESXI are not proper switches... they forward
packets based on static mac- virtual port entries. (they do not do proper
mac learning)
you can set the vwswitch in the networking configuration section ... there
Some things I forgot:
All interfaces are UP
pf(4) ist disabled
bridge0 sees a bunch of lladdrs on em0 and one on em1, which is that of “A”
-Heinrich
> On 29. Nov 2020, at 22:29, Heinrich Rebehn wrote:
>
> Hi all,
>
> I am trying to setup an OpenBSD 6.7 virtual machine under VMware ESXi 6.7
Unfortunately, switching to vmx(4) did *not* do the trick
-Heinrich
> On 29. Nov 2020, at 22:38, Heinrich Rebehn wrote:
>
> Some things I forgot:
>
> All interfaces are UP
> pf(4) ist disabled
> bridge0 sees a bunch of lladdrs on em0 and one on em1, which is that of “A”
>
> -Heinrich
>
>
5 matches
Mail list logo