Good deal :)
On 2/16/06, Chris Green <[EMAIL PROTECTED]> wrote:
> It worked... not only did it work, but I discovered that it automatically
> converted the auto-created/implied rule to an actual rule. Very nice. :)
>
> Chris green
>
>
>
> On 2/16/06, Scott Ullrich <[EMAIL PROTECTED]> wrote:
> >
It worked... not only did it work, but I discovered that it automatically converted the auto-created/implied rule to an actual rule. Very nice. :)Chris greenOn 2/16/06,
Scott Ullrich <[EMAIL PROTECTED]> wrote:
It should work okay if you carefully review the settings beforeflipping the switch.And
It should work okay if you carefully review the settings before
flipping the switch.
And I do mean carefully ;)
On 2/16/06, Chris Green <[EMAIL PROTECTED]> wrote:
> Ok. So this only works with advanced NAT on. Since I am remote, I assume I
> can pre-enter a default NAT rule at the end, apply/sa
Ok. So this only works with advanced NAT on. Since I am remote, I assume I can pre-enter a default NAT rule at the end, apply/save the changes, then enable advanced NAT? Will this work without losing connectivity, or would I need to be on-site for this?
Chris GreenOn 2/16/06, Bill Marquette <[EM
On 2/16/06, Chris Green <[EMAIL PROTECTED]> wrote:
> I am running PFSense 1.0b1. I am having an issue with outbound NAT Mapping
> not working properly and am looking for some assistance.
>
> The firewall has an outside IP address of x.x.x.66. It has an additional IP
> address of x.x.x.67 set as a
I am running PFSense 1.0b1. I am having an issue with outbound NAT Mapping not working properly and am looking for some assistance.The firewall has an outside IP address of x.x.x.66. It has an additional IP address of
x.x.x.67 set as a virtual which is working perfectly with NAT rules to allow i
