From: Florian Echtler <echtler@fs.tum.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] l2ping working only in one direction
Date: Wed, 6 Jul 2005 09:45:49 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0507060942310.7056@block.bubble> (raw)
In-Reply-To: <Pine.LNX.4.63.0507060905270.7056@block.bubble>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Okay, sorry to have bothered you, just solved the problem myself:
> Here's hciconfig -a from the desktop:
> Link mode: ACCEPT MASTER
> And this is hciconfig -a from the router, where l2ping fails:
> Link mode: ACCEPT MASTER
Obviously, not both sides can be master, so I changed the router
to use only "lm accept;", and now everything works, including
the headset (which I consider somewhat interesting, because it
worked with the desktop machine, which used "lm accept,master;"
all the time).
How is it determined which side will become master when both try
to be? Just timing issues?
Yours, Florian
- --
Preserve wildlife - pickle a squirrel today!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCy4wv7CzyshGvatgRAqndAJ0T4D3yROQd/U1UOhtTWZNGWhNZbACggcBw
sZXWqUganh0UWc/SNCGuBuc=
=HgXx
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-07-06 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 7:15 [Bluez-users] l2ping working only in one direction Florian Echtler
2005-07-06 7:45 ` Florian Echtler [this message]
2005-07-06 8:26 ` Marcel Holtmann
2005-07-08 5:54 ` Abraham HAouchar
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=Pine.LNX.4.63.0507060942310.7056@block.bubble \
--to=echtler@fs.tum.de \
--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