From: Antonio Quartulli <antonio@meshcoding.com>
To: zaki.bm@gmail.com
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] IBSS key in batman-adv
Date: Wed, 17 Sep 2014 09:31:49 +0200 [thread overview]
Message-ID: <541938E5.8010701@meshcoding.com> (raw)
In-Reply-To: <CABQkniB+rTunkzArRbkfxp07zwj_CKP4_VysZkzUpzwPpGt2mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Hi Zaki,
On 17/09/14 09:04, Zaki wrote:
> Hi,
>
>
> I have a short question. I am using IBSS to create batman-adv mesh
> network. To secure the IBSS, i am using the IBSS key. I noticed that
> when i am on the mesh network, any device that is not having the key
> also can ping and iperf to me. I thought IBSS key is supposed to
> allow only legitimate device. Does anybody know where i do wrong
> here?.
This is more a linux-wireless question other than a batman-adv one.
batman-adv itself can't do much in this case since it does not know
anything about what is happening on the layers below.
In my opinion you are doing something wrong while setting up the
IBSS-RSN mechanism. (I guess you are using IBSS-RSN right ?)
A station not having the correct key should show up in the "station
dump" output of the other nodes with the "Authorized" attribute set to
"no". Is this the case? If not, then something i wrong with the
wpa_supplicant setup.
Cheers,
p.s. I'd recommend CC'ing the linux wireledd mailing list if you have
further questions.
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-17 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 7:04 [B.A.T.M.A.N.] IBSS key in batman-adv Zaki
2014-09-17 7:31 ` Antonio Quartulli [this message]
2014-09-17 7:43 ` Zaki
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=541938E5.8010701@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=zaki.bm@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.