1 Topic by grievah

(0 replies, posted in Chillispot Configuration)

Hello,

I have been using basic configurations of Chillispot for a while (running on OpenWRT on a WRT54GL). Users connect through wireless.

I am now receiving strange requirements from someone hosting such a box, and although it does seem impossible to achieve with Chillispot to me, maybe you will know better or may provide some hints. This person wants that:

1. if a user equipment is configured with any static IP address, he wants IP substitution to occur.
--> I guess thats impossible, but at least, the user being able to reach the captive portal (which would give instructions to the user on how to configure DHCP on his equipment) would be OK. Possible ?

2. same request, with static DNS servers configured on the user's equipment
--> tried with my basic configuration, portal is unreachable if static DNS servers do not respond. Any ideas ?

3. he also wants that if a web proxy is configured on the user's equipment, the user may still reach the portal.
--> tried with my basic configuration, portal is unreachable (as proxy is not reachable until chillispot allows it..). Any ideas ?

4. finally, he wants 2 users not to be able to route packets between themselves.
--> I tried, 2 users can ping each other. As I have iptables running, I can configure this requirement on the firewall. But was wondering if there is a better way to do this. Any ideas ?

Cheers

Go to forum: Chillispot Configuration

2 Reply by grievah

(3 replies, posted in Radius Configuration)

No, I mean that existing, established, SSH connections are NOT closed, when the Chillispot session expires.

SSH still gets forwarded, even though Chillispot redirects the browser to the hotspotlogin.cgi portal.

Go to forum: Radius Configuration

3 Topic by grievah

(3 replies, posted in Radius Configuration)

My setup:

Client  (PC) <----> Chillispot v1.1.0 (OpenWRT) <----> Freeradius v1.1.3 (Debian)

All works as configured and wanted:
1. Client tries to access a URL, and is redirected to hotspotlogin.cgi

2. Chillispot asks Freeradius, which sends back a "Acct-Status-Type = Start"

3. Client PC can then browse, establish SSH connections, etc etc

4. Until Freeradius generates an "Acct-Status-Type = Stop", reason: "Acct-Terminate-Cause = Session-Timeout"

5. Chillispot receives the information, client PC cannot browse anymore and is redirected to hotspotlogin.cgi


EXCEPT:
6. Client PC established SSH connections (puTTy) are still working, even though its browser cannot access any new site !?

Am I missing something big ?

Go to forum: Radius Configuration