netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Florian Fainelli <florian.fainelli@int-evry.fr>
Cc: netdev@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>
Subject: Re: Network activity LED trigger
Date: 03 Mar 2007 03:20:00 +0100	[thread overview]
Message-ID: <p73y7mfax0v.fsf@bingen.suse.de> (raw)
In-Reply-To: <200703012241.49165.florian.fainelli@int-evry.fr>

Florian Fainelli <florian.fainelli@int-evry.fr> writes:

> Hi All,
> 
> I have been talking a bit with Richard, who is the LED API maintainer, and a 
> LED trigger based on network activity would be something great.

You should be aware that normally the kernel doesn't see all packets
on a ethernet unless promiscuous mode is enabled (which it is normally 
not). That is because the hardware filters out all packets
not for this host. A software controlled LED wouldn't be equivalent
to the activity LEDs you normally have on network cards,
but only show local traffic.

That said if you want to get events for any in/outgoing packets
you can use the same hooks as PF_PACKET uses for sniffing;
using dev_add_pack with ETH_P_ALL.
That will get you all incoming and outgoing packets that 
are local.

And when someone runs tcpdump it will suddenly see all which
might be unexpected.

-Andi

  parent reply	other threads:[~2007-03-03  1:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 21:41 Network activity LED trigger Florian Fainelli
2007-03-02 12:58 ` Florian Fainelli
2007-03-02 14:11   ` jamal
2007-03-02 14:16     ` Florian Fainelli
2007-03-02 15:16       ` jamal
2007-03-02 16:03         ` Richard Purdie
2007-03-02 16:19           ` jamal
2007-05-10 19:21       ` Florian Fainelli
2007-05-10 20:27         ` jamal
2007-03-03  2:20 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-23 21:02 Florian Fainelli
2007-05-23 22:12 ` jamal

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=p73y7mfax0v.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=florian.fainelli@int-evry.fr \
    --cc=netdev@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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).