Rare project developers

[Frédéric LOUI <>]

> well, better off using the assigned mac address of the vm in the 
> rtr-hw.txt? :)
What I had to request, as there was an existing consistent policy in place 
(sysadmin rules :) )
I was told that the interface given by NSX belongs to a VLAN managed by 
VSphere.
And giving promiscuous mode to freeRtr VM would be also applied all existing 
hosts in the entire VLAN. )

For me the solution was to requets the creation of an additional VLAN (with 
PROMISCUOUS mode enable on Vsphere) add a new interface to freeRtr VM in that 
VM.

With newer NSX-T. I’m banging my head as there is seemingly no simple way to 
enable PROMISCUOUS mode with NSX-T tagging.

However, you might not have this issue with OpenStack. (It was just FYI)

> Le 30 mars 2022 à 14:00, mc36 <> a écrit :
> 
> hi,
> 
> On 3/30/22 13:57, Edgard da Cunha Pontes wrote:
>> *2) With our VMWare cluster we also had the issue when NSX gave an 
>> interface to our VM that was not in promiscuous mode.*
>> Another pending. I haven't put the interface in promiscuous mode yet.
> 
> well, better off using the assigned mac address of the vm in the 
> rtr-hw.txt? :)
> (if it was really a 100% copy of everything then you're having a mac 
> collision right now....)
> 
> regards,
> cs