2012-02-12 - [GRASE-Hotspot] #56: Ability to have “slave” access points
Header Data
From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: 3af89974d069d0c4552f250650639f52adcc044cd0bee04b68c6e5b7584c0d94
Message ID: <039.02b174c4f6ef1176e57505a2ba356c18@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2012-02-12 23:31:23 UTC
Raw Date: Mon, 13 Feb 2012 06:31:23 -0000
Raw message
#56: Ability to have "slave" access points
---------------------------+-----------------
Reporter: tim | Owner: tim
Type: enhancement | Status: new
Priority: major | Milestone: 4.0
Component: Other Backend | Version: 3.7
Keywords: |
---------------------------+-----------------
Need an easy way to setup "slave" access points.
Most likely needs a 2nd VPN (or could run off the main one with
permission?)
Needs to only run chilli, and maybe a web server on the slave. Chilli
would connect to Freeradius on the master which would handle everything.
Master needs some way to register each slave, and keep track of them, give
them a different ip range for example. Any customisations of the login
screen should be available to all slaves, etc.
--
Ticket URL: <http://trac.grasehotspot.org/ticket/56>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker
Thread
- Return to February 2012
-
Return to March 2012
-
Return to “GRASE Trac <tr***c@grasehotspot.org>”
- 2012-02-12 (Mon, 13 Feb 2012 06:31:23 -0000) - [GRASE-Hotspot] #56: Ability to have “slave” access points - GRASE Trac <tr***c@grasehotspot.org>
- 2012-03-19 (Mon, 19 Mar 2012 20:37:42 -0000) - Re: [GRASE-Hotspot] #56: Ability to have “slave” access points - GRASE Trac <tr***c@grasehotspot.org>