From: Andreas Bardoutsos
Date: Thu, 04 May 2017 14:06:32 +0200
> Signed-off-by: Andreas Bardoutsos
First of all, the net-next tree is closed. You will need to resubmit
this when the net-next tree opens back up.
Second of all, your Subject line is malformed. Please format it like this:
Stefan Schmidt wrote:
> > The kernel tosses it because the RPL option/RFC says so
> > ('nodes that do not understand this option on a received
> > packet MUST discard the packet.').
>
> What we might need is a way to let the kernel know we have a RPL running with
> support for this option. Would
Hello.
On Thu, 2017-05-04 at 14:33, Florian Westphal wrote:
> Stefan Schmidt wrote:
> > ipv6: ext_header: add function to handle RPL option 0x63
>
> But its not handled, is it?
Its not handled in the kernel. The RPL daemon would run in userspace in this
case.
>From my understanding unstrung (o
Stefan Schmidt wrote:
> ipv6: ext_header: add function to handle RPL option 0x63
But its not handled, is it?
The kernel tosses it because the RPL option/RFC says so
('nodes that do not understand this option on a received
packet MUST discard the packet.').
Hello.
Lets do the review here on netdev.
Some general things first. You might want to use git send-email to make
sure the formatting does not get screwed up from your mailer. Another
thing to keep in mind is that net-next is closed right now (we are in
the 4.12 merge window right now) and Da
Signed-off-by: Andreas Bardoutsos
---
I have added a dump function(always return true) to recognise RPL
extension header(RFC6553)
Otherwise packet was dropped by kernel resulting in impossible
communication in RPL DAG's between
linux running border routers and devices in the graph,which may run
