mdns-repeater needs additional restart after reboot

[tscomm]

Hi

I connected two sites with OpenVPN between two OPNsense FWs. All is working fine and I can also use all services based on mdns across both sites. But when I reboot one of the FWs I need to manually restart the mdns-repeater on that FW again for it to work. Could this be a problem with the boot-sequence or that maybe the OpenVPN interface does not come up early enough for the mdns-repeater to recognize and use it?

Many thanks,
Thomas

[franco]

So you have assigned OpenVPN interfaces selected in mdns-repeater?

It's a bit of an issue for sure if these are not ready when the service is started at boot.


Cheers,
Franco

[tscomm]

Yes, the OpenVPN interface is configured/selected as a listen interface. I checked if I can restart mdns-repeater with cron or if I have a "hook" to execute actions when the tunnel comes up. But both don't seem to be possible.

[franco]

Ok, I'm a bit shy of ideas. Here's the readme:

https://github.com/geekman/mdns-repeater

"mdns-repeater only requires the interface names and it will do the rest."

Ok, that doesn't really help now does it... To me it's a unclear what event leads to mdns-repeater to start and behave incorrectly which means we don't know which event we're looking for. Cron restart we could do, although it's not very elegant.

Just throwing ideas around for now.


Cheers,
Franco

[tscomm]

Agree, cron is far from elegant... According to https://manpages.ubuntu.com/manpages/noble/en/man8/openvpn.8.html#scripting%20integration OpenVPN would have script hooks but I'm aware that this looks quite complex to implement in OPNsense. Also it would then be just a solution for OpenVPN and not for other kinds of interface changes on the system.