0000979: DynDNS: need to be defined per uplink

Please see now our new Bugtracker system: JIRA

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000979

Endian Firewall

Other Services

public

2008-06-19 18:01

2011-11-07 13:17

Reporter

aender

Assigned To

peter-endian

Priority

normal

Severity

major

Reproducibility

always

Status

confirmed

Resolution

open

Platform

OS Version

Product Version

2.2-rc1

Target Version

future

Fixed in Version

Summary

0000979: DynDNS: need to be defined per uplink

Description

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/setddns.pl

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/setddns.pl
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.

Tags

No tags attached.

Attached Files

Relationships

parent of	0001062	assigned	max-endian	DynDNS: need to be defined per uplink (make GUI changes)
parent of	0001063	confirmed	peter-endian	setddns.pl: need to advertise the ip change on each uplink
has duplicate	0000748	confirmed	peter-endian	Dynamic DNS client should have an uplink selector
child of	0001937	confirmed	peter-endian	issues to fix with ddns
Not all the children of this issue are yet resolved or closed.

Notes
(0001429) jvodan (reporter) 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

(0002407) aender (reporter) 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.

(0002435) peter-endian (administrator) 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.

(0007529) aender (reporter) 2011-11-07 13:17	Any updates about this issue? Can we see this in 2.5?

Issue History
Date Modified	Username	Field	Change
2008-06-19 18:01	aender	New Issue
2008-06-23 22:34	peter-endian	Target Version	=> 2.2-rc2
2008-06-25 13:52	raphael-endian	Priority	normal => immediate
2008-07-01 17:52	peter-endian	Issue cloned: 0001062
2008-07-01 17:52	peter-endian	Relationship added	parent of 0001062
2008-07-01 17:55	peter-endian	Issue cloned: 0001063
2008-07-01 17:55	peter-endian	Relationship added	parent of 0001063
2008-07-01 17:55	peter-endian	Severity	feature => major
2008-07-10 03:39	jvodan	Note Added: 0001429
2008-07-10 18:51	peter-endian	Priority	immediate => normal
2008-07-23 11:20	peter-endian	Relationship added	has duplicate 0000748
2008-07-24 16:02	ra-endian	Target Version	2.2-rc2 => 2.2-rc3
2008-07-28 08:46	peter-endian	Target Version	2.2-rc3 => 2.2
2008-09-10 15:41	chris-endian	Target Version	2.2 => 2.3
2009-05-27 09:32	peter-endian	Target Version	2.3 => future
2009-05-27 10:57	aender	Note Added: 0002407
2009-05-29 09:55	peter-endian	Note Added: 0002435
2009-06-10 13:53	peter-endian	Relationship added	child of 0001937
2010-09-21 18:33	peter-endian	Status	new => confirmed
2011-02-02 11:22	lorenzo-endian	Customer Occurencies	=> 0
2011-02-02 11:22	lorenzo-endian	Assigned To	=> peter-endian
2011-11-07 13:17	aender	Note Added: 0007529