From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Problem trying to connect second PANU
Date: Thu, 26 Jan 2006 11:10:57 +0100 [thread overview]
Message-ID: <1138270257.5901.22.camel@localhost> (raw)
In-Reply-To: <6916dea20601251400g667d13edm@mail.gmail.com>
Hi Alexandre,
> I have 3 laptop computers running Debian Linux Kernel 2.6 and Bluez.
> My scenario is as following:
>
> PANU1------->GN<----------PANU2
>
> I created the connection by:
>
> GN:
> pand --listen --role GN
> ifconfig bnep0 10.0.0.1
>
> PANU1
> pand --connect <GN_ADDR>
> ifconfig bnep0 10.0.0.2
>
> This connection went well and I "pinged" both each other.
>
> So, I tried to connect the PANU2 to GN by:
> pand --connect <GN_ADDR>
> ifconfig bnep0 10.0.0.3
>
> But I could not ping GN (10.0.0.1) anymore from PANU2.
> I tried to ifconfig bnep1 10.0.0.4 and ping it from PANU2 and no
> answer too.
> So the second slave to the piconet is no established (the first one is
> ok yet).
every PAN connection gets its own bnepX device and of you have multiple
on one side (like the GN) you need to bridge them.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-01-26 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 22:00 [Bluez-users] Problem trying to connect second PANU Alexandre Passito
2006-01-26 10:10 ` Marcel Holtmann [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=1138270257.5901.22.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).