On 10/21/05, Brian <[EMAIL PROTECTED]> wrote:
> Would the port forwarding issue also affect PPTP connections? That is
> what I am trying to do.
unknown, try it and let us know ;)
--Bill
-
To unsubscribe, e-mail: [EMAIL PROTECTE
On Fri, 21 Oct 2005 11:29:48 -0400
Scott Ullrich <[EMAIL PROTECTED]> wrote:
>
> Yes, it is supposed to update. Please modify config.xml and add a
> tag to the area. Then run rm
> /tmp/config.cache and reboot the firewall. At this point you will be
> using the old dynamic dns updater code.
>
Would the port forwarding issue also affect PPTP connections? That is
what I am trying to do.
Ben Browning wrote:
I thought this too at first, until I found out my dyndns was really
working ok and the issue was with NAT and port forwarding. There is a
bug in 0.88 that breaks any port forwards
Please test: http://www.pfsense.com/~sullrich/pfSense-Full-Update-0.88.4.tgz
On 10/21/05, Ben Browning <[EMAIL PROTECTED]> wrote:
> I thought this too at first, until I found out my dyndns was really
> working ok and the issue was with NAT and port forwarding. There is a
> bug in 0.88 that breaks
I thought this too at first, until I found out my dyndns was really
working ok and the issue was with NAT and port forwarding. There is a
bug in 0.88 that breaks any port forwards that forward to a different
internal port than the one specified in the external port. This issue
was fixed in CVS, but
On 10/21/05, Brian <[EMAIL PROTECTED]> wrote:
> Can anyone confirm there are issues with dyndns updates in 0.88? I did
> a remote update to my pfSense today and I am no longer able to get in to
> it via the dyndns address.
>
> I also noticed that when running 0.86.4 recently when I disabled and
>
Can anyone confirm there are issues with dyndns updates in 0.88? I did
a remote update to my pfSense today and I am no longer able to get in to
it via the dyndns address.
I also noticed that when running 0.86.4 recently when I disabled and
re-enabled dyndns, the client would still not update
