Messages

1

24.1 Legacy Series / Re: mdns-repeater needs additional restart after reboot

« on: May 14, 2024, 03:08:57 pm »

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.

2

24.1 Legacy Series / Re: mdns-repeater needs additional restart after reboot

« on: May 14, 2024, 01:32:50 pm »

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.

3

24.1 Legacy Series / mdns-repeater needs additional restart after reboot

« on: May 13, 2024, 02:47:31 pm »

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

4

22.1 Legacy Series / Re: os-ddclient

« on: February 24, 2022, 04:34:02 pm »

Great, many thanks! I Changed the files and could configure it. I saw it do (log) the right thing once in the log on the FW. Trying to trigger another update by changing the record in public DNS. Rebooting the FW did not trigger another update. But I assume it generally works.

I just created a pull request for DNS Made Easy, but I'm not able to test, because I do not use the service.

https://github.com/opnsense/plugins/pull/2859

If you want to test before the new version will be released, please adjust the two files.

5

22.1 Legacy Series / Re: os-ddclient

« on: February 22, 2022, 10:45:14 pm »

Reading through most of the discussion I did not spot someone raising/answering my point so I would like to bring it up. In my setup with dnsmadeeasy I had to do the entire update and authentication via the update URL field. I found no easy way to recreate this with ddclient. Looking at the project rules on github also makes me wonder if they would accept this enhancement request since dnsmadeeasy is a commercial provider... Am I out of luck having this implemented on OPNsense in 6 months?