| | 32 | |
| | 33 | * {{{Idle}}} → {{{MPDU Tx}}}: This transition occurs when two conditions are met: (a) The [wiki:../Low low-level MAC] has indicated that it is ready to receiver another packet for wireless transmission and (b) the transmit queue in the high-level MAC contains a packet that needs to be sent. |
| | 34 | |
| | 35 | * {{{Idle}}} → {{{MPDU Rx}}}: This transition occurs when the [wiki:../Low low-level MAC] has indicated that a reception has occurred with the following criteria: (a) the received packet is not a control packet (e.g. ACK, RTS, CTS) and (b) the received packet has a receiver address that is either a broadcast packet or a unicast packet whose address matches the MAC address of the node running this software. |
| | 36 | |
| | 37 | * {{{MPDU Rx}}} → {{{Ethernet Tx}}}: This transition occurs when a wireless MPDU data reception occurs that should be de-encapsulated and via Ethernet. Note: Unlike the {{{MPDU Tx}}} state, the {{{Ethernet Tx}}} state does not employ a queue. As such, it can be directly accessed from the {{{MPDU Rx}}} state without transitioning through {{{Idle}}}. The reason for this is that, even at the fastest 802.11g rates, wireless packets are much slower than wired packets. When receiving a wireless packet, there is enough time to directly transmit a wired packet without halting the next wireless reception. This is not the case for wired receptions. |
| | 38 | |
| | 39 | * {{{Idle}}} → {{{Ethernet Rx}}}: This transition occurs when any packet has been received by the Ethernet MAC on the board. |
| | 40 | |
| | 41 | * {{{Idle}}} → {{{Scheduled Event}}}: |
