2018-09-25 - Re: [GRASE-Hotspot] Re: CoovaChilli Login Page

Header Data

From: Drazen Zuvela -gmail <dr***a@gmail.com>
Message Hash: 9e2062318cfad977fa2f83e527bdea9c3c1b949fb6dc39722db8a677bbad6f88
Message ID: <10da2d13-34f3-a112-6a85-28a84babdec6@gmail.com>
Reply To: <15e2b9c0-846a-4ad6-8cb3-3b3b9bba94e4@grasehotspot.org>
UTC Datetime: 2018-09-25 10:42:18 UTC
Raw Date: Tue, 25 Sep 2018 19:42:18 +0200

Raw message 

Sergen

actually this is solved and I have working system for years now. I will 
need to check my archives because I saved complete setup instructions 
from this group messages where one other member (can't remember his name 
at the� moment) did it and explain all setup.
Hopefully tomorrow at work will be able to find instruction. There is 
also a chance that I lost them, but they must be somewhere on this 
collaboration group. Maybe Tim or someone else still remember that 
topic. I think the author was from Spain or Portugal.
Just general description:
As Tim said you will need Coovachilli at the each remote location.

This is achieved this way:
1. at each remote location you will need one router (or single 
AP/router) with DD-WRT or Open-WRT router firmware on it.
2. There is exact setting how to configurre Covachili at each site and 
connect to central Grase radius.
3. LAN network should be divided into several subnetworks. Or, (not sure 
at the moment) whole IP class� need to be extended to have enough 
addresses. At each location local DHCP range should be divided to cover 
single range without overlaping with other range.

In such system you can maintain clients centrally at the Grase. You can 
see them in sessions, but you will not see traffic log from remote 
sessions. Clients are in kind of roaming when moving from one location 
to another. Only issue is that if they are moving form one location to 
another without interrupting connection (same SSID in close proximity to 
each other but belongs to different sub/DHCP range) it will not work. In 
such case client still carry DHCP address from previous location which 
will not work in another location. Client need to refresh connection. 
Simplest way turn client Wifi Off then On.

Till tomorrow.

Drazen Zuvela


09/17/2018 u 08:08 AM, Sergen �olak je napisao/la:
> Hi Tim
> I'm sorry for the late reply. The fiction I've tried is like this.
> Central is a hotspot server. And a few locations that are far away 
> from this center. They're not on the same network. Can I access the 
> login page by routing with the router?
>
> 14 Eyl�l 2018 Cuma 10:49:34 UTC+3 tarihinde Sergen �olak yazd\u0131:
>
>     Hello everyone,
>     I have a question about Coovachilli.
>     The default network layout,
>     WAN PORT: 192.168.1.210
>     LAN PORT: 192.168.80.1/24 <http://192.168.80.1/24>
>     We can access the control panel with the Wan port. However, we can
>     not access the login page through the WAN port. Can I get the
>     login page from WAN Port?
>     I hope I can tell. I apologize for the bad english.
>     Thank you.
>
> -- 
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google 
> Groups "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to gr***e@grasehotspot.org 
> <mailto:gr***e@grasehotspot.org>.
> To post to this group, send email to gr***t@grasehotspot.org 
> <mailto:gr***t@grasehotspot.org>.
> Visit this group at 
> https://groups.google.com/a/grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit 
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/15e2b9c0-846a-4ad6-8cb3-3b3b9bba94e4%40grasehotspot.org 
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/15e2b9c0-846a-4ad6-8cb3-3b3b9bba94e4%40grasehotspot.org?utm_medium=email&utm_source=footer>.

Thread