Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Lionel Litty <llitty@gmail.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Setting the interfaces in promiscuous mode
Date: Thu, 16 Sep 2004 14:06:15 -0700	[thread overview]
Message-ID: <20040916140615.3aee9580@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <5f3f2c61040916134370cc8897@mail.gmail.com>

On Thu, 16 Sep 2004 16:43:40 -0400
Lionel Litty <llitty@gmail.com> wrote:

> > promiscuous mode is tracked in the kernel with a counter, the kernel
> > won't change the actual hardware until the counter goes to zero. This is
> > why running something like tcpdump which changes interface to promiscuous mode
> > will have no effect on the bridge.  How did you
> > force the interface out of non-promiscious mode?  You may not changed anything.
> > 
> 
> I simply did "ifconfig eth0 -promisc" and "ifconfig tap0 -promisc".
> "ifconfig" then no longer indicates that the interfaces are in
> promiscuous mode. Are you saying that the output of ifconfig is not
> reliable and that the interfaces may in fact still be in promiscuous
> mode? This would make sense, but then how come the performance seems
> to be affected by the change?

Because when the stack thinks it is in promiscious mode then all the packets
have to be processed.


> > Also promiscuous on tap means nothing really since there is no hardware
> > filtering.
> 
> OK. I thought there might have been some software simulation of the
> promiscuous mode.
> 
> Thanks, Lionel.

      reply	other threads:[~2004-09-16 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 16:28 [Bridge] Setting the interfaces in promiscuous mode Lionel Litty
2004-09-16 18:09 ` Stephen Hemminger
2004-09-16 20:43   ` Lionel Litty
2004-09-16 21:06     ` 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=20040916140615.3aee9580@dell_ss3.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=bridge@lists.osdl.org \
    --cc=llitty@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