2014-11-03 - Re: [GRASE-Hotspot] Grase on Routed Networks + Billing

Header Data

From: Edward Allen <yb***j@gmail.com>
Message Hash: fc93be4a918707c9b959289ee67a4fe81bd8e047af084853339687ab06bc1d13
Message ID: <c6d6dbe1-5af5-4160-b626-b0d1d7f09205@grasehotspot.org>
Reply To: <CAESLx0Ke6g7p=3RnRLf1MQEUbR-cprvy_fiEt6Umvp0fdW=rgw@mail.gmail.com>
UTC Datetime: 2014-11-03 08:47:48 UTC
Raw Date: Mon, 03 Nov 2014 07:47:48 -0800

Raw message 

Thanks for your reply TIM.


As grase grow I believe there will be more and more request similar what 
what I've asked above. I believe this is the networking model that will be 
most likely used in most areas. Im not really a programmer, im from the old 
pascal c and asm days, with little time right now to learn new tools.


it would be good to implement the mode for grase to work in routed 
environments versus flat Lans. NATted lans might not be easy as only the 
device that does the NAT would authenticate but then i believe this would 
be a desired outcome anyways. This could be a configuration setting.

I'll try my best to provide whatever help I can to achieve this.


On Sunday, 10 August 2014 01:08:10 UTC-5, timwhite88 wrote:
>
> Hi Edward
>
> The Coova Chilli module that we use to do the captive portal, can be done 
> in Layer 3 mode, where your routers do all the DHCP etc, and the Coova 
> Chilli just does Layer 3 routing. The way I have it setup with the Grase 
> Hotspot is in the default Layer 2 routing instead. I've not played with the 
> Layer 3 routing, and unfortunately don't have the time.
>
> I'm also not going to have any time to write a billing module, however 
> feature branches from the git repository are welcome, if you have the 
> skills to implement one.
>
> Tim
>
>
> On Thu, Aug 7, 2014 at 11:11 AM, Edward Allen <yb***.@gmail.com 
> <javascript:>> wrote:
>
>>
>> Is it possible to deploy grase on routed networks? I'm thinking it should 
>> still WORK but i want to make sure.
>>
>>
>>
>> Example
>>
>> Internet ------> Grase (10.10.0.X)--------->Network A 
>> (192.168.0.X)------>> Network C(192.168.100.X)
>>                                            |------------>Network B 
>> (172.16.0.X) ------->> Network D (172.16.2.X)
>>
>> Assuming there are routers between the different network legs, and all 
>> routes are known/set statically or otherwise.
>>
>>
>> When i say WORK I'm also referring to the system being able to provide 
>> auth to all clients. I'm thinking that the Machine clients might not work 
>> seen that MAC addresses gets replaced during routing. what would be a 
>> workable solution for this?
>>
>>
>> Also is there any possibility of having a billing module?
>>
>> I was thinking that maybe having some form of PPPOE to authenticate 
>> against the user database.....??
>>  
>> -- 
>> 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***.@grasehotspot.org <javascript:>.
>> To post to this group, send email to gr***.@grasehotspot.org 
>> <javascript:>.
>> 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/fc98436f-5002-4143-b2d9-fa34ad53f48f%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/fc98436f-5002-4143-b2d9-fa34ad53f48f%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>

Thread