![]() You can check whether it is running by issuing: ps aux | grep noip2 Now when you reboot your server, the noip2 service should be running. To tell the system it needs to run the script after booting, I open up and edit rc.local sudo nano /etc/rc.localįind the line that contains exit “0” and on the line above add: /etc/init.d/noip startĪgain, Ctrl-x to exit nano and y to save. I need to make the script executable so I issue: sudo chmod 755 /etc/init.d/noip The Ctrl-x to exit nano and y to save the file. I add the following to the file (referenced in the README): #! /bin/shįor i in `noip2 -S 2>&1 | grep Process | awk '' | tr -d ','` To remedy this, I create a new file in init.d using the nano text editor: sudo nano /etc/init.d/noip However, if the power on the remote site goes down (and it often does, especially during storms) the server will reboot but there is nothing to tell it to restart the noip2 client. Note that you may need to open port 8245 (outbound) on your router if you have a restrictive outbounds ports setup. A command to execute when the update is successful (you can leave this blank)Īt this point, I have a working client that will update your public IP to No-IP.The interval (in minutes) that you wish to update your public IP address to No-IP.Your username (email address for No-IP account). ![]() The -C flag tells the installed client to create a new configuration where you enter: You’ll need the username and password you selected when you signed up for your No-IP DDNS user account. Now I install the client using: sudo make install The directory may differ if the noip2 client version number is updated. Then I extract the archive and cd to the resulting directory: tar -xvf Instead, I now use the NoIP2 client in the following fashion:įirst of all, working locally on the server (because that ADSL connection really is that bad!) I download the NoIP2 client: wget They offer a free basic DDNS account which meets my needs.Ĭlient wise, I have previously (some years ago) used ddclient to update the IP address to No-IP but have more recently struggled to get the configuration working reliably. The service I chose for this purpose is No-IP. In order to communicate with the server remotely, I need to know the current public IP (dynamically assigned) so I need to run a dynamic DNS client on the server to update a remote service. I recently updated the server from Ubuntu 13.10 to Ubuntu 14.04 Long Term Support which, as it is supported until 2019, should see out the antiquated hardware’s days The reliability of the connection is weak at best and the dynamically assigned IP address tends to change every time the connection drops which can be several times a day. The site is connected to the internet via a RADSL link on the end of 1.5km of very old copper cable. I look after a server which is connected to some temperature sensors on a remote site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |