From: "Jérôme LECOMTE" <lecomte@celar.fr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] IPv6 Bluez and Router Advertissement
Date: Mon, 02 Aug 2004 16:38:01 +0200 [thread overview]
Message-ID: <410E51C9.1020401@celar.fr> (raw)
Hi,
I'm having a problem concerning IPv6 autoconfiguration over Bluetooth
with Bluez Stack.
I set up a PICONET architecture like described in the "PAN How to". A
bridgde is taking care of all point-to-point bnep interfaces between the
master node and the slaves.
This master node acts like a router to provide access to a MANET 802.11b
network and implements IPV6 technology. Ipv4 configuration works well.
My aim is to provide IPv6 autoconfiguration to the BT slaves nodes.
I installed RADVD on the router in order to broadcast an ipv6 prefix to
BT nodes but they can't achieve to auto-configure.
The auto configuration is working through an ethernet link so the
problem comes from Bluetooth I think.
With a sniffer, router sollicication are going well from the slave to
the router but router advertisement (with ipv6 prefix) can't go through
Bluetooth links (sniffer on slaves shows that) and I don't understand why.
Experience about this would be welcome
Cheers.
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-08-02 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:38 Jérôme LECOMTE [this message]
2004-08-02 18:59 ` [Bluez-devel] IPv6 Bluez and Router Advertissement Marcel Holtmann
2004-08-02 20:26 ` David Woodhouse
2004-08-03 7:59 ` [Bluez-devel] BlueZ Disconnects Talbi
2004-08-03 8:28 ` David Woodhouse
2004-08-03 10:14 ` Talbi
2004-08-03 10:22 ` Till Harbaum
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=410E51C9.1020401@celar.fr \
--to=lecomte@celar.fr \
--cc=bluez-devel@lists.sourceforge.net \
/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