Re: Chillispot FreeRadius
I don't understand, Chilli is running on a WRT54G AP under DD-WRT and directing users to the login. What sends the Radius requests Chilli or the CGI script? The chilli daemon - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Chillispot FreeRadius
On 7/15/05, sean [EMAIL PROTECTED] wrote: On Fri, 2005-07-15 at 20:58 +0200, freeradius-users- [EMAIL PROTECTED] wrote: I have setup pinholes for both tcp and udp on ports 1812, 1813 and 1814. They all point to the Radius server on 192.168.1.2. The Chillispot on 192.168.1.6 can direct traffic to the CGI login but sends nothing to Radius. What I'm trying to understand is the sequence of events. When the hospotlogin.cgi script gets a request from a Chillispot user from the AP, does the cgi script initiate the Radius request? No, it's the chillispot server - not the cgi. Server is in case you run chilli on the wlan-router the wlan-router, in case you ran chilli on an linux-box the linux-server. I don't understand, Chilli is running on a WRT54G AP under DD-WRT and directing users to the login. What sends the Radius requests Chilli or the CGI script? I think Chilli is the CGI script. You should ask the Chillispot developers that question. Maybe it is on their website. This is what Chilli sends to the hotspotlogin.cgi script https://82.141.232.132/cgi-bin/hotspotlogin.cgi/? res=notyetuamip=192.168.182.1uamport=3990challenge=1b23fb5583173741fcfcb91b7b4e5e7auserurl=nasid=nas01mac=00-C0-49-5C-40-48 Radius gets no requests at all. The script just times out while waiting to login. 192.168.182.1 is the DSL modem which has been told to send traffic arriving on ports 1812, 1813, and 1814 to the Radius server. I have also opened port 3990 on the DSL modem to the Radius server. ie. DSL modem static ip 82.141.232.132. all traffic to 192.168.182.1 (82.141.232.132:1812) goes to 192.168.1.2:1812 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Chillispot FreeRadius
On Fri, 2005-07-15 at 20:58 +0200, freeradius-users- [EMAIL PROTECTED] wrote: I have setup pinholes for both tcp and udp on ports 1812, 1813 and 1814. They all point to the Radius server on 192.168.1.2. The Chillispot on 192.168.1.6 can direct traffic to the CGI login but sends nothing to Radius. What I'm trying to understand is the sequence of events. When the hospotlogin.cgi script gets a request from a Chillispot user from the AP, does the cgi script initiate the Radius request? No, it's the chillispot server - not the cgi. Server is in case you run chilli on the wlan-router the wlan-router, in case you ran chilli on an linux-box the linux-server. I don't understand, Chilli is running on a WRT54G AP under DD-WRT and directing users to the login. What sends the Radius requests Chilli or the CGI script? This is what Chilli sends to the hotspotlogin.cgi script https://82.141.232.132/cgi-bin/hotspotlogin.cgi/? res=notyetuamip=192.168.182.1uamport=3990challenge=1b23fb5583173741fcfcb91b7b4e5e7auserurl=nasid=nas01mac=00-C0-49-5C-40-48 Radius gets no requests at all. The script just times out while waiting to login. 192.168.182.1 is the DSL modem which has been told to send traffic arriving on ports 1812, 1813, and 1814 to the Radius server. I have also opened port 3990 on the DSL modem to the Radius server. ie. DSL modem static ip 82.141.232.132. all traffic to 192.168.182.1 (82.141.232.132:1812) goes to 192.168.1.2:1812 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
