From: Simon Wunderlich <sw@simonwunderlich.de>
To: Xuebing Wang <xbing6@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org, sven@narfation.org
Subject: Re: [B.A.T.M.A.N.] About making batman-adv mesh network invisible
Date: Mon, 08 Apr 2019 10:10:27 +0200 [thread overview]
Message-ID: <1743828.EEJ9lJHY9g@prime> (raw)
In-Reply-To: <f2d6318d-a691-971e-9889-00867115303f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
Hi Xuebing,
I'm not aware of any "proprietary modulation", and I doubt it's possible - at
least not while using an AP at the same time. You can look into 5/10 MHz mode
or do other quirks if mesh is the only thing running on your module though.
Cheers,
Simon
On Saturday, April 6, 2019 2:06:55 PM CEST Xuebing Wang wrote:
> Hi Simon,
>
> Thanks a lot for your reply.
>
> With ath9k chip and ath9k driver, do you think it is possible to use
> "proprietary modulation" (slightly modified), so wireshark + wlan in
> monitor mode won't be able to detect wireless frames batman-adv network
> sends?
>
> Xuebing Wang
>
> On 2019/4/1 下午5:59, Simon Wunderlich wrote:
> > Hi Xuebing,
> >
> > at least for Ad-Hoc mode, you can't hide the SSID without changing the
> > kernel driver (mac80211). Encrypting the beacon doesn't help here, as the
> > SSID needs to be clear text eventually even if management frames get
> > encrypted.
> >
> > Cheers,
> >
> > Simon
> >
> > On Saturday, March 30, 2019 11:50:27 AM CEST Xuebing Wang wrote:
> >> 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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-08 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 3:50 [B.A.T.M.A.N.] About making batman-adv mesh network invisible (by encrypting Beacon frame) Xuebing Wang
2019-04-01 9:59 ` 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 [this message]
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=1743828.EEJ9lJHY9g@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.org \
--cc=xbing6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox