Bug #193
closedis there a client-limit per node?
0%
Description
There seem to be a client-limit per node on batman-adv routers. On the "bonn-freifunk mailinglist" was a problem discussed which limits the clients per node to around 72 clients.
The author thinks the problem is around the fact that the maximum fragment size is set to 16 and the batman-adv nodes cant communicate more than 72 clients on one packet, because of the limitation to 16 fragments.
Since they are using 2013.x I thought on reading this thread this problem should be fixed with batman-adv 2014.x. But on the last 4 days we had a festival in our town, and 2014.x seem to have similar problems.
Is there a way to fix this problem to get more than 200 clients on a node?
Updated by Marek Lindner over 9 years ago
Please read the entire thread and then come back with questions:
https://lists.open-mesh.org/mailman3/hyperkitty/list/b.a.t.m.a.n@lists.open-mesh.org/thread/6IR5GCSI2QA2ZV4LMZWO2R7WVMMYL3VZ/#QTKXBXQMS6HGQRBUPWFN5UMP3NSRYLR5
Updated by Ruben Kelevra over 9 years ago
Thank you for your answer.
I did already had over 150 clients on a bridging ap on large festivals. As Felix said there is no hard client limit.
The clients which can't 'connect' was stucking on 'receiving ip address which might lead to a routing or Batman-adv client/server management problem.
Since we have more than one Hotspot which seem to hit this issue every week I might investigate further if you might point a possible fix out.
Best regards
Ruben
Updated by Ruben Kelevra about 9 years ago
We are still very interested in a fix, if this is issue still exist.
I think we going to test around a bit next days on batman-adv 2014.4 and figure out if there's a client limit or not.
Thanks for the kind reminder!
Updated by Marek Lindner about 9 years ago
Ruben Kelevra wrote:
We are still very interested in a fix, if this is issue still exist.
I think we going to test around a bit next days on batman-adv 2014.4 and figure out if there's a client limit or not.
As far as I remember, it wasn't even proven that the client limit had anything to do with batman-adv ?
Updated by Ruben Kelevra about 9 years ago
Sorry, but #204 does have a higher priority for us. After we found what cause this issue, we have time to address this one. :)
Updated by Marek Lindner about 9 years ago
Updated by Ruben Kelevra almost 9 years ago
So, we just got 104 Clients on a mesh-node, which meshes over 5 GHz. It's a 128 MByte RAM device.
Just in case you're wondering how much ram this consumes:
# free -h total used free shared buffers Mem: 126452 30160 96292 0 2384 -/+ buffers: 27776 98676 Swap: 0 0 0
the load is fairly low for this much clients:
load average: 0.52, 0.54, 0.44
And top:
Mem: 29960K used, 96492K free, 0K shrd, 2384K buff, 7308K cached CPU: 2% usr 6% sys 0% nic 81% idle 0% io 0% irq 9% sirq Load average: 0.46 0.48 0.43 1/43 31843 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 1299 1 root S 1652 1% 3% /usr/sbin/hostapd -P /var/run/wifi-ph 1323 1 root R 1632 1% 2% /usr/sbin/hostapd -P /var/run/wifi-ph 2839 2 root SW 0 0% 1% [kworker/u2:1] 9253 2 root SW 0 0% 1% [kworker/u2:3]
# batctl -v batctl 2014.3.0 [batman-adv: 2014.3.0]
Pretty nice overall, so I think we can close this bug! :)
Updated by Marek Lindner almost 9 years ago
- Status changed from New to Closed
Nice! Thanks for the verification.
Updated by Sven Eckelmann about 7 years ago
- Status changed from Closed to Rejected