| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| docs:guide-user:network:wifi:mesh:batman [2021/11/18 16:30] – [batman-adv Options for bat0 (the main mesh interface)] bonding is disabled (0) by default because it may actually decrease performance cgomesu | docs:guide-user:network:wifi:mesh:batman [2022/01/02 15:10] – [Installation] plural lastedit |
|---|
| To enable use of 802.11s mesh: | To enable use of 802.11s mesh: |
| <code> | <code> |
| | # Remove |
| opkg remove wpad-basic | opkg remove wpad-basic |
| | opkg remove wpad-basic-wolfssl |
| | |
| | # Install |
| opkg install wpad-mesh-openssl # or wpad-mesh-wolfssl | opkg install wpad-mesh-openssl # or wpad-mesh-wolfssl |
| </code> | </code> |
| |
| If building/assembling your own image, you will need to remove the default ''wpad-basic'' as it conflicts with ''wpad-mesh=*''. | If building/assembling your own image, you will need to remove the default ''wpad-basic'' as it conflicts with ''wpad-mesh-*''. |
| | |
| | [[https://github.com/openwrt/openwrt/commit/49cc712b44c76e99bfb716c06700817692975e05|As of September 2019]], ''wpad-openssl'' or ''wpad-wolfssl'' are //**also**// sufficient for 802.11s use and are the **full version** of ''wpad''. |
| | |
| | **Notes:** |
| | - ''wpad-mesh-openssl'' and ''wpad-mesh-wolfssl'' are ''wpad-basic'' (trimmed ''wpad'') with support for ''802.11s'' (mesh). |
| | - ''wpad-openssl'' and ''wpad-wolfssl'' are the **full version** of ''wpad'', they support ''802.11k'', ''802.11v'' and ''802.11s'' (mesh). |
| | - The **full version** of ''wpad'' means that nothing was trimmed and ''wpad-basic'' is the trimmed version of ''wpad'', it was trimmed to reduce its size and can be installed on routers with **low memory**. |
| |
| ''wpad'' (full) is //**not**// sufficient for 802.11s use. | |
| |
| ===== Configuration ===== | ===== Configuration ===== |
| | ''network_coding'' | boolean | ''1'' | ''0'', ''1'' | Combine two packets into a single transmission, which saves air-time but **requires**: \\ -- At least 3 nodes to be effective \\ -- One node must act as a relay which has this option enabled \\ -- Relay must support Promiscuous mode (both receive and send) \\ -- Support MTU value of at least 1546. | | | ''network_coding'' | boolean | ''1'' | ''0'', ''1'' | Combine two packets into a single transmission, which saves air-time but **requires**: \\ -- At least 3 nodes to be effective \\ -- One node must act as a relay which has this option enabled \\ -- Relay must support Promiscuous mode (both receive and send) \\ -- Support MTU value of at least 1546. | |
| | ''hop_penalty'' | boolean | ''30'' | ''not specified'' | Modify batman_adv's preference for multihop routes vs short routes, the value is applied to the TQ of each forwarded OGM, propagating the cost of an extra hop(packet must be received and re-transmitted), the higher it's the more unlikely other nodes will choose the current node as an intermediate hop towards any node, otherwise, a lower value will result in longer routes because re-transmissions aren't penalized. | | | ''hop_penalty'' | boolean | ''30'' | ''not specified'' | Modify batman_adv's preference for multihop routes vs short routes, the value is applied to the TQ of each forwarded OGM, propagating the cost of an extra hop(packet must be received and re-transmitted), the higher it's the more unlikely other nodes will choose the current node as an intermediate hop towards any node, otherwise, a lower value will result in longer routes because re-transmissions aren't penalized. | |
| | ''ap_isolation'' | boolean | ''1'' | ''0'', ''1'' | Standard WiFi APs support AP Isolation, which prevents clients communicating with each other, if the WiFi AP interface is bridged into batman-adv mesh network, it might be desirable to extend this isolation throughout the mesh by enabling this option. | | | ''ap_isolation'' | boolean | ''0'' | ''0'', ''1'' | Standard WiFi APs support AP Isolation, which prevents clients communicating with each other, if the WiFi AP interface is bridged into batman-adv mesh network, it might be desirable to extend this isolation throughout the mesh by enabling this option. | |
| | ''isolation_mark'' | string | ''0x00000000/0x00000000'' | ''0'', ''1'' | An extension of ''ap_isolation'', it allows the user to decide which client is classified as isolated via firewall rules, increasing the flexibility of the isolation, batman-adv extracts the fwmark the firewall attached to each packet it receives through the soft-interface and decides based on that value if the source client is isolated or not, this value is defined as a ''value/mask'', in the firewall, a simple case is to mark all the packets coming with a fwmark using ''tc'', you then set the fwmark you've set with ''tc'' in this option for it to work. | | | ''isolation_mark'' | string | ''0x00000000/0x00000000'' | ''0'', ''1'' | An extension of ''ap_isolation'', it allows the user to decide which client is classified as isolated via firewall rules, increasing the flexibility of the isolation, batman-adv extracts the fwmark the firewall attached to each packet it receives through the soft-interface and decides based on that value if the source client is isolated or not, this value is defined as a ''value/mask'', in the firewall, a simple case is to mark all the packets coming with a fwmark using ''tc'', you then set the fwmark you've set with ''tc'' in this option for it to work. | |
| |