Heres an interesting update to this. I was testing on a machine at home before I configure ddclient at my the location I want it to run. I wondered about if it would renew the IP address mapping when a new WAN ip was configured;
When you configure ddclient it always seems to setup a config file like so: pid=/var/run/ddclient.pid protocol=dyndns2 use=if, if=eth0 server=members.dyndns.org login=<username> password='<password>' <myhostname>.dyndns.org It wasnt updating the WAN ip when I power cycled the router. I wasnt sure if it would or not. Anyway a quick google yielded the following change pid=/var/run/ddclient.pid protocol=dyndns2 use=web, web=checkip.dyndns.org, web-skip='Current IP Address: ' server=members.dyndns.org login=<username> password='<password>' <myhostname>.dyndns.org Then when ddclient re-checks, it shows the following, when you check for the process, its configured to run as a daemon. $ ps -ef | grep ddclient root 1717 1 0 09:46 pts/1 00:00:00 ddclient - connecting to checkip.dyndns.org port 80 $ ps -ef | grep ddclientroot 1717 1 0 09:46 pts/1 00:00:00 ddclient - reading from members.dyndns.org port 80 $ ps -ef | grep ddclientroot 1717 1 0 09:46 pts/1 00:00:00 ddclient - sleeping for 300 seconds My /var/log/daemon.log shows Mar 29 09:51:07 Bart ddclient[1717]: SUCCESS: updating <myhostname>. dyndns.org: good: IP address set to 1.2.3.4 What settings do you folks use in your /etc/ddclient.conf files? Do you run the client as a daemon? On 25 March 2011 12:55, Alan Pope <[email protected]> wrote: > On 25 March 2011 12:47, Byte Soup <[email protected]> wrote: > > It seems if you add a new ssh key into seahorse it always generates a > file > > called "id_rsa.pub" and "id_rsa", renaming old ones to .1 etc, is that > > correct? > > No idea. I don't use Seahorse. > > > When you generate your keys is it always done as the user you are logged > in > > as? For example my user name on my machine might be "curtis" but I may > want > > to create a username login on my friends machine as "support" is that > > possible and still able to generate a key? > > > > I generate my key as me, my user ID, they are stored in .ssh in my > home directory. > > If I want to logon to a remote machine which has a different user ID > then I put my public key in that users folder on the remote machine. > E.g. in /home/support/.ssh/authorized_keys - on the _remote_ machine. > > I can then do:- > > ssh [email protected] > > or > > vncviewer -via [email protected] localhost > > Cheers, > Al. > > -- > [email protected] > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > https://wiki.ubuntu.com/UKTeam/ >
-- [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
