public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion•org>
To: Jukka Rissanen <jukka.rissanen@linux•intel.com>
Cc: netdev@vger•kernel.org
Subject: Re: Bluetooth 6LoWPAN and routing
Date: Thu, 24 Oct 2013 13:55:06 +0200	[thread overview]
Message-ID: <20131024115506.GD15744@order.stressinduktion.org> (raw)
In-Reply-To: <5268C214.2040307@linux.intel.com>

Hi!

On Thu, Oct 24, 2013 at 09:45:40AM +0300, Jukka Rissanen wrote:
> I have been prototyping with BT 6LoWPAN support (using this draft 
> http://tools.ietf.org/html/draft-ietf-6lowpan-btle-12 as a reference). I 
> sent first version yesterday to linux-bluetooth ml 
> http://thread.gmane.org/gmane.linux.bluez.kernel/39394
> 
> In this current prototype, after the BT connection is created, the code 
> set ups the virtual network interface, sets the IPv6 LL address for it 
> and creates an IPv6 route to peer (the BT 6LoWPAN connections are 
> point-to-point connections). I am using ip6_route_add() function from 
> net/ipv6/route.c file to do that. Unfortunately that function is not 
> exported so I GPL exported it for this prototype. Will this kind of 
> export accepted in upstream or should I figure out some other way to 
> create the desired route?

I am very confident that a patch making ip6_route_add gpl exported will be
accepted.

Greetings,

  Hannes

  reply	other threads:[~2013-10-24 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  6:45 Bluetooth 6LoWPAN and routing Jukka Rissanen
2013-10-24 11:55 ` Hannes Frederic Sowa [this message]
2013-10-24 12:25 ` Alexander Aring
2013-10-24 12:48   ` Jukka Rissanen
2013-11-04 21:46     ` Claudio Takahasi
2013-11-04 22:53       ` Alexander Aring
2013-11-05  8:36       ` Jukka Rissanen
2013-11-05  8:52         ` Alexander Aring
2013-11-05  8:55         ` Alexander Aring
2013-11-06 14:17           ` Claudio Takahasi

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=20131024115506.GD15744@order.stressinduktion.org \
    --to=hannes@stressinduktion$(echo .)org \
    --cc=jukka.rissanen@linux$(echo .)intel.com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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