Do the filter rules for these forwardings show up in the filter
section? If not, something screwed up somewhere.
--Bill
On 7/21/05, Kim C. Callis <[EMAIL PROTECTED]> wrote:
> I have added to NAT:Port Forwarding
> WAN - LAN port 22 192.168.150.1
> WAN - LAN port 443 192.168.150.1
> WAN - LAN port
On 7/21/05, Kim C. Callis <[EMAIL PROTECTED]> wrote:
> I have added to NAT:Port Forwarding
> WAN - LAN port 22 192.168.150.1
> WAN - LAN port 443 192.168.150.1
> WAN - LAN port 53 192.168.150.1
>
Unless I'm missing something, this should work the same way as
m0n0wall, put in rules on the WAN inte
I have added to NAT:Port Forwarding
WAN - LAN port 22 192.168.150.1
WAN - LAN port 443 192.168.150.1
WAN - LAN port 53 192.168.150.1
I am unable to ping my router, nor does any of the other services come
up... I checked off the box to auto-add rules to permit traffic and
still nothing...
On 7/21/
You should just go to the NAT section and add them there and pfSense
will create the actual rule for you. I think there is a check box on
the NAT setup screen to tell pfSense to create the rule.
Kim C. Callis wrote:
I went into rules to add access to SSH and HTTPS, and added entries on
the WA
More info please. What rules did you add? Both NAT and filter please.
--Bill
On 7/21/05, Kim C. Callis <[EMAIL PROTECTED]> wrote:
> I went into rules to add access to SSH and HTTPS, and added entries on
> the WAN interface. Is there something else that I need to add, because
> I am still not ab
I went into rules to add access to SSH and HTTPS, and added entries on
the WAN interface. Is there something else that I need to add, because
I am still not able to access the broswer or ssh into the server
remotely... What am I doing wrong?
--
When It Absolutely, Positively has to be Destroyed