From: Antonio Quartulli <antonio@meshcoding.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <antonio@open-mesh.com>
Subject: [B.A.T.M.A.N.] [PATCHv3 4/6] batman-adv: extend the ap_isolation mechanism
Date: Sat, 16 Nov 2013 12:03:50 +0100 [thread overview]
Message-ID: <1384599832-3959-5-git-send-email-antonio@meshcoding.com> (raw)
In-Reply-To: <1384599832-3959-1-git-send-email-antonio@meshcoding.com>
From: Antonio Quartulli <antonio@open-mesh.com>
Change the AP isolation mechanism to not only "isolate" WIFI
clients but also all those marked with the more generic
"isolation flag" (BATADV_TT_CLIENT_ISOLA).
The result is that when AP isolation is on any unicast
packet originated by an "isolated" client and directed to
another "isolated" client is dropped at the source node.
Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
---
translation-table.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/translation-table.c b/translation-table.c
index 09b1112..9c8d55f 100644
--- a/translation-table.c
+++ b/translation-table.c
@@ -1865,6 +1865,11 @@ _batadv_is_ap_isolated(struct batadv_tt_local_entry *tt_local_entry,
tt_global_entry->common.flags & BATADV_TT_CLIENT_WIFI)
ret = true;
+ /* check if the two clients are marked as isolated */
+ if (tt_local_entry->common.flags & BATADV_TT_CLIENT_ISOLA &&
+ tt_global_entry->common.flags & BATADV_TT_CLIENT_ISOLA)
+ ret = true;
+
return ret;
}
--
1.8.4.3
next prev parent reply other threads:[~2013-11-16 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 11:03 [B.A.T.M.A.N.] [PATCHv3 0/5] Introducing the Extended-Isolation Antonio Quartulli
2013-11-16 11:03 ` [B.A.T.M.A.N.] [PATCHv3 1/6] batman-adv: add isolation_mark sysfs attribute Antonio Quartulli
2013-11-17 3:30 ` Marek Lindner
2013-11-16 11:03 ` [B.A.T.M.A.N.] [PATCHv3 2/6] batman-adv: mark a local client as isolated when needed Antonio Quartulli
2013-11-17 3:31 ` Marek Lindner
2013-11-16 11:03 ` [B.A.T.M.A.N.] [PATCHv3 3/6] batman-adv: print the new BATADV_TT_CLIENT_ISOLA flag Antonio Quartulli
2013-11-17 3:32 ` Marek Lindner
2013-11-16 11:03 ` Antonio Quartulli [this message]
2013-11-17 3:34 ` [B.A.T.M.A.N.] [PATCHv3 4/6] batman-adv: extend the ap_isolation mechanism Marek Lindner
2013-11-16 11:03 ` [B.A.T.M.A.N.] [PATCHv3 5/6] batman-adv: create helper function to get AP isolation status Antonio Quartulli
2013-11-17 3:35 ` Marek Lindner
2013-11-16 11:03 ` [B.A.T.M.A.N.] [PATCHv3 6/6] batman-adv: set the isolation mark in the skb if needed Antonio Quartulli
2013-11-17 3:37 ` Marek Lindner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1384599832-3959-5-git-send-email-antonio@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=antonio@open-mesh.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox