Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: David Palma <david.palma@ntnu.no>
Cc: linux-wpan - ML <linux-wpan@vger.kernel.org>
Subject: Re: Bridging a lowpan interface
Date: Sat, 11 Nov 2017 13:53:27 -0500	[thread overview]
Message-ID: <22033.1510426407@obiwan.sandelman.ca> (raw)
In-Reply-To: <D59C859A-19A4-4898-A7E1-19C09BEBEA4E@ntnu.no>

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]


David Palma <david.palma@ntnu.no> wrote:
    > I'm all for routing and starting with RPL is fine. However, the idea
    > was also to enable traffic differentiation based on flows (the SDN
    > part), without breaking them, and not only based on IP
    > addresses. That's why I mentioned that I used routing and ip6tables.

I don't understand what the problem is.
What would you do with bridged interfaces in an SDN?
What kind of breaking are you speaking of?

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-11-11 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 12:25 Bridging a lowpan interface David Palma
2017-11-10 17:46 ` Michael Richardson
2017-11-10 23:32   ` David Palma
2017-11-11 18:53     ` Michael Richardson [this message]
2017-11-11 22:59       ` David Palma
2017-11-12  0:06         ` Alexander Aring
2017-11-12  0:09           ` Alexander Aring
2017-11-12 11:56             ` David Palma

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=22033.1510426407@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=david.palma@ntnu.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox