Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Port Security
Date: Fri, 10 Sep 2010 08:11:28 -0700	[thread overview]
Message-ID: <20100910081128.0d582d9f@nehalam> (raw)
In-Reply-To: <AANLkTikWFR0xWPTALmVJz_Yt8J+2OCTXSHrE8syQH8pQ@mail.gmail.com>

On Fri, 10 Sep 2010 00:01:57 -0400
Ryan Whelan <rcwhelan@gmail.com> wrote:

> I am developing an appliance that will use bridging to create a little
> integrated switch.  We need to ensure that only approved devices are allowed
> to connect to the switch; are there any mechanisms to enforce security
> within the linux bridge? What would be the recommended method if not?
> ebtables?

no. it is not designed to do this.

> I did a search and found nothing- please point me in the right direction if
> I missed something!

802.1X?


-- 

      reply	other threads:[~2010-09-10 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  4:01 [Bridge] Port Security Ryan Whelan
2010-09-10 15:11 ` Stephen Hemminger [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=20100910081128.0d582d9f@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=rcwhelan@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