All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <bradjc5@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>,
	Alexander Aring <alex.aring@gmail.com>,
	linux-wpan@vger.kernel.org
Cc: Brad Campbell <bradjc5@gmail.com>
Subject: [PATCH v2 0/1] ieee802154: cc2520: Check CRC & add promiscuous
Date: Wed, 23 Dec 2015 03:17:57 -0500	[thread overview]
Message-ID: <1450858678-59333-1-git-send-email-bradjc5@gmail.com> (raw)

I've updated the patch to provide monitors a method for determining if
the incoming packet had a valid CRC or not. This required adding promiscuous
mode, which is no longer the default.

Also, am I correct in noting that configuring a node interface to be in
promiscuous mode with something like:

ioctl(sockfd, SIOCGIFFLAGS, &ifopts);
ifopts.ifr_flags |= IFF_PROMISC;
ioctl(sockfd, SIOCSIFFLAGS, &ifopts);

is not currently supported? That's how I was testing at first and it
didn't seem to work.... Also, if a user does set an interface to
promiscuous using an ioctl, it seems like they would still want CRC
checking, which is not what would currently happen.


Changes since v1:
- Add support for promiscuous mode in cc2520
- Make frame filtering default
- Append CRC to incoming packets for monitors
- Actually calculate LQI

Brad Campbell (1):
  ieee802154: cc2520: Check CRC & add promiscuous

 drivers/net/ieee802154/cc2520.c | 128 ++++++++++++++++++++++++++++++++++------
 1 file changed, 111 insertions(+), 17 deletions(-)

--
2.6.3


             reply	other threads:[~2015-12-23  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23  8:17 Brad Campbell [this message]
2015-12-23  8:17 ` [PATCH v2 1/1] ieee802154: cc2520: Check CRC & add promiscuous Brad Campbell
2015-12-23  9:55   ` Alexander Aring
2015-12-23 21:27     ` Brad Campbell
2015-12-23 22:12       ` Alexander Aring
2015-12-23  9:22 ` [PATCH v2 0/1] " Alexander Aring
2015-12-23 21:33   ` Brad Campbell
2015-12-23 22:17     ` Alexander Aring

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=1450858678-59333-1-git-send-email-bradjc5@gmail.com \
    --to=bradjc5@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkabhadram@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.