Hello there, first thank you for your work !
I am working on setting up a portable deployment kit, which would be a pre-installed rack controller already registered to the region controller through a mesh network (netbird), so that rack/region connectivity only requires an internet connection (no vpn required), and that kit can be shipped anywhere, and be able to cache and deploy our custom images.
So far we have successfully connected a rack controller, but we notice that the network interfaces of our rack are not registered or discovered. I saw similar problems reported caused by MAAS beaconing not being able to work because of multicast issues (not being able to join a group) which seems necessary for network and interfaces reporting.
In our case this is explained by multicast not being supported by netbird so the beaconing error makes total sense.
I tried disabling the option with cli: set-config name=network_discovery value=disabled, but i still see the error pop (see capture) and interfaces are not refreshed.
So my question is: Is there a way to make network discovery on the rack work without relying on multicast ?
Info on system: maas 3.7.2
Thanks for your time
Quentin
