Bug #68: Dyndns for second WAN( opt1) does not work - pfSense - pfSense bugtracker

Actions

Copy link

Bug #68

closed

Dyndns for second WAN( opt1) does not work

Added by GS FON over 14 years ago. Updated over 14 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Dynamic DNS

Target version:

2.0

Start date:

08/31/2009

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

There are two problems with the dyndns page.

1) When ever I make any changes (disable/enable, or aything at all) and click save, it takes an AWFUL long time. I don't know what is spinning in the background to cause it.

2) the ip address for my second WAN which is on opt1 is not detected.

dyndns for WAN is detected properly:

alix-pfsense:/# more /cf/conf/dyndns_wandyndns.cache
24.x.x.x:1251448583

dyndns if WAN2 is NOT detected properly:

alix-pfsense:/# more /cf/conf/dyndns_opt1dyndns.cache
:1251694941

Actions

Copy link

Updated by Scott Ullrich over 14 years ago

Status changed from New to Feedback

Please try commit r07a3b40 or a new snapshot and report back.

Actions

Copy link

Updated by GS FON over 14 years ago

I looked at the change revision and added the changes but it still did not work.

There was actually an error in the change which read:

$this->_dnsIP = get_interface_ip($this->_if);

I added a log_error debug log_error("!!! IP for interfance {$dnsIf} - {$this->_dnsIP}."); and found it did not produce the correct IP until I changed it back to

$this->_dnsIP = get_interface_ip($dnsIf);

The real error is when it goes into the update function, it seems like all the variables are lost. When I debug print out $this->_dnsIP, it would be blank. I think that's where the real problem is.

Thanks!

Actions

Copy link