Bugzilla – Bug 326
Multicast and Broadcast traffic is fragmented and shouldn't be.
Last modified: 2005-10-03 13:34:23
You need to log in before you can comment on or make changes to this bug.
When fragmentation is enabled (iwconfig eth1 frag X) and multicast or broadcast packets larger or equal to Fragmentation Threshold are sent, they are fragmented. Moreover, in IBSS, mode sending broadcast or multicast packet larger than Fragmentation Threshold causes loosing connection (no data is transmitted any more between DUT and wireless peer)and the driver sends only first fragment of the whole broadcast/multicast packet (size X+28 bytes). Repro: Establish BSS or IBSS connection Enable fragmentation - iwconfig eth1 frag X Send broadcast packet of size X+1 from server to DUT or from wireless peer to DUT (ping -s X+1 -c 1 10.72.2.99) In case of multicast firstly set routing of network 224.0.0.0 to wireless interface (eth1) - for example - ip route add 224.0.0.0/16 dev eth1 Send multicast packet of size X+1 (ping -c 1 -s X+1 224.0.0.1)
We have a fix in place for this that has minimal impact to the code regression testing required. The problem is currently fixed in 0.60 if you are using an encrypted sessions. The fix was to make a two line code path execute whether encryption is enabled or not.
Please mark as fixed.
Note that in 0.60 it still does not work.
Fixed in 1.0.1
verified