-
Notifications
You must be signed in to change notification settings - Fork 34
IBSS vs. 802.11s
Sven Roederer edited this page Mar 6, 2020
·
6 revisions
based on issue #670 (https://github.com/freifunk-berlin/firmware/issues/670)
Arch | board | WiFi-chip | IBSS | 802.11s | "iw info" output |
---|---|---|---|---|---|
Ramips | GLInet MT300n | MT7620 | no | yes | #{ managed, AP, mesh point } <= 8, total <= 8, #channels <= 1 |
Unifi-ac-mesh | ath10k | no | yes | #{ AP, mesh point } <= 8, #{ managed } <= 1, | |
Unifi-ac-mesh | ath10k-ct | yes | no | #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 16, #{ IBSS } <= 1 |
NOTE: This is how I understand it. Please correct me if I'm wrong
if (device AC-gen1)
if (driver is from candela)
adhoc is supported
mesh is not supported
else if (driver is the closed source version)
mesh is supported
adhoc is not supported
fi
else if (device is AC-gen2)
if (driver is from candela)
mesh and adhoc are both supported
else if (driver is the closed source version)
mesh is supported
adhoc is not supported
fi
Example: Unifi-ac-mesh with -ct firmware:
valid interface combinations:
* #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 16, #{ IBSS } <= 1,
... with non-ct firmware
valid interface combinations:
* #{ AP, mesh point } <= 8, #{ managed } <= 1,