Adhoc Mode, Association and MSDU Aggregation

Dear Falk,

> as far as I can see, there is only MPDU Aggregation implemented and no MSDU Aggregation. Is it right?
That is correct; although, it should be "straightforward" to implement
MSDU Aggregation using the Concatenation FU from the LDK. The trick of
the MPDU Aggregation is the enhanced error resilience that comes with
the extra headers and CRCs inserted in the packet "train". This
resilience is simulated via the "DeAggregation" FU that is inserted in
the convergence part of the FUN - in short, extra effort is required to
correctly simulate A-MPDUs. For A-MSDUs, this is not the case.

> Furthermore I would like to know if it is right, that only MPDUs for the same receiver are aggregated.
That is correct (and 11n - conform).

> Is there Beacon Generation for Adhoc Modus implemented?
No. Actually, the Adhoc Modus for STAs is not implemented.

However, I would recommend to use the mesh network capability (with MPs
instead of STAs) instead using an Adhoc Modus. If the topology is fully
meshed, then the results should be similar to a adhoc mode. Furthermore,
the path selection FU supports multi-hop topologies.

> Is there a real association frame exchange sequence implemented or does the station only selects an available AP, but does not perform authentication etc.?
There is no real association frame exchange sequence implemented. STAs
select the AP according to the best received beacon (highest RSS) during
the scan time (default 0.3s). The association is done "virtually", i.e.
without the exchange of control frames.

BR,
Sebastian