I have Pfsense2.0.1 installed with Dual WAN load balancing, but any
firewall rules i have created on LAN is not working for instance i have
created one rule for Block any services particularly for 192.168.1.4 IP
ActionBlock
Interface
sorry my mistake both are same 1923.168.10.14
On Mon, Mar 26, 2012 at 5:30 PM, Russell Howe rh...@moonfruit.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/03/12 12:54, Pankaj Kumar wrote:
i have created one rule for Block any services particularly for
192.168.1.4 IP
192.168.10.14
On Mon, Mar 26, 2012 at 5:32 PM, Pankaj Kumar pankajnh...@gmail.com wrote:
sorry my mistake both are same 192.168.10.14
On Mon, Mar 26, 2012 at 5:30 PM, Russell Howe rh...@moonfruit.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/03/12 12:54, Pankaj Kumar
I have Pfsense2.0.1 installed with Dual WAN load balancing, but any
firewall rules i have created on LAN is not working for instance i have
created one rule for Block any services particularly for 192.168.10.14 IP
ActionBlock
Interface
Hi Folks,
Giving a look around on PFSense lists, there is a lot of people who needs
NTLM support for
transparent AD authentication into PFSense's Captive portal feature.
Unofficially, it is possible already to find some people making tweaks and
workarounds to accomplish that,
but surely nothing
Are you using squid or any other Proxy ?
Am 26.03.2012 um 14:54 schrieb Pankaj Kumar
pankajnh...@gmail.commailto:pankajnh...@gmail.com:
I have Pfsense2.0.1 installed with Dual WAN load balancing, but any firewall
rules i have created on LAN is not working for instance i have created one rule
no no, i didn't installed any packages yet!
On Mon, Mar 26, 2012 at 6:40 PM, Fuchs, Martin
martin.fu...@trendchiller.com wrote:
Are you using squid or any other Proxy ?
Am 26.03.2012 um 14:54 schrieb Pankaj Kumar pankajnh...@gmail.com:
I have Pfsense2.0.1 installed with Dual WAN load
Hello,
I was using the squid-reverse package based on squid 2.x up till last
week when i seen it was upgraded and now using the 3.x version of
squid. After upgrading it appeared my QOS ACLs were not marking
traffic which matched any longer. This was confirmed by viewing the
logs and