2014-12-03 - Re: [GRASE-Hotspot] Re: Grase Hotspot working with DD-WRT routers in remote locations.

Header Data

From: Dražen Žuvela <dr***a@radez.hr>
Message Hash: 04f6e5e9e23ba2e67e3f5afec6f8d70ff0c4c0e669c72c8684b1d5b7a381dcb6
Message ID: <547EB8D1.6050000@radez.hr>
Reply To: <c36d2e76-109d-401f-a8fa-f11ce7b974a8@grasehotspot.org>
UTC Datetime: 2014-12-03 00:16:33 UTC
Raw Date: Wed, 03 Dec 2014 08:16:33 +0100

Raw message 

I am joining  to Antonio.
Would be nice to see that solution documented.
Drazen

Dana 3.12.2014. 0:19, Ant�nio Chimuzu je napisao:
> Norberto
> You are a genius. I suck at fidling with any of this stuff but if you 
> can make that work please share.
> Im willing to have a setup like this:
> remote router 1 (dd-wrt / tomato, etc) --\
>     \
>       \
>          - - - - - - - grase (on cloud virtualbox server)
>      /
> remote router 2 (same setup) -------------/
>
> Cheers
>
> On Tuesday, December 2, 2014 9:38:54 PM UTC+2, Norberto Esteves wrote:
>
>     Hi all,
>
>     I managed to get this configuration working.
>
>     Basically I have the Grase Hotspot installed in a machine (shuttle
>     XPC DS6) in the office and one router (D-Link DIR-615) with DD-WRT
>     in my house for testing.
>     The remote site (D-Link Router) uses the Coova Chilli included
>     with the DD-WRT firmware to redirect users to the Grase
>     authentication Portal, after that, the username, password, and
>     other attributes are checked with the radius server. If the
>     authentication is successful then the user is allowed to use the
>     Internet and DD-WRT Coova Chilli takes care of the session even if
>     the main site (Grase) goes down. DD-WRT Coova Chilli also sends
>     periodical data (every 5 minutes) to Radius server to keep
>     information up to date.
>
>     So far I had to change a few things in the follwing files:
>     hotspot.php, nojsstatus.php, /includes/site.inc.php
>
>     I do not use VPN, so, there is a few ports that need forwarding:
>     In the main site: Radius (1812, 1813, 1814), UAM (3990) and HTTP
>     (80) ports forward to Grase Hotspot machine.
>     The remote site only needs port forwarding for COA port 3779 if
>     you are going to use the radclient to disconnect users.
>
>     Freeradius also needs to allow remote site to connect, to do this
>     you need to add remote client to clients.conf, or use nas table.
>
>     So far I'am still testing and correcting some "bugs" i found.
>
>     The bad new is that this setup don't work with Javascript login, I
>     did some tests and I think DD-WRT is not able to use the JSON
>     interface for Coova Chilli. So if you want to use DD-WRT, Java
>     script login should be disabled.
>
>     If anyone is interested in multi-location setup using DD-WRT I can
>     make a document and share with the community.
>
>     Regards,
>
>     Norberto Esteves
>
>
> -- 
> 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 
> http://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/c36d2e76-109d-401f-a8fa-f11ce7b974a8%40grasehotspot.org 
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/c36d2e76-109d-401f-a8fa-f11ce7b974a8%40grasehotspot.org?utm_medium=email&utm_source=footer>.

Thread