I'm testing the latest 7.09 build of OpenWRT with Meraki hardware and I think there might be a memory leak in the association / disassociation.

I am testing with my laptop (running WinXP) and the AP running in ap mode.  I'm using a static ip for my laptop to try to limit the number of processes running on the AP (no dhcp server).  I'm using the XP repair function to disassociate and reassociate to the AP.

what I'm seeing is 4k being lost when I type the 'free' command... it doesn't happen every time, but after two or three repairs 4k disappear, never to return.

investigating further, /proc/meminfo shows that the 'Slab' goes up without going down. 

looking at the /proc/slabinfo files shows that the biggest changes (diff files at different points in time) come from the following:
jffs2_node_frag
jffs2_full_dnode
size-4096
size-2048
size-512
size-64

I don't really know if any of this information is useful, but I am trying to find what my next step should be.  If anyone has any advice to help figure this out, please let me know.

Thanks

I'm observing similar memory leaks on an Asus WL500g Premium, with Kamikaze 7.09. I suspect that this might be related to the following problem: when I connect to the wireless network of the router from my Windows XP laptop, using either WPA or WPA2, everything seems fine for the first time. The wireless client reports a signal strength of Excellent and a speed of 54 Mbps. From this point the speed starts dropping till 1 Mbps, with a constant signal strength of Excellent or Very good. When 1 Mbps is reached reauthentication occurs and a new DHCP request is also issued. The reauthentications occur with such frequency so that the wireless network is rendered completely useless. It seems that every reauthentication sends a wl0: invalid argument to the console. The same story can be observed on other clients as well. Has anybody seen and been able to solve such a problem?

if you bring down the interface and then back up, does the memory get restored?  If yes then this may be a temp workaround to this serious problem.

Thank you for your answer! The memory, or at least a great chunk of it, seems to get restored - however, the reauthentications remain. I have tested with WPA{1|2}/{Enterprise|PSK} (all combinations, that is), but no joy. I've already found a dev ticket discussing similar issues, but nothing useful for me so far. Luckily, I only have to resort to wifi about once in a leap year, but still...
EDIT: I've just read this thread: http://forum.openwrt.org/viewtopic.php?id=14540 I also seem to have a high Tx excessive retries number (3235) while Rx invalid is 0.

(Last edited by neutron on 5 Apr 2008, 18:38)

with wep no problem ... with wpa2 problem "no argument" appears and wifi unstable, known problem ... no fix yet if i remember