All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Townsend <martin.townsend@xsilon.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Promiscuous patches
Date: Thu, 18 Sep 2014 09:57:09 +0100	[thread overview]
Message-ID: <541A9E65.3090300@xsilon.com> (raw)
In-Reply-To: <20140914234551.GA7009@omega>

Hi Alex,

Thanks for the links, I needed this to get wireshark working again as we now have address filtering support in HW.

The code looks good and using the net device op for detecting a rx flag change looks good to me.  A couple of thoughts.
1) Maybe you could remove the HW flag for promiscuous? just let the driver implement the set_promiscuous_mode driver ops function if the HW supports it or leave it NULL if it doesn't
2) I had to implement the ndo_change_rx_flags net device ops in wpan.c not monitor.c.  For remote wireshark captures that we do we use tcpdump -i wpan0 on the boards.  Are we doing something wrong here? Your code seems to suggest that we should bring up a separate monitor interface?

- Martin.



On 15/09/14 00:45, Alexander Aring wrote:
> Hi Martin,
>
> On Fri, Sep 12, 2014 at 02:14:01PM +0100, Martin Townsend wrote:
>> Hi Alex,
>>
>> You sent me a patch not long ago to allow automatic setting of promiscous mode.  I seem to have lost this patch, could you resend as I want to look into it.
>>
> some of my old branch [0].
>
> btw.
>
> I added to the rework now the promiscous mode and decided to not enable
> this mode while setting promiscous mode flag.
>
> It's now setted by doing a ifup of a monitor interface. See [1].
>
> Maybe you will change it like this (it's better) but there are so many
> issue to think about (Disable promiscous if netif on non MONITOR
> interfaces etc...).
>
> And also you can't have NODE and MONITOR running because it's phy mac
> sublayer attribute.
>
> I will cc linux-wpan, hope it's okay.
>
> In next days I will draw some fancy architecture graphic about the
> rework. To understand what I really did there. (I also have no idea
> about to implement it 100% right, I do experiments and then think about
> it "how we can do that in a better way") and very important in a way
> where we could easily handle/add _new features_.
>
> If anybody has questions about this implementation I would be very happy
> to answer them. :-)
>
> - Alex
>
> [0] https://github.com/linux-wpan/linux-wpan-next/commits/alex/wip
> [1] https://github.com/linux-wpan/linux-wpan-next/blob/d5d62172f69ecf8db4dce77e790403e532687662/net/mac802154/iface.c#L42


  parent reply	other threads:[~2014-09-18  8:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5412F199.7010803@xsilon.com>
2014-09-14 23:45 ` Promiscuous patches Alexander Aring
2014-09-14 23:56   ` Alexander Aring
2014-09-15 11:56     ` Alexander Aring
2014-09-15 12:01       ` Alexander Aring
2014-09-18  8:57   ` Martin Townsend [this message]
2014-09-18  9:41     ` Alexander Aring
2014-09-18 10:04       ` Martin Townsend
2014-09-18 10:43         ` Alexander Aring
2014-09-18 12:00           ` Martin Townsend
2014-09-18 12:21             ` Alexander Aring
2014-09-18 12:30               ` Alexander Aring
2014-09-18 12:44                 ` Alexander Aring
2014-09-18 13:25                   ` Martin Townsend
2014-09-18 13:34                     ` Alexander Aring
2014-09-18 13:42                       ` Alexander Aring
2014-09-18 14:36                         ` Martin Townsend
2014-09-18 16:05                           ` Alexander Aring
2014-09-18 16:54                             ` Martin Townsend
2014-09-18 17:07                               ` Alexander Aring
2014-09-18 17:54                                 ` Alexander Aring
2014-09-18 17:56                                   ` Alexander Aring
2014-09-18 18:30                                     ` Martin Townsend
2014-09-18 18:53                                       ` Alexander Aring
2014-09-18 20:34                                         ` Alexander Aring
2014-09-19 10:11                                           ` Alexander Aring
2014-09-20  7:03                                             ` Martin Townsend
2014-09-21 10:06                                               ` 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=541A9E65.3090300@xsilon.com \
    --to=martin.townsend@xsilon.com \
    --cc=alex.aring@gmail.com \
    --cc=linux-wpan@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 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.