Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit ec9e303b6c5604c3b1e3e2377ff152ba462a8222 Author: Antonio Quartulli a@unstable.cc Date: Sun Feb 19 19:07:05 2012 +0000
doc: batman-adv/Ap-isolation
ec9e303b6c5604c3b1e3e2377ff152ba462a8222 batman-adv/Ap-isolation.textile | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+)
diff --git a/batman-adv/Ap-isolation.textile b/batman-adv/Ap-isolation.textile new file mode 100644 index 00000000..55ff8c95 --- /dev/null +++ b/batman-adv/Ap-isolation.textile @@ -0,0 +1,22 @@ +h1. Ap-isolation + +h3. What is it? + +Like any commercial Access Point, the "Access Point Isolation" is that feature which prevent any communication between stations connected to the same infrastructured BSSID. B.A.T.M.A.N.-Advanced replicates the same behaviour by denying communications between clients connected to their nodes through a wireless link. + +h3. How to enable it? + +<pre> +batctl ap_isolation 1 +</pre> +or +<pre> +batctl ap 1 +</pre> +To disable it, just switch 1 to 0 + +Note that packets are checked either at the sender and at the receiver node, therefore, if at least one of those enabled the AP-Isolation, the communication is forbidden. However we strongly suggest to enable the AP-Isolation on all the nodes in order to prevent wasting of resources (e.g. send of data over the mesh knowing that it is going to be dropped at the receiver) + +h3. Technical details + +to be added \ No newline at end of file