Chillispot seems to be ignoring, or not acting quickly enough for the max download octets

[mrplibble]

Hi there,

Not sure if this is the best place for this type of query, and I can't find anything else like it here, so I will post and hope I don't get banned or moaned at :)

I have chilli configured to allow each session a max download of 25MB (26,214,400 octets).
This seems to be ignored, well, more specifically, temporarily ignored and allows user sessions to download a further upto ~4.5MB-5MB before shutting down the session.

Is there anything anywhere that suggests that the speed of the traffic flowing through chilli might be too quick for chilli to act when it needs to? This is my guess, but I have no way of proving this, it's just a hunch right now.

The sessions are on a 4G router, so bandwidth speeds are >10Mbps.

Thoughts / suggestions please.

Christian.

[wlanmac]

Chilli should cut off access right away. Are you seeing the byte could in chilli go past the limit, or are you getting that usage data from some other source? If so, it could be that the figure includes more headers in the count. You also might need to turn off GSO/TSO using ethtool.

[mrplibble]

Hi, thanks for the response, when running "chilli_query -s chilli2.socket list" I can see the list of sessions and the various options that are configured etc, one being the max download octets. What I am seeing is the max download octets set are a figure, but the actual downloaded octets goes beyond, sometimes by quite a bit passed the max that was set.

[mrplibble]

incidentally, I turned off GSO/TSO and it made no difference, it still didn't cut off the session as it hit the limit, the session carried on passing data for a short while after the limit was reached causing the max download octets to not get obeyed.

is it a timing issue? i mean, it feels like coova chilli isn't quick enough to cut off the session as it hits the limit. it seems to update every 1000ms perhaps? and in that 1000ms depending on the bandwidth available to that user session, anything upto ~4MB could have passed beyond the max allowed.

Does that seem right? that it might be a plausible theory? It's only what I've observed and have no real evidence or knowledge/skill to back that up.

[mrplibble]

Hi Guys,

Does anyone have any help to give on this one? It's really a huge problem for us, and it's turned round and bitten us in the rear end. Any help will be much appreciated.

Is this a confirmed bug? Can we get some feedback on this asap?

Cheers :)

[sevan]

Can you try the latest version from git and provide feedback if the issue still persists

[mrplibble]

built our firmware with the latest build of coova chilli, just going to test it out today.
Thanks for the advice, will post results later.

[nzamps]

You could also try changing CHECK_INTERVAL from 3 to 1 in chilli_limits.h and recompiling:

#define CHECK_INTERVAL 1 /* Time between checking connections */

[mfaroukg]

pinging google is ignored !!!!