Nethserver-ddclient with multiple red

saitobenkei · May 12, 2022, 9:41am

Ciao

From what I have seen, the nethserver-ddclient module works on the first available red.
Is it possible to force it to be associated with another red, thus have different ddns domains associated with the various reds, and possibly have it follow the operation of the reds backup module, in case one of the lines goes down, the ddns associated with that red is updated on the ip of another red?

Thank you!

robb · May 13, 2022, 8:41am

Looks like ddclient can handle multi WAN. To get it working on Nethserver, I think you will need a custom template. I am curious if you can get it working.

saitobenkei · May 13, 2022, 9:37am

Thank you, as soon as my provider restores the main line ( ) I’ll work on it a bit

pike · May 13, 2022, 10:37am

Tailgating for updates…

saitobenkei · May 13, 2022, 12:19pm

I took a look at that link but from what I understand, it’s for having multiple ddns on the same ip.
I searched a bit but couldn’t find any parameters for ddclient to indicate which interface to use.
There’s a command that says yes which interface to use, but it’s only for deriving the IP address to send to the ddns service.

Andy_Wismer · May 13, 2022, 12:27pm

Hi @saitobenkei

On OPNsense (Using ddclient):

You can even use different methods for each Interface / Connection…

It should also work in NethServer, but there without GUI…

My 2 cents
Andy

saitobenkei · May 20, 2022, 10:10am

Okay, here is something to start with:

github.com/opnsense/plugins

os-ddclient: unable to use webservice to check IP of various interfaces

opened 11:11PM - 25 Feb 22 UTC

closed 04:39PM - 13 Mar 22 UTC

toxic0berliner

**Important notices** Before you add a new report, we ask you kindly to acknowl…edge the following: - [X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md - [X] I have searched the existing issues, open and closed, and I'm convinced that mine is new. - [X] The title contains the plugin to which this issue belongs **Describe the bug** my dns record is being updated with the local ip of my interfaces instead of the public IP as I have 2 "public" interfaces that have 2 different public IPs but are both behind a routher that does NAT **To Reproduce** 1. setup a VPN interface to some cheapo VPN providing you some shared IP 2. use the old os-dyndns plugin to monitor that VPN interface for yourhost.example.com 3. you'll see a public IP beeing assigned to yourhost.example.com 4. now setup os-ddclient to monitor that same interface 5. you'll see the crappy privateIP assigned to you by the VPN provider beeing assigned to yourhost.example.com 6. If you're so lucky to have a VPN provider that enable you to do port-forwarding you'll see that yourhost.example.com:1234 will work at step 3 using the dyndns plugin but not at step 5 using ddclient... **Expected behavior** monitoring an interface when the "Check ip method" setting in the "General settings" page is set to anything that is a public webservice should result in a config file using the workaround `use=cmd, cmd="<something intelligent>"` or something better but not fallback to using `use=if` **Screenshots** Not applicable **Relevant log files** Not applicable **Additional context** To understand the context, I have 1 public fibre connection and 2 VPNs, all of which are on dedicated interfaces on the opnsense box, but NAT is happening between my opnSense box and the real internet public network somewhere at my ISP or at my VPN providers. All of these do provide me with a single IP address and all ports forwarded properly, but the real public IP of each of these interface is not visible by opnSense and suceptible to change. The previous os-dyndns plugin allowed me to select the interface I wanted **and** use any online service like checkmyip or similar to find out what is the real public IP of the interface. Now, it is a limitation of ddclient, if the configfile says `use=web, web=http://...` you cannot specify which interface is going to be used to send out the http request... If you want to specify the interface as is now possible thanks to nice people solving the issue #2784 if will always have `use=if` which will return the IP of the interface which in my case is not a public IP address and not useful at all :( The only way around this I see is to have `use=cmd, cmd="<something intelligent>"` and craft something intelligent to be able to perform an http request over a specific interface and parse the result. I am not good enough to actually create that cmd to send the http request over a specific interface and parse it, nor to actually update the plugin ui to allow setting it up, so thanks in advance for any help you would kindly provide ! **Environment** OPNsense 22.1.1_3-amd64 os-ddclient (installed) | 1.1

It would then suffice to dynamically modify the configuration file by replacing the interfaces with the active ones and re-executing the ddclient each time the lsm comes into action.

If the reds are more than 2 it gets a little bit more complicated because you would have to predict an assignment priority for each entry…