Professional Documents
Culture Documents
Why Mesh?
Enables rapid deployment with lower-cost backhaul Easy to provide coverage in hard-to-wire areas Self-healing, resilient, extensible Greater range due to multi-hop forwarding
PMK is used to derive a Mesh Temporal Key (MTK), used for encrypting unicast traffic between peer mesh stations, and a group key (GTK) is derived for broadcast traffic between peers. (per station GTK)
802.1X AAA server reachability Issue: If the Authentication server is on the wired network, using 802.1X implies that both mesh stations have access to the wired network and the server. Both Peer need to act as a Supplicant and as well as Authenticator and Authenticate each other.
PREP by ROOT
Mesh Metric
Number of Hops to gateway: Simply counts the number of stations between the local station and the target destination. Less Number of Hop could mean best path but its not always the case as in between links might be not good. So combination with other factors can be used. RSSI of the next hop Mesh Point: This can be very useful in peer to peer path but if path is multi hop then Mesh path RSSI can be calculated with its use and best path can be used. Load on the Mesh Point: This defines the traffic that the mesh point is handling. This can be calculated on whole path and then lowest load path can be selected as best path Mesh Path RSSI: RSSI of all the hops are calculated and then on each path the minimum RSSI (Bottleneck) is taken in account. The path with better minimum RSSI is considered as best path. Number of Mesh Points Connected: This define number of Peers connected to station, more the number of peer more can be the Load. Using Static Routing: A pre-defined routing can be used as per user requirement. Airtime metric : the metric is a combination of data rate and bit error rate
6 Address Scheme
6 Address Example
Example 1: Ping from client (00:11:22:31:15:29) connected at 1st hop node (00:11:22:34:15:29) via MPP (00:11:22:35:15:29) to Google using 6 Address via Gateway (2C:27:D7:6D: 2A:C0)
Ping Reply from Google via Gateway (2C:27:D7:6D: 2A:C0) to MPP (00:11:22:35:15:29) to 1st hop node (00:11:22:34:15:29) to DA client (00:11:22:31:15:29)
MCCAOP responders sends MCCA Setup Reply frame that accepts or reject the MCCAOP MCCA Advertisement frames. These frames are action frames sent to the broadcast address as soon as a change occurs in a MCCAOP and contains details about the various MCCAOP on the emitting station. Any MCCA enabled neighbor mesh station in range, that could cause interference to transmissions during these reserved time periods