[MLB-WIRELESS] HotSpot Setup

[Craig Sanders]

On Wed, Apr 11, 2007 at 03:39:35PM +1000, gregsonm at aanet.com.au wrote:
> I am interested in setting up a hotspot that is easy to setup and uses off
> the shelf hardware/software.
> 
> The HotSpot must have security so that people must have authorisation to
> use it, either via a ticket/token or password.
> 
> Does anyone out there have any suggestions on how this can be done?

haven't used it myself yet (am planning to trial it this weekend if i get
time), but you might want to have a look at chillispot.

http://www.chillispot.org/

from the web site:

    "ChilliSpot is an open source captive portal or wireless LAN access
     point controller. It is used for authenticating users of a wireless
     LAN. It supports web based login which is today's standard for
     public HotSpots. Authentication, authorization and accounting (AAA)
     is handled by your favorite radius server.

     Binary downloads are available for Redhat, Febora, Debian, Mandrake
     and OpenWRT. ChilliSpot is an ebuild in Gentoo and compiles under
     FreeBSD. Source code under GPL is available for other platforms.

     To build your own HotSpot you need the following items:

         * Internet connection
         * Wireless LAN access point
         * ChilliSpot software for your PC
         * Radius server
         * Web server"

and:

     "It supports two authentication methods:

         * Universal Access Method (UAM)
         * Wireless Protected Access (WPA)

     With UAM the wireless client requests an IP address, and is
     allocated a an IP address by Chilli. When the user starts a web
     browser chilli will capture the tcp connection and redirect to
     browser to an authentication web server. The web server queries the
     user for his username and password. The password is encrypted and
     sent back to chilli.

     With WPA authentication is handled by the access point, and
     subsequently forwarded from the access point to chilli.  If WPA
     is used the connection between the access point and the client is
     encrypted.

     For both UAM and WPA chilli forwards the authentication request to
     a radius server. The radius server sends an access-accept message
     back to chilli if authentication was successful. Otherwise an
     access-reject is sent back."




my wireless AP is a laptop running debian (linux 2.6.20 with hostap
drivers, senao 200mW card connected to an 8dbi omni on a 12m mast on
roof), so getting it all working should be fairly easy.

craig

-- 
craig sanders <cas at taz.net.au>

ps: anyone in inner-north region who can see my node
(cja.wireless.org.au) is welcome to use my debian 'sid' mirror. see
http://surya.taz.net.au/ for more info. mirror is updated daily
direct from ftp.us.debian.org, which is better than you can say for
other australian mirrors, including ftp.au.debian.org

unfortunately, i'm at the bottom of the Merri Creek valley (Coburg, nr
cnr of Bell St & Nicholson St), so even with a 12m mast on my roof, it's
difficult for anyone to see my node.


BOFH excuse #188:

..disk or the processor is on fire.