There was already some discussion of this here: http://forum.pfsense.org/index.php/topic,8531.0.html

Either you cache has stale data or your system is not fully in sync with the changes, otherwise i cannot see how this is happening in your system since i cannot replicate in 3 systems here. Debugging info: to verify this check that the $tabscount is getting incremented in the loop after the form is declared since you seem to have to interfaces that should be shown there.

Can you please send me the config.xml part where your wireless parameters are saved so i can take a look at it. It happens only with certain parameters i cannot replicate.

confirmed fixed. thanks.

the latest build fixed this.

Hi I too run the latest: Mon Sep  8 18:22:10 EDT 2008 1.3-ALPHA-ALPHA built on Mon Sep 8 17:54:11 EDT 2008 FreeBSD 7.0-RELEASE-p4 and don't see the issues(yet :P). Keep update till you don't see any strange. That's what 1.3-AA is.  ;D ;D ;D

Read the systemlog. The dyndns client writes its output there. I think right now it's when your IP changes or after 28 days or something like that.

My partition are not wrong …. coze in bot version 1.2 and 1.3 ALPHA are working installed on hardisk... maybe u know how to installed on bsd command. regards, kambeeng

Thank you guys for detail. I will hold my tongue for now ;D ;D ;D

You can do this using network aliases in 1.2 already, but it'll never update the ruleset to reflect any DNS changes (unless you make a firewall rule change). For records that change frequently this isn't practical.

You can restore the configuration on a similar configuration (amount of nics, they may be different brands) and restore the xml config. This is the strongest point of pfSense, you can save and restore your configuration on any computer fit to run pfSense.

The console option is only there for the intial setup so the webui can be accessed. It is not ment for complete configuration.

Remove the red from the resulting config and please search before complaining. It will be fixed later on… when i get to it.

@Shraik: my openVPN server with PKI dont worked after this upgrade. OpenVPN in 1.3 is a moving target at the moment, doesn't surprise me. I don't think the config upgrade code is in place yet.