From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: 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.] 802.1x on top of batman-adv
Date: Sun, 4 Sep 2016 17:07:04 +0200 [thread overview]
Message-ID: <20160904150704.GE8395@otheros> (raw)
In-Reply-To: <CAA_JP8UttdRRoNtKGm6K4TdzZd5kyicd93szDV6S-m0_cstN9A@mail.gmail.com>
Hi Dan,
On Mon, Aug 08, 2016 at 11:30:54PM -0600, dan wrote:
> any consideration to making a batman-adv 802.1x interface? or anyone
> tested successfully using hostapd for wireless and wired clients and
> 802.1x?
>
> Combining batman-adv's layer2 mesh and some NAC would be very handy.
I'd be very very interested in something like this, too. Did you
have any success with hostapd yet?
What I'm interested in in particular: Moving the authenticator
from the wireless AP to some device somewhere else in the mesh.
The wireless AP should then choose to forward to an authenticator
based on the username provided (some authentication protocols
use non-anonymous usernames).
Regards, Linus
prev parent reply other threads:[~2016-09-04 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 5:30 [B.A.T.M.A.N.] 802.1x on top of batman-adv dan
2016-09-04 15:07 ` Linus Lüssing [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=20160904150704.GE8395@otheros \
--to=linus.luessing@c0d3.blue \
--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