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

Header Data

From: Gianluca Filippini <gi***4@gmail.com>
Message Hash: 6975c44467f3dc4ff6166eeaff382e867d47c3e5757b0e37f04dfd2bfcd48380
Message ID: <49f0fd48-9277-47ad-978c-a52db9f6dca9@grasehotspot.org>
Reply To: <ead47ddd-2dcc-49de-b069-53ba68d72dfb@grasehotspot.org>
UTC Datetime: 2017-01-22 02:02:46 UTC
Raw Date: Sun, 22 Jan 2017 01:02:46 -0800

Raw message 

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

On Sunday, January 8, 2017 at 9:45:29 AM UTC+1, Michael Raynor wrote:
>
> 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[1
>
>

Thread