From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: Simon Vincent <simon.vincent@xsilon.com>,
linux-wpan@vger.kernel.org, jukka.rissanen@linux.intel.com
Subject: Re: ICMPv6 Redirects
Date: Tue, 30 Sep 2014 10:53:49 +0200 [thread overview]
Message-ID: <20140930085347.GA28060@omega> (raw)
In-Reply-To: <542A6DF6.809@gmail.com>
Hi Varka,
On Tue, Sep 30, 2014 at 02:16:46PM +0530, Varka Bhadram wrote:
> Alex,
>
> On 09/30/2014 02:09 PM, Alexander Aring wrote:
> >On Tue, Sep 30, 2014 at 09:34:29AM +0100, Simon Vincent wrote:
> >>I can confirm that this fixes the problem. I will create some patches when I
> >>get a chance.
> >>Thanks
> >>
> >This should make trouble on phy's which have no address filter...
>
> I didnt get what do you mean by this..?
>
The mac802154 address filter sets PACKET_BROADCAST, PACKET_HOST and
PACKET_OTHERHOST. When you have an address filter on PHY, then
PACKET_OTHERHOST should never happen (on good phy's).
So you always set PACKET_HOST xor PACKET_BROADCAST.
> >But when IPv6 Layer look on PACKET_BROADCAST then this is also another
> >bug...
> >
> >I did a grep:
> >
> >grep -r "PACKET_BROADCAST" net/IPv6
> >
> >matches on:
> >
> >net/ipv6/mcast.c: skb->pkt_type != PACKET_BROADCAST)
>
6LoWPAN layer always override the mac802154 parse value to PACKET_HOST.
Now I want to check if IPv6 Layer ever evaluate this value to
PACKET_BROADCAST and yes it seems so. So there is some other bug which
nobody detected.
Ok?
- Alex
next prev parent reply other threads:[~2014-09-30 8:53 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 [this message]
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
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=20140930085347.GA28060@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-wpan@vger.kernel.org \
--cc=simon.vincent@xsilon.com \
--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.