hello here is the file /etc/config/ddns: the update was done from the web interface (the previous version was the beta 2). DynDNS on fonera had never been configured and I loaded settings from backup.
################################################################# # In order to enable dynamic dns you need at least one section, # and in that seciton the "enabled" option must be set to one # # Each section represents an update to a different service # # You specify your domain name, your username and your password # with the optins "domain", "username" and "password" respectively # # Next you need to specify the name of the service you are # connecting to "eg. dyndns.org". The format of the update # urls for several different dynamic dns services is specified # in the /usr/lib/ddns/services file. This list is hardly complete # as there are many, many different dynamic dns services. If your # service is on the list you can merely specify it with the # "service_name" option. Otherwise you will need to determine # the format of the url to update with. You can either add an # entry to the /usr/lib/ddns/services file or specify this with # the "update_url" option. # # We also need to specify the source of the ip address to associate with # your domain. The "ip_source" option can be "network", "interface" # or "web", with "network" as the default. # # If "ip_source" is "network" you specify a network section in your # /etc/network config file (e.g. "wan", which is the default) with # the "ip_network" option. If you specify "wan", you will update # with whatever the ip for your wan is. # # If "ip_source" is "interface" you specify a hardware interface # (e.g. "eth1") and whatever the current ip of this interface is # will be associated with the domain when an update is performed. # # If "ip_source" is "script" you specify a script to obtain ip address. # The "ip_script" option should contain path to your script. # # The last possibility is that "ip_source" is "web", which means # that in order to obtain our ip address we will connect to a # website, and the first valid ip address listed on that page # will be assumed to be ours. If you are behind another firewall # this is the best option since none of the local networks or # interfaces will have the external ip. The website to connect # to is specified by the "ip_url" option. You may specify multiple # urls in the option, separated by whitespace. # # Finally we need to specify how often to check whether we need # to check whether the ip address has changed (and if so update # it) and how often we need to force an update ( many services # will expire your domain if you don't connect and do an update # every so often). Use the "check_interval" to specify how # often to check whether an update is necessary, the "retry_interval" # to specify how often to retry in case the update has failed, and # the "force_interval" option to specify how often to force an # update. Specify the units for these values with the "check_unit", # the "retry_init" and the "force_unit" options. Units can be # "days", "hours", "minutes" or "seconds". The default force_unit # is hours, the default retry_unit is seconds and the default # check_unit is seconds. The default check_interval is 600 seconds, # or ten minutes. The default retry_interval is 60 seconds, or one # minute. The default force_interval is 72 hours or 3 days. # # ######################################################### config service "myddns" option enabled "0" option interface "wan" option service_name "dyndns.org" option domain "mypersonaldomain.dyndns.org" option username "myusername" option password "mypassword" option ip_source "network" option ip_network "wan" option force_interval "72" option force_unit "hours" option check_interval "10" option check_unit "minutes" option retry_interval "60" option retry_unit "seconds" #option ip_source "interface" #option ip_interface "eth0.1" #option ip_source "script" #option ip_script "path to your scrip" #option ip_source "web" #option ip_url "http://www.whatismyip.com/automation/n09230945.asp"; #option update_url "http://[USERNAME]:[PASSWORD]@ members.dyndns.org/nic/update?hostname=[DOMAIN]&myip=[IP]" ******************************************************** for the second problem thanks for your interest, I look forward to hearing from you. greatings. 2012/8/23 Matthijs Kooijman <matth...@stdin.nl> > Hi Mariano, > > > I tried to apply the fix (Ticket #1181) > > http://trac.fonosfera.org/fon-ng/ticket/1181 via ssh (picture 1). I > > rebooted but no change, still does not work (picture 2). > Hmm, your screenshot shows no interface at all, which seems to be a > different problem. > > Could you copy-paste the contents of the /etc/config/ddns file on your > Fonera (but remove any passwords or other sensitive data that might be in > there)? > > Also, how did you upgrade to beta3? Did you do an upgrade through the > webinterface, or a clean install through SSH? Did you restore a settings > backup? Did you have ddns configured before the upgrade? > > > For the 2° problem: > I'll do some testing with my 2.0g here, just to check if wifi client > mode is not entirely broken on 2.0g. I'll reply separately later (might > be next week). > > Gr. > > Matthijs > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAlA2LFgACgkQz0nQ5oovr7yv0gCfaWYUgaeHh+LrYdfik3lXKX/E > GcYAn0K/urEjCxZuJV5EngRKmRoCV54r > =7HPW > -----END PGP SIGNATURE----- > > _______________________________________________ > Development mailing list > Development@fonosfera.org > http://fonosfera.org/mailman/listinfo/development > > -- Saluti, Mariano Rispetta l'ambiente. Non stampare questa e-mail se non è necessario
<<foglia.gif>>
_______________________________________________ Development mailing list Development@fonosfera.org http://fonosfera.org/mailman/listinfo/development
