This was fixed last night. Please try a newer snapshot.
_____
From: Fuchs, Martin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 15, 2007 9:39 AM
To: [email protected]
Subject: [pfSense Support] pfSense NAT and DynDNS after
IP-change
Hi, All !
I have noticed some stange things after upgrading from the
30-4-snapshot:
I'm using PPPoE and I did a fresh install to eleminate an
upgrade glitch.
After disconnecting and getting a new IP (only then, NOT if IP
stays the same), I'm unable to connect thru NAT from WAN to my services
on the LAN side of pfSense. The WAN IP is not updated by the DynDNS
client, too.
I checked the logs and everything and it seems to me that the
dyndns-client is not updating it's new ip and that the NAT rules do not
use the new WAN IP.
so I tried the following after manually disconnecting and
reconnecting:
When hitting "STATUS -> Filter reload" it does not seem to help
anyhow, but if I change some rule and hit "apply" then suddenly NAT from
WAN is activated again... only the IP is not updated at dyndns.org.
Hitting the "apply" button on the dyndns.org service it's
updated and everything works as expected...
Now everything works as expected again...
So can it be that some scripts do not run correctly ?
If I remember correctly it worked with snap 30-4...
On my system at work with a static IP there are no problems at
all, so I believe it has something to do with PPPoE or with dynamic IP
scripts ?
Regards,
Martin
