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
Subject: Re: ICMPv6 Redirects
Date: Mon, 29 Sep 2014 14:14:07 +0200 [thread overview]
Message-ID: <20140929121404.GA13564@omega> (raw)
In-Reply-To: <542949AE.30701@gmail.com>
On Mon, Sep 29, 2014 at 05:29:42PM +0530, Varka Bhadram wrote:
> On 09/29/2014 05:27 PM, Alexander Aring wrote:
> >On Mon, Sep 29, 2014 at 01:53:51PM +0200, Alexander Aring wrote:
> >>On Mon, Sep 29, 2014 at 05:15:51PM +0530, Varka Bhadram wrote:
> >>>On 09/29/2014 05:05 PM, Varka Bhadram wrote:
> >>>>On 09/29/2014 04:39 PM, Simon Vincent wrote:
> >>>>>On 29/09/14 11:58, Varka Bhadram wrote:
> >>>>>>Simon,
> >>>>>>
> >>>>>>On 09/29/2014 03:50 PM, 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.
> >>>>>>>
> >>>>>>I think we are not supposed to discard the packets like this. This will
> >>>>>>create the problems if routing enabled on the node.
> >>>>>>
> >>>>>>This not problem with the IEEE-802.15.4 driver or MAC implementation.
> >>>>>>
> >>>>>>These issues related to IPv6/ICMPv6 (ECHO request and ECHO reply).
> >>>>>>Here RFC2461/RFC4861 will
> >>>>>>come into picture. see:http://www.tahi.org/logo/phase2-core/result/Self_Test_4-0-3/freebsd71.router/nd.p2/
> >>>>>>
> >>>>>>Can you explain the setup..? What h/w you are using. How the network
> >>>>>>connected..?
> >>>>>>
> >>>>>I am running three nodes all directly connected to each other via
> >>>>>powerline networking running 802.15.4.
> >>>>>Therefore all nodes can see all the traffic. The nodes are setup with
> >>>>>ipv6 forwarding enabled.
> >>>>>If I ping node A from node B node C sends ICMP redirects.
> >>>>Please add:
> >>>>
> >>>>net.ipv6.conf.all.accept_redirects = 1
> >>>>net.ipv6.conf.all.send_redirects = 1
> >>>>
> >>>>to your//etc/sysctl.conf/ file.. It will disable redirect..
> >>>>
> >>>>Try this . I hope it will work.
> >>>Sorry for the wrong info...
> >>>
> >>>Set up accept_redirects/send_redirects to boolean value '0'
> >>>
> >>>echo 0 > /proc/sys/net/ipv6/conf/all/accept_redirects
> >>>
> >>don't know but I think this is only if we send or accept the route
> >>ICMPv6 messages. You only configure some filtering if you get these
> >>ICMPv6 messages or not, or if you send these ICMPv6 messages.
> >>
> >ah yes and this also make handling of these ICMPv6 messages or not.
> >
> >But Simon, did some dropping of skb's when these are PACKET_OTHERHOST,
> >and then it works for him. So this should some other issues, because
> >IPv6 should drop all sk_buff's which are PACKET_OTHERHOST.
> >
> >Which should be the same like dropping PACKET_OTHERHOST in mac802154.
> >
> >- Alex
>
> Please see:*http://lxr.free-electrons.com/source/net/ieee802154/af_ieee802154.c?v=2.6.34#L319*
>
> If packet type is PACKET_OTHERHOST its dropping, isn't it..?
Yep that's why dropping PACKET_OTHERHOST is handled by next layer. Not
mac802154. We have as next layer 6LoWPAN and af_ieee802154.
- Alex
next prev parent reply other threads:[~2014-09-29 12:14 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 [this message]
[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
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=20140929121404.GA13564@omega \
--to=alex.aring@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox