netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Miller <davem@davemloft.net>
Cc: martin.ferrari@gmail.com, netdev@vger.kernel.org
Subject: Re: IFF_PROMISC again
Date: Tue, 22 May 2007 17:22:54 -0700	[thread overview]
Message-ID: <4653895E.9000801@candelatech.com> (raw)
In-Reply-To: <20070522.171225.70219741.davem@davemloft.net>

David Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Tue, 22 May 2007 17:08:18 -0700
> 
>> Anyone know the reasoning for masking out the PROMISC flag
>> in dev_get_flags() ?
> 
> Because promiscuous status is a counter, not a binary
> on-off state.
> 
> You can't expect to just clear it and expect all the
> other promiscuous users to just "go away" and be ok
> with the device leaving promiscuous mode.

Yes, I understand why you wouldn't let a user set promisc in this
manner.

> Since you can't sanely "set" it, we don't provide it
> either.

What harm is there letting the user know if their hardware is PROMISC
or not, regardless of how it got that way?

Also, it seems you *can* at least turn it on with ifconfig, and
you can decrement at least once with ifconfig as well.  If nothing
else has promiscuity set, then this will indeed toggle the state, right?

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2007-05-23  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 18:36 IFF_PROMISC again Martín Ferrari
2007-05-23  0:08 ` Ben Greear
2007-05-23  0:12   ` David Miller
2007-05-23  0:22     ` Ben Greear [this message]
2007-05-26  6:42     ` Martín Ferrari
2007-05-26  6:28   ` Martín Ferrari
     [not found]     ` <20070527094923.3b4705b6@freepuppy>
2007-05-28  1:05       ` Martín Ferrari
     [not found]         ` <20070527235819.3695a2a1@freepuppy>
2007-05-28 22:07           ` Martín Ferrari

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=4653895E.9000801@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davem@davemloft.net \
    --cc=martin.ferrari@gmail.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).