From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: paras kumar <paras.kumar@samsung.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org
Subject: Re: Query regarding IPv6 address configuration for BT 6lowpan device/interface
Date: Thu, 18 Jun 2015 09:55:00 +0300 [thread overview]
Message-ID: <1434610500.2794.24.camel@linux.intel.com> (raw)
In-Reply-To: <037201d0a986$4f1ff2b0$ed5fd810$@samsung.com>
Hi Paras,
On to, 2015-06-18 at 10:48 +0530, paras kumar wrote:
> Hi Marcel,
>
> Could you please provide me answer of below query.
>
> When BT 6Lowpan interface is UP after BLE & IPSP L2CAP connection (Say for
> example "bt0").
> I don't find interface is configured with inet6/IPv6 address which should be
> configured during device initialization.
>
> The snapshot is here:
> sh-4.1# ifconfig
> bt0: flags=4177<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
> unspec 00-02-FA-FF-FE-72-2D-17-00-00-00-00-00-00-00-00 txqueuelen 0
> (UNSPEC)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> My query is how IPv6 address is configured or generated for BT interface? Or
> the process which should be followed to get IPv6 address configured ?
>
> Please give me some pointer in kernel code also, where to check?
>
> Thanks & regards,
> Paras
>
>
See net/bluetooth/6lowpan.c:chan_ready_cb(), it will setup the netdev
and take the interface up. This should then cause the interface to have
the IPv6 link local address properly setup by the kernel.
Cheers,
Jukka
prev parent reply other threads:[~2015-06-18 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 5:18 Query regarding IPv6 address configuration for BT 6lowpan device/interface paras kumar
2015-06-18 6:55 ` Jukka Rissanen [this message]
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=1434610500.2794.24.camel@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=paras.kumar@samsung.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;
as well as URLs for NNTP newsgroup(s).