2017-01-07 - Re: [GRASE-Hotspot] Semi-urgent: coova-chilli[1340]: dhcp.c: 644: reached max connections 512!

Header Data

From: Michael Raynor <mx***1@gmail.com>
Message Hash: 9a5d7dc657c6032272ef73f43e1fda547572d87a994dfac876ac3468ddce32ec
Message ID: <2a1b5aa4-d0d2-4200-b983-cac236723ef5@grasehotspot.org>
Reply To: <CAESLx0+D5O5QPz37KYes+ZX2NAz2YZzhAYkKJpMa5CSAdgSugA@mail.gmail.com>
UTC Datetime: 2017-01-07 18:33:26 UTC
Raw Date: Sat, 07 Jan 2017 17:33:26 -0800

Raw message 

Hi Tim,

Thanks for the quick reply.

I have put the setting in the chilli config and it appears to have 
propagated. I just set it to match the DHCP End (for now).

/etc/chilli/config
# HS_DYNIP=
# HS_DYNIP_MASK=255.255.255.0
# HS_STATIP=
# HS_STATIP_MASK=255.255.255.0
HS_DNS_DOMAIN=hotspot.lan
HS_MAXCLIENTS=65532


/etc/chilli/main.conf
wwwdir /etc/chilli/www
wwwbin /etc/chilli/wwwsh
uamuiport 4990
adminuser
adminpasswd
maxclients 65532

We are up to 345 connections and counting - I will let you know if it 
survives past 512.

If this does work, is there a line I could put in the chilli reload/config 
refresh script that updates changes from the portal to also update said 
setting?

Also, would the HS_MAXCLIENTS variable be overwritten in a Grase update or 
would it remain persistent?


Cheers,

Michael


On Sunday, 8 January 2017 10:40:24 UTC+11, timwhite88 wrote:
>
> In theory, you need to add $HS_MAXCLIENTS to /etc/chilli/config with the 
> value of MAXCLIENTS that you want. However, as you state, there is a 512 
> hard coded in the coova-chilli code. It's not clear if that is a different 
> issue or not. Try setting MAXCLIENTS and then after restarting 
> coova-chilli, check that /etc/chilli/main.conf has the new maxclients line. 
> If you still hit the 512 limit, we'll just adjust the Coova Chilli version 
> we compile to have a higher limit.
>
> Regards
>
> Tim
>
> On Sun, Jan 8, 2017 at 9:20 AM, Michael Raynor <mx***.@gmail.com 
> <javascript:>> wrote:
>
>> Hi Tim (and everyone),
>>
>> We are having an issue with our Grase server where it refuses to dish our 
>> more DHCP leases.
>>
>> We are using the 10.50.0.0/16 subnet for Guests with DHCP Start of 2 
>> (10.50.0.2) and DHCP End of 65532 (10.50.255.253 or close to).
>>
>> In theory I was hoping that just the DHCP Start and End would be 
>> sufficient to make this work.
>>
>> /var/log/syslog shows the following:
>>
>> Jan  8 06:51:31 grase01 coova-chilli[1340]: message repeated 10 times: [ 
>> dhcp.c: 644: reached max connections 512!]
>> Jan  8 06:51:31 grase01 coova-chilli[1340]: dhcp.c: 5602: ARP: out of 
>> connections
>> Jan  8 06:51:33 grase01 coova-chilli[1340]: dhcp.c: 644: reached max 
>> connections 512!
>> Jan  8 06:51:33 grase01 coova-chilli[1340]: dhcp.c: 5602: ARP: out of 
>> connections
>> Jan  8 06:51:45 grase01 coova-chilli[1340]: dhcp.c: 644: reached max 
>> connections 512!
>>
>>
>> http://stackoverflow.com/questions/38784447/coovachilli-dhcp-server-limit-issue 
>> speaks of a maxclients variable of 512 hard coded into chilli - which 
>> doesn't sound like an easy fix.
>>
>> https://coova.github.io/mail-archive/chilli/2014-May/002729.html speaks 
>> of a maxclients setting that can be overwritten in the chilli config
>>
>> As part of Grase hotspot, is the maxclients variable being modified 
>> relative to the DHCP Start and DHCP End in the Admin Portal? If it isn't , 
>> can I manually whack this in there to get us out of trouble? Should I put 
>> it in the main.conf or the local.conf?
>>
>> I have restarted the Grase server and it appears to be working again, 
>> however "sudo chilli_query list | wc -l" has already crept back up to 331 
>> of the possibly 512 limit.
>>
>> We have three 1 week conferences ahead so I really want to find a 
>> solution ASAP.
>>
>> Thanks for your help,
>>
>> Michael
>>
>> -- 
>> 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 
>> 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/1722670a-4b5b-4328-bd0f-12876fcb407d%40grasehotspot.org 
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/1722670a-4b5b-4328-bd0f-12876fcb407d%40grasehotspot.org?utm_medium=email&utm_source=footer>
>> .
>>
>
>

Thread