From: Alexander Aring <alex.aring@gmail.com>
To: Simon Vincent <simon.vincent@xsilon.com>
Cc: linux-wpan@vger.kernel.org, jukka.rissanen@linux.intel.com
Subject: Re: ICMPv6 Redirects
Date: Mon, 29 Sep 2014 13:37:09 +0200 [thread overview]
Message-ID: <20140929113708.GA12927@omega> (raw)
In-Reply-To: <20140929112357.GB18804@omega>
On Mon, Sep 29, 2014 at 01:23:57PM +0200, Alexander Aring wrote:
> On Mon, Sep 29, 2014 at 01:13:25PM +0200, Alexander Aring wrote:
> > Hi,
> >
> > On Mon, Sep 29, 2014 at 11:20:41AM +0100, Simon Vincent wrote:
> > > Currently there does not seem to be any filtering in the mac layer anyway.
> > > In wpan.c mac802154_subif_frame we check the pan id and dest address but we
> > > don't discard any packets. Should we be discarding packets at this point?
> > > For example packets of type PACKET_OTHERHOST.
> > >
> > > If I discard all PACKET_OTHERHOST in mac802154_subif_frame it solves my
> > > problem. I just don't know if this will effect anything else.
> > >
> >
> > Please see [0]. IPv6 will drop all PACKET_OTHERHOST. Maybe this
> > information is gone by some new skb_alloc's. Simon can you check this?
> >
> > Simple add some printk before deliver to IPv6 layer.
> >
> > And no, we don't make this at mac802154 layer.
> >
>
> Maybe we should do this in 6LoWPAN Layer. Means a:
>
> if (skb->pkt_type == PACKET_OTHERHOST) {
> kfree_skb(skb);
> return NET_RX_DROP;
> }
>
> in lowpan_rcv [0] function. I am not 100% sure right now, but I think it's
> better than we don't parse any OTHERHOST frames in 6LoWPAN packet layer.
>
> But this is another issue...
>
> - Alex
>
> [0] http://lxr.free-electrons.com/source/net/ieee802154/6lowpan_rtnl.c#L456
cc: jukka.rissanen@linux.intel.com
here, this could be also useful for bluetooth 6LoWPAN.
- Alex
prev parent reply other threads:[~2014-09-29 11:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:16 ICMPv6 Redirects Simon Vincent
2014-09-26 15:35 ` Alexander Aring
2014-09-26 16:26 ` Simon Vincent
2014-09-27 1:42 ` Alexander Aring
2014-09-29 10:20 ` Simon Vincent
2014-09-29 10:58 ` Varka Bhadram
2014-09-29 11:09 ` Simon Vincent
[not found] ` <5429441C.5000302@gmail.com>
[not found] ` <5429466F.4080506@gmail.com>
2014-09-29 11:53 ` Alexander Aring
2014-09-29 11:57 ` Alexander Aring
[not found] ` <542949AE.30701@gmail.com>
2014-09-29 12:14 ` Alexander Aring
[not found] ` <54294BE7.7040501@gmail.com>
2014-09-29 12:14 ` Alexander Aring
[not found] ` <54295556.3030800@xsilon.com>
2014-09-29 13:12 ` Alexander Aring
2014-09-29 13:30 ` Alexander Aring
2014-09-29 13:33 ` Simon Vincent
2014-09-29 13:38 ` Alexander Aring
2014-09-29 13:41 ` Alexander Aring
2014-09-29 13:51 ` Simon Vincent
2014-09-29 13:54 ` Varka Bhadram
2014-09-29 14:12 ` Simon Vincent
2014-09-29 13:58 ` Alexander Aring
2014-09-29 14:05 ` Varka Bhadram
2014-09-29 14:12 ` Alexander Aring
2014-09-29 14:15 ` Varka Bhadram
2014-09-29 14:19 ` Alexander Aring
2014-09-29 14:12 ` Simon Vincent
2014-09-29 14:17 ` Alexander Aring
2014-09-29 14:39 ` Alexander Aring
2014-09-29 14:51 ` Alexander Aring
2014-09-29 16:41 ` Alexander Aring
2014-09-30 8:34 ` Simon Vincent
2014-09-30 8:34 ` Varka Bhadram
2014-09-30 8:39 ` Alexander Aring
2014-09-30 8:46 ` Varka Bhadram
2014-09-30 8:53 ` Alexander Aring
2014-09-30 9:10 ` Varka Bhadram
2014-09-30 9:25 ` Alexander Aring
2014-09-30 9:35 ` Varka Bhadram
2014-09-30 9:43 ` Alexander Aring
[not found] ` <542A7D85.8050608@gmail.com>
2014-09-30 10:03 ` Alexander Aring
2014-09-30 10:55 ` Jukka Rissanen
2014-09-30 11:13 ` Alexander Aring
2014-09-30 11:35 ` Alexander Aring
2014-09-29 11:13 ` Alexander Aring
2014-09-29 11:23 ` Alexander Aring
2014-09-29 11:37 ` Alexander Aring [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=20140929113708.GA12927@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-wpan@vger.kernel.org \
--cc=simon.vincent@xsilon.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