On Wed, May 28, 2014 at 12:43 PM, Yeoh Chun-Yeow <yeohchunyeow@xxxxxxxxx> wrote: >> While looking through the code I noticed that there seems to be no code-path >> that removes stall mpp_path entries (except for the removal of the mesh >> interface) ! Unless I overlooked something this would be a way to use up all >> existing memory of the kernel by sending it 802.11s packets with changing >> proxied addresses. > > AFAIK, we don't really "manage" the mpp path and relying on incoming > packet to update the mpp path table. Imagine a malicious or maybe misbehaving node that is sending you proxied traffic and is just counting up the source mac address. Every received packet would generate another entry in the mpp_path table. Even without this, one usecase for 802.11s is to connect multiple access points and allow clients to roam between them and not loosing internet connectivity through a gateway. A scenario like this would have one mpp_path table entry for every client that has connected to the network... even if it has been years ago. Henning Rogge -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
