Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2019-09-14,master
commit f26f2640b63a77d2d8cdb03326633dfa0a27c2b9 Author: Sven Eckelmann sven@narfation.org Date: Sun Mar 3 19:36:47 2019 +0000
doc: batman-adv/Extended-isolation
f26f2640b63a77d2d8cdb03326633dfa0a27c2b9 batman-adv/Extended-isolation.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/batman-adv/Extended-isolation.textile b/batman-adv/Extended-isolation.textile index 32f8f42..df2560e 100644 --- a/batman-adv/Extended-isolation.textile +++ b/batman-adv/Extended-isolation.textile @@ -22,7 +22,7 @@ With these commands, all the the packets coming in through _eth1_ will be marked
The next step it is to configure batman-adv properly, meaning that the user must tell the kernel module which is the value to match in the _skb->mark_ field when detecting isolated clients. <pre> -# batctl isola 0x06/0xFFFFFFFF # VALUE/MASK +# batctl isolation_mark 0x06/0xFFFFFFFF # VALUE/MASK </pre>
As reported in the example above, the isolation mark needs to be configured in batman-adv in the form _VALUE/MASK_ in order to keep the mechanism as flexible as possible.