public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: b.a.t.m.a.n@lists.open-mesh.org, sw@simonwunderlich.de
Cc: sven@narfation.org, hostap@lists.infradead.org
Subject: [B.A.T.M.A.N.] About making batman-adv mesh network invisible (by encrypting Beacon frame)
Date: Sat, 30 Mar 2019 11:50:27 +0800	[thread overview]
Message-ID: <a5949349-69fa-7ef5-fd78-88af76749e24@gmail.com> (raw)

Hi community,

We have batman-adv + OpenWRT + ath9k chip + ath9k driver reliably 
running for about 2 years. The biggest batman-adv mesh network is with 
100+ nodes.

As this is a closed network, we have a new requirement which is to make 
our batman-adv mesh network invisible, although the current SSID is just 
some meaningless characters.

One thought is hidden_ssid. But, it seems hidden_ssid is only supported 
for AP mode (not IBSS mode).

802.11w does not protect Beacon frame (because it is before four-ways 
handshake).

As this is a closed network, what about encrypting Beacon (maybe all 
management frames later) using a hard-coded key in wpa_supplicant?

Thanks for your help.

Xuebing Wang


             reply	other threads:[~2019-03-30  3:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30  3:50 Xuebing Wang [this message]
2019-04-01  9:59 ` [B.A.T.M.A.N.] About making batman-adv mesh network invisible (by encrypting Beacon frame) Simon Wunderlich
2019-04-06  6:06   ` [B.A.T.M.A.N.] About making batman-adv mesh network invisible Xuebing Wang
2019-04-08  8:10     ` Simon Wunderlich

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=a5949349-69fa-7ef5-fd78-88af76749e24@gmail.com \
    --to=xbing6@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=hostap@lists.infradead.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /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