From: paras kumar <paras.kumar@samsung.com>
To: 'Alexander Aring' <alex.aring@gmail.com>,
jukka.rissanen@linux.intel.com, marcel@holtmann.org,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org
Subject: RE: Re: Query regarding IPv6 address configuration for BT 6lowpan device/interface
Date: Fri, 26 Jun 2015 10:28:10 +0530 [thread overview]
Message-ID: <022a01d0afcc$b9936c20$2cba4460$@samsung.com> (raw)
In-Reply-To:
Hello All,
Please help me to understand below queries.
Thanks & Regards,
Paras
-----Original Message-----
From: paras kumar [mailto:paras.kumar@samsung.com]=20
Sent: Tuesday, June 23, 2015 12:30 PM
To: 'Alexander Aring'
Cc: 'jukka.rissanen@linux.intel.com'; 'marcel@holtmann.org'; =
'johan.hedberg@gmail.com'; 'linux-bluetooth@vger.kernel.org'
Subject: RE: Re: Query regarding IPv6 address configuration for BT =
6lowpan device/interface
Hi Alexander,
Thanks for the code modification you suggested [0].
After adding the case "ARPHRD_6LOWPAN" to generate IPv6 address for BT =
interface in IPv6 module (addrconf.c file); kernel gets panicked.
May be this panic is because I am using below setup.
1. Linux kernel version 3.10.
2. For 6LoWPAN: Just copied [net/6lowpan/.. and net/Bluetooth/.. code =
from 4.0.2 kernel] Rest all other modules are older only (kernel 3.10) =
including IPV6 module.
As I cannot upgrade whole kernel due to official reasons, please =
suggest which other dependent modules I need to upgrade mandatorily to =
get the 6LoWPAN working for Bluetooth properly.
Or
Above setup is sufficient to work for Bluetooth 6lowpan?=20
Please let me know your suggestions.
=20
Thanking you,
Paras
[0] http://lxr.free-electrons.com/source/net/ipv6/addrconf.c#L1912
-----Original Message-----
From: Alexander Aring [mailto:alex.aring@gmail.com]
Sent: Thursday, June 18, 2015 2:39 PM
To: paras kumar
Cc: jukka.rissanen@linux.intel.com; marcel@holtmann.org; =
johan.hedberg@gmail.com; linux-bluetooth@vger.kernel.org
Subject: Re: Re: Query regarding IPv6 address configuration for BT =
6lowpan device/interface
Hi,
On Thu, Jun 18, 2015 at 02:26:40PM +0530, paras kumar wrote:
> Thanks Jukka for your response,
>=20
> I could see link -local address is configured for other interfaces=20
> like wlan0, but not getting configured for bt0 interface when it is =
UP.
> I am using linux kernel version 3.10 and had merged net/6lowpan/..=20
> changes from linux kernel version 4.0.2 as below to enable bt 6lowpan.
>=20
> I am able to make the BT interface UP after merging 6lowpan changes as =
> above. But not able to get the ipv6 address for the same.
>=20
> Please tell me if any system environment or module dependencies are =
there?
>
Maybe you missing [0].
- Alex
[0] http://lxr.free-electrons.com/source/net/ipv6/addrconf.c#L1912
next prev parent reply other threads:[~2015-06-26 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 8:56 Re: Query regarding IPv6 address configuration for BT 6lowpan device/interface paras kumar
2015-06-18 9:08 ` Alexander Aring
2015-06-23 7:00 ` paras kumar
2015-06-26 4:58 ` paras kumar [this message]
2015-06-26 7:53 ` 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='022a01d0afcc$b9936c20$2cba4460$@samsung.com' \
--to=paras.kumar@samsung.com \
--cc=alex.aring@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).