2016-05-30 - Re: [GRASE-Hotspot] Re: Grase Hotspot working with DD-WRT routers in remote locations.

Header Data

From: Henry Terkura Swende <he***e@gmail.com>
Message Hash: 43cffad58863f32562397b1d711dcd5a925815891407b563e083f3c6ed1677ea
Message ID: <CAHoMbhdezuZ41zrAuwKoMe4_RFxoD6vQnTsUy4khuyXx-sv_nA@mail.gmail.com>
Reply To: <205375b6-59af-1674-6bbc-dbd11bb71374@radez.hr>
UTC Datetime: 2016-05-30 11:22:55 UTC
Raw Date: Mon, 30 May 2016 19:22:55 +0100

Raw message 

If you want to cover a wider area with wifi I think you should lookup
wireless mesh with openwrt I've implemented it in my facility, one ssid on
multiple routers though I'm now testing performance. I have grase run on my
server and just create ap with single ssid. Grase gives out IP address
transparently. Seems to be working pretty OK, and wireless roaming too. I
could connect to one router, obtain IP from my remote grace and ping grase
continuously while hopping from router to router.
On May 30, 2016 1:33 PM, "Dražen Žuvela" <dr***a@radez.hr> wrote:

> Hi Norberto,
>
> I just expanding local WiFi network based on your receipt for remote Grase
> access. Finally I got MACAUTH working over remote routers. Target clients
> are smartphones/tablets of employers/students, and guests. Most are MAC
> based authentication while guests and students will get limited vouchers.
>
> I did segmentation in Grase/Chili IP range as per your advice, so every
> DD-WRT router supply clients in different range: 10.1.1.0/24; 10.1.2.0/24,
> 10.1.3.0/24 ...and so on.
>
> Whole idea is to cover wider area  inside same site (Eg. school, single
> site factory/company) using existing LAN infrastructure. So all APs are set
> to the same SSID. Some of WiFi signals are overlapping each other
> (different channels are applied. I mean on pure radio signal intensity
> overlap). I assume that roaming will happen automatically.
>
> Well, seems that roaming does not happen smoothly because when changing AP
> connection client will not get new IP so it will not connect to closer AP,
> while previous got IP remains.  If fully radio disconnection occur, next
> connection attempt will succeed (client will get new IP )
>
> When more APs connected to same Chilly (as originally is to grase LAN
> side) roaming goes smoothly because no IP changes needed.
>
> Do you have any experience with this, or advice how to solve this?
>
> My set up is based on TP link WR 842ND ver.2 and firmware: DD-WRT v24-sp2
> (04/09/15) for this router.
>
> Rgds.
>
>
> *Drazen *
> 8.12.2014. u 13:15, Norberto Esteves je napisao/la:
>
> Hi Bob,
>
> dhcpend is correct since it is a count starting from first IP (10.1.0.0)
> which means dhcpend 299 is the IP 10.1.1.43. An easier way to calculate
> this would be to have each entire subnet assigned to each site:
>
> Site 1 (Master): dhcpstart 2 dhcpend 254 (range 10.1.0.1 -> 10.1.0.254)
> Site 2 (Slave): dhcpstart 257 dhcpend 510 (range 10.1.1.1 -> 10.1.1.254)
> Site 3 (Slave): dhcpstart 513 dhcpend 766 (range 10.1.2.1 -> 10.1.2.254)
> Site 4 (Slave): dhcpstart 769 dhcpend 1022 (range 10.1.3.1 -> 10.1.3.254)
> ....
>
> The rule is: Next Site will start 3 hosts away from last one and end 253
> hosts away from start
> This way Chillispot IP is always 10.1.0.1 and  we can easily identify
> which sites the clients belong to.
>
> Before coming up with this solution I used a different method assigning
> different networks to each site (Master = 10.1.0.0/24, Slave 1 =
> 10.1.1.0/24 ....) this means each Chillispot would have a different IP
> which means it is harder to do because involves more modifications to
> original code and I don't think it worth it.
>
> Next thing to do in order to solve Development Issue #56 is to add a new
> menu in Grase admin to manage and customise the remote sites and modify
> portal page to identify and adapt to each site, including different logos,
> Names, etc... also ticket printing could be adapted to reflect each site
> information.
>
> Regarding to DD-WRT Routers, I use for testing D-Link Dir-615 (hardware
> version H2) And Netgear WNDR3700 V4 for the remote sites.
> WNDR3700 can support hundreds of concurrent users.
>
> Regards,
>
> Norberto
>
>
>
>
>
>
>
> Segunda-feira, 8 de Dezembro de 2014 0:58:40 UTC, bob.hunt.52 escreveu:
>>
>> Hi Norberto,
>>
>> Thanks so much for your efforts. This looks like it might solve
>> Development Issue #56 https://github.com/
>> GraseHotspot/grase-www-portal/issues/56
>> <https://github.com/GraseHotspot/grase-www-portal/issues/56>
>>
>> One issue I noticed with your tutorial...
>> Shouldn't "dhcpend 299" really read  "dhcpend 255"?
>>
>> Also I think that standard openwrt based CoovaAP firmware (
>> http://coova.org/CoovaAP ) should work out of the box as client access
>> controller.
>>
>> Cheers,
>>
>> Bob
>>
>> On Mon, Dec 8, 2014 at 7:25 AM, Norberto Esteves <no***.@gmail.com>
>> wrote:
>>
>>> Other thing that was missing,
>>>
>>> If you want to use computer accounts you need to add the option
>>> "macauth" to Advanced Chilispot Options:
>>>
>>> defidletimeout 600
>>> interval 600
>>> macauth
>>> macpasswd password
>>> nousergardendata
>>> uamlogoutip 1.0.0.0
>>> coaport 3779
>>> dhcpstart 200
>>> dhcpend 299
>>>
>>> Regards,
>>>
>>> Norberto
>>>
>>>
>>> Domingo, 7 de Dezembro de 2014 10:14:38 UTC, Norberto Esteves escreveu:
>>>
>>>> Hi Drazen,
>>>>
>>>> Router is connected at WAN side, all remote sites connect to Grase
>>>> trough the WAN interface:
>>>>
>>>>   Remote hotspot users <=> DD-WRT <=> Internet <=> Router <=> (WAN)
>>>> GRASE (LAN) <=>Local hotspot users
>>>>
>>>> Yes, OpenWRT or other firmware with Coova Chilli built-in should work
>>>> fine.
>>>>
>>>> Best Regards,
>>>>
>>>> Norberto
>>>>
>>>> Domingo, 7 de Dezembro de 2014 8:36:03 UTC, drazen.zuvela escreveu:
>>>>>
>>>>> Hi Norberto
>>>>> This is great manual, and great solution for schools and companies
>>>>> local
>>>>> wifi network.
>>>>>
>>>>> Still I have some questions:
>>>>> 1. Which side of grase you have conneted to corporate router or
>>>>> network?
>>>>> 2. Assume Openwrt should also work.
>>>>>
>>>>> Rgds,Drazen
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 12/06/2014 02:59 AM, Norberto Esteves wrote:
>>>>> > Hi all,
>>>>> >
>>>>> > As promised, here is the information you need to setup Grase Hotspot
>>>>> > on Multiple-locationst (please Tim, feel free to move this to the
>>>>> wiki
>>>>> > if you wish).
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>> 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.
>>> To post to this group, send email to gr***.@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/859e967f-5056-4364-a94a-2c8f575e187c%40grasehotspot.org
>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/859e967f-5056-4364-a94a-2c8f575e187c%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>>
>> --
>>
>>
>> --
> 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.
> To post to this group, send email to 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/094df1a0-59ce-463c-bcc8-0af29812afea%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/094df1a0-59ce-463c-bcc8-0af29812afea%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>
>
> --
> 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.
> To post to this group, send email to 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/205375b6-59af-1674-6bbc-dbd11bb71374%40radez.hr
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/205375b6-59af-1674-6bbc-dbd11bb71374%40radez.hr?utm_medium=email&utm_source=footer>
> .
>

Thread