SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0000979: DynDNS: need to be defined per uplink - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000979Endian FirewallOther Servicespublic2008-06-19 18:012011-11-07 13:17
0000979: DynDNS: need to be defined per uplink
DynDNS only works with the main uplink

If any other uplink goes up the dyndns doesn´t update his ip.

Please replace "main" with a variable for the Uplink in /usr/local/bin/

if (-f "${swroot}/uplinks/main/data") {
       my %conf_hash = ();
       readhash("${swroot}/uplinks/main/data", \%conf_hash);
       $ip = $conf_hash{'ip_address'};

This variable (Uplink) should be setup within the DynDNS Page. Defined per uplink.

And at least you should do a symlink at /etc/uplinksdaemon/addrchanged to /usr/local/bin/
With this symlink every time a uplink changes the DynDNS would be updated.

This is very important for doing OpenVPN with other uplinks than main in combination with DynDNS. For Example a fallback OpenVPN via UMTS.

No tags attached.
parent of 0001062assigned max-endian DynDNS: need to be defined per uplink (make GUI changes) 
parent of 0001063confirmed peter-endian need to advertise the ip change on each uplink 
has duplicate 0000748confirmed peter-endian Dynamic DNS client should have an uplink selector 
child of 0001937confirmed peter-endian issues to fix with ddns 
Not all the children of this issue are yet resolved or closed.
Issue History
2008-06-19 18:01aenderNew Issue
2008-06-23 22:34peter-endianTarget Version => 2.2-rc2
2008-06-25 13:52raphael-endianPrioritynormal => immediate
2008-07-01 17:52peter-endianIssue cloned: 0001062
2008-07-01 17:52peter-endianRelationship addedparent of 0001062
2008-07-01 17:55peter-endianIssue cloned: 0001063
2008-07-01 17:55peter-endianRelationship addedparent of 0001063
2008-07-01 17:55peter-endianSeverityfeature => major
2008-07-10 03:39jvodanNote Added: 0001429
2008-07-10 18:51peter-endianPriorityimmediate => normal
2008-07-23 11:20peter-endianRelationship addedhas duplicate 0000748
2008-07-24 16:02ra-endianTarget Version2.2-rc2 => 2.2-rc3
2008-07-28 08:46peter-endianTarget Version2.2-rc3 => 2.2
2008-09-10 15:41chris-endianTarget Version2.2 => 2.3
2009-05-27 09:32peter-endianTarget Version2.3 => future
2009-05-27 10:57aenderNote Added: 0002407
2009-05-29 09:55peter-endianNote Added: 0002435
2009-06-10 13:53peter-endianRelationship addedchild of 0001937
2010-09-21 18:33peter-endianStatusnew => confirmed
2011-02-02 11:22lorenzo-endianCustomer Occurencies => 0
2011-02-02 11:22lorenzo-endianAssigned To => peter-endian
2011-11-07 13:17aenderNote Added: 0007529

2008-07-10 03:39   
A hack to get ddns to follow the link so as to have vpn failover

 if (-f "${swroot}/uplinks/main/data") {
        my %conf_hash = ();
        readhash("${swroot}/uplinks/main/data", \%conf_hash);
        $ip = $conf_hash{'ip_address'};

    $ip = `/usr/local/bin/detectip`; #ADD This line
2009-05-27 10:57   
Please solve this with 2.3 and not in "future"

This post is nearly one year old!
This only need "some" changes to the gui.
2009-05-29 09:55   
it's not *that* easy. adding support for multiple uplinks needs correct uplinksdaemon integration which is not that easy right now, since dyndns currently is a mess.
we need to rewrite dyndns from scratch. that's nothing we should do in a 2.3 beta stage.
2011-11-07 13:17   
Any updates about this issue?

Can we see this in 2.5?