2017-02-09 - Re: Semi-urgent: coova-chilli[1340]: dhcp.c: 644: reached max connections 512!

Header Data

From: Vicente Henríquez <vi***z@gmail.com>
Message Hash: d377c29bf458ec5b3cf35921f3455ceb1fa360b109983374676010148b7be55f
Message ID: <60092321-1c66-46d3-9cf6-2230d433b959@grasehotspot.org>
Reply To: <1722670a-4b5b-4328-bd0f-12876fcb407d@grasehotspot.org>
UTC Datetime: 2017-02-09 12:54:15 UTC
Raw Date: Thu, 09 Feb 2017 11:54:15 -0800

Raw message 

Hi Michael!

Today i started config the CoovaChilli with a "kinda huge" pool range and i 
have (i don't know it is a great idea) solution. I make this changes in 
/etc/chilli/conf

HS_NETMASK=${HS_NETMASK:-255.255.252.O}

and put the next thing after HS_DNS_DOMAIN:hotspot.lan

HS_MAXCLIENTS=1022

I put this because i need this config 

*Address* (Host or Network) *Netmask* (i.e. 24) *Netmask* for sub/supernet 
(optional)
 / move to: 
 limpiar <http://www.aprendaredes.com/cgi-bin/ipcalc/ipcalc_cgi>

------------------------------
Address:     10.1.0.1              00001010.00000001.000000 00.00000001
Netmask: 255.255.252.0 = 22 11111111.11111111.111111 00.00000000
Wildcard: 0.0.3.255 00000000.00000000.000000 11.11111111
=>
Network:     10.1.0.0/22           00001010.00000001.000000 00.00000000
HostMin: 10.1.0.1 00001010.00000001.000000 00.00000001
HostMax: 10.1.3.254 00001010.00000001.000000 11.11111110
Broadcast: 10.1.3.255 00001010.00000001.000000 11.11111111
Hosts/Net: 1022 Class A, Private Internet 
<http://www.ietf.org/rfc/rfc1918.txt>
and after make this changes, i modify /etc/chilli/local.conf with this (if 
you do a cat /etc/chilli/local.conf show this config)

macpasswd=password
defidletimeout=600
nousergardendata
interval=600

and you need put the next thing

macpasswd=password
defidletimeout=600        
*dhcpstart=2*
*dhcpend=1021   you can define the pool range that you want, but in my case 
it's was that because use class A network*
nousergardendata
interval=600


Sorry for my english!!! 

Regards, Vicente



Michael Raynor escribió:

> 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
>

Thread