If you want to block by site, better use OpenDNS to block at DNS level.
-Raylund From: Sean Cavanaugh [mailto:[EMAIL PROTECTED] Sent: Thursday, January 31, 2008 12:01 PM To: [email protected] Subject: RE: [pfSense Support] Pfsense public intenet w/ authentication security wise, remember that more and more programs are using HTTP tunneling to get out thru firewalls. this type of traffic cannot really be stopped that well without layer 4+ firewalls that look at packet content. you will however block most of the joe blow users that will try stuff. also adding in blocks to specific sites will help cut down on nefarious activities. -Sean _____ > Date: Thu, 31 Jan 2008 10:40:23 -0600 > From: [EMAIL PROTECTED] > To: [email protected] > Subject: [pfSense Support] Pfsense public intenet w/ authentication > > I have a small computer shop and would like to setup free / open access > point so that clients can use it while in the shop. But I don't want it > so open that my neighbors are using it for nefarious purposes. Can > somebody recommend a configuration. > > My thoughts: > Add another nic and a wireless router or access point w/ captive portal > Add a wireless nic Ad-Hod w/ captive portal > Setup up some sort of VLan w/ Access point > > Any recommendation on the route I should go? Another route? > > And a lazy questions (I've not really looked into it) - what is best / > easiest way to lock this connection down to HTTP only. And will failure > to log into the captive portal block all traffic or just prevent browsing? > > Thanks, > -Dane > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _____ Connect and share in new ways with Windows Live. Get it now! <http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008 >
