On Fri, Jan 21, 2011 at 1:20 PM, Dimitri Rodis
wrote:
> pfSense 2.0-BETA5 (i386) built on Wed Jan 19 12:45:14 EST 2011
>
> I created a NAT rule with a linked firewall rule using a port alias that I
> called OWA_PORTS. After creating the rule I decided to rename the port alias
> to PORTS_WEBSERVE
On Sun, Feb 6, 2011 at 2:19 PM, Michel Servaes wrote:
> Hi,
>
> Have posted it on the forum too, I think that the 512MB images have no use
> anymore.
> Yesterday I tried to update to the latest snapshot, but it told me that the
> file was corrupted.
>
> When checking into SSH, I saw that only 43MB
The simplest way to do this (for the users anyway) is to run a webserver inside
the clients network and serve out a web based proxy (e.g. phpMyProxy),
authenticate users at the PHP proxy (using htpasswd or any other apache auth
module).
This would allow the users to browse to a web site which w
We have experimented with a kind of "reverse captive portal" where
logging in to another web site (temporarily) adds your IP to the list
in pfSense. Maybe you could try something like that.
Moshe
On Tuesday, February 8, 2011, Chuck Mariotti wrote:
>
> I’m not sure how best to describe this situ
I'm not sure how best to describe this situation without it getting word.
We have a number of servers behind a pfSense firewall at a datacenter. One of
the servers is a web site that needs to be accessible only by computers on our
client's network (also behind pfSense elsewhere)... This solution
