How can I get ddclient to always be on?
I run Linux Mint 13 Cinnamon on my computer. I installed and set up ddclient, with the purpose of my computer telling OpenDNS my IP address whenever it changes. What can I do so that ddclient will always be on? I don't want to have to bother with typing some code in the terminal everything I power on my computer or whenever I switch from one WiFi network to another.
-
Sorry to see that you blocked the search engines. :(
This is widely documented on the internet: https://startpage.com/do/search?q=ddclient+daemon
-
rotblitz,
I did some browsing, even with that link you provided, but am somewhat overwhelmed by all the information. I don't know what to apply.
In Windows, if we want a program to start whenever we power on the computer, we put the shortcut/link in the StartUp folder.
What is the equivalent of that?
If I switch wifi networks, does ddclient need to be run again? How can I do this automatically?
But my questions are all summed up in one question: What must/can I do now so that I never have to worry about ddclient again?
-
"somewhat overwhelmed by all the information"
This is somehow normal nowadays, with nearly everything...
"If I switch wifi networks, does ddclient need to be run again? How can I do this automatically?"
Are you talking about other WLANs? OpenDNS Home, as its name says, is for networks you own, not for your devices in other networks. That said, you don't run an Updater on a roaming device at all.
"What must/can I do now so that I never have to worry about ddclient again? "
Not a Linux expert either. I'll leave that with someone else.
-
"In our house, for instance, we have two wifi networks"
Ah, I see now what you mean. But these two WLANs use the same internet connection (public IP address), right? So if some Updater like ddclient is running, the WLAN in use should be irrelevant. It is your public IP address informatino which needs to keep updated at OpenDNS.
"each with their own SSID, password, IP address."
SSID and passphrase are irrelevant for TCP/IP matters. It doesn't matter if TCP/IP goes over cupper cable or radio waves. And the different IP address is certainly a private one, without relevance for the internet.
-
Ah, this is new information. Hoping to see now what's going on.
You'll have to maintain two accounts then, or open a support ticket to request being able to add another network in your current account. This is theoretically possible. Then you must run two update clients, one for each internet connection.
Please sign in to leave a comment.
Comments
12 comments