Firewall Wizards mailing list archives
Re: Locking down public wireless access
From: David Lang <david.lang () digitalinsight com>
Date: Wed, 23 Feb 2005 21:21:08 -0800 (PST)
On Tue, 22 Feb 2005, Dale W. Carder wrote:
- Roll out a "captive portal" style network admission box. The captive portal also strongly encourages the use of VPN (and allows them to get the client before allowed through) when on the wireless network, but acts as a fallback mechanism for those without: the vpn client, clue, admin on their machines, or who are otherwise guests.There's several free captive portal thingys out there like NoCatAuth, PacketFence, and then the vendors like Perfigo (now vendor C), BlueSocket, and BSi. We found that they all had limitations one way or another, so choose your poison carefully!
Dale, any chance of getting you to list the limitations that you ran into to save the rest of us some research time? :-)
David Lang -- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare _______________________________________________ firewall-wizards mailing list firewall-wizards () honor icsalabs com http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
Current thread:
- Locking down public wireless access Chris Bills (Feb 22)
- Re: Locking down public wireless access ArkanoiD (Feb 22)
- Re: Locking down public wireless access Jim Seymour (Feb 22)
- Re: Locking down public wireless access Kevin Sheldrake (Feb 22)
- Re: Locking down public wireless access Paul D. Robertson (Feb 22)
- RE: Locking down public wireless access Mark Gumennik (Feb 22)
- RE: Locking down public wireless access John Adams (Feb 22)
- Re: Locking down public wireless access Dale W. Carder (Feb 23)
- Re: Locking down public wireless access David Lang (Feb 24)
- <Possible follow-ups>
- RE: Locking down public wireless access Smith, Aaron (Feb 22)