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

[Michael Raynor]

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

[Timothy White]

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

--
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 grase-hotspot+unsubscribe@grasehotspot.org.
To post to this group, send email to grase-...@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/1722670a-4b5b-4328-bd0f-12876fcb407d%40grasehotspot.org.

[Michael Raynor]

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

To unsubscribe from this group and stop receiving emails from it, send an email to grase-hotspo...@grasehotspot.org.

[Michael Raynor]

Hi Tim,

We are now sitting at 520 connections and haven't seen the error.

Just need to know whether the setting will be persistent with any Grase software updates.

Thanks for your help!

Michael

On Sunday, 8 January 2017 10:40:24 UTC+11, timwhite88 wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to grase-hotspo...@grasehotspot.org.

[Michael Raynor]

Hi Tim,

So everything was great for a couple of hours, until the traffic started to ramp up (233 logged in via free group).

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 780: 11 (Resource temporarily unavailable) could not read packet

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 806: 11 (Resource temporarily unavailable) net_read_eth(fd=5, len=65497, mtu=1500) == -1

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 780: 11 (Resource temporarily unavailable) could not read packet

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 806: 11 (Resource temporarily unavailable) net_read_eth(fd=5, len=65497, mtu=1500) == -1

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 780: 11 (Resource temporarily unavailable) could not read packet

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 806: 11 (Resource temporarily unavailable) net_read_eth(fd=5, len=65497, mtu=1500) == -1

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 780: 11 (Resource temporarily unavailable) could not read packet

Jan  8 19:04:05 grase01 coova-chilli[1381]: net.c: 806: 11 (Resource temporarily unavailable) net_read_eth(fd=5, len=65497, mtu=1500) == -1

It doesn't look like linux exhausted its sockets, I saw under 350 active sockets (netstat -an | wc -l).

According to the logs the above error was appearing for maybe 5 minutes, but still curious if there is another limit we need to increase.

There is talk about the "enable large limits" option when compiling coova-chilli - do you know if this is was enabled for the custom compile of coova-chilli?

Thanks,

Michael

On Sunday, 8 January 2017 10:40:24 UTC+11, timwhite88 wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to grase-hotspo...@grasehotspot.org.

[Gianluca Filippini]

Hi,
I'm interested on the "enable large limits too" since on my current (old) installation I have many problems when the number of users is high (above 150).
I see issued on coova-chilli like this one .. and also issues on freeradius queue getting full.

pbly not the same problem ...

Tim if you please can confirm the "enable large limits" option is added on the build ... that would allow me to double check on the 3.8 upgrade that I'm planning in a week.

thanks

[Timothy White]

Hi Gianluca

"Large limits" isn't enabled on any builds yet. The documentation is actually pretty vague about what large limits does. However, I don't think large limits will help you if you're having issues with 150 users. Large Limits is for >512 users. I intend to investigate large limits and enable when I can.

Can you post some of your specifications of your existing hardware, and use the support collection tool https://grasehotspot.org/support/collecting-support-information/ so we can get a better idea of your setup. I wouldn't be surprised if your issues are due to inadequate hardware for the number of connections, or older software versions.

Regards

Tim

--
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 grase-hotspot+unsubscribe@grasehotspot.org.

To post to this group, send email to grase-...@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/49f0fd48-9277-47ad-978c-a52db9f6dca9%40grasehotspot.org.

[Vicente Henríquez]

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

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

[Timothy White]

On Fri, Feb 10, 2017 at 5:54 AM, Vicente Henríquez <vicente.a...@gmail.com> wrote:

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

Hi Vicente

The dhcpstart and end need to be put in the admin interface of Grase. If you put them in /etc/chilli/local.conf, they'll get overwritten.

Regards

Tim

[Hotspotuser]

Hello

We use HS_MAXCLIENTS=65000 together with S_NETMASK=255.255.0.0 and we dont set any DHCPSTART or DHCPEND, and all works well for over 800 users at same time... Today we setup a 2500 max users hotstpot and we expect it to be ok.

Can you elaborate on why you need the DHCPSTART DHCPEND set?

[Vicente Henríquez]

Thanks Tim!!!