From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] pan link quality
Date: Tue, 10 Jan 2006 17:07:36 +0100 [thread overview]
Message-ID: <1136909256.7200.6.camel@localhost.localdomain> (raw)
In-Reply-To: <43C29249.3020008@fillibach.de>
Hi Kosta,
> I am currently playing around in setting up IP ad-hoc networks using
> bluez. olsr-over-bluetooth works, and `pand -Q` is a nice thing :)
>
> The bad stuff is that inquiry & connecting can take some time, but its
> hard to really do something against that. (I have a few hacks in mind,
> but they wont scale)
>
> What would be really nice is some link quality metric. On my mobile
> device `hcitool lq` always returns 255 (Even if the link goes bad and
> the other side sees it). But I have one metric in mind: the interface
> gets destroyed if a certain number of packets are not acknowledged by
> the receiver. Is there some way (other than writing a script that
> listens to hcidump) to measure this? `ifconfig bnep0` shows errors:0
> and dropped:0 until it is detroyed. I am not a kernel hacker, i looked
> around a bit in the bluez module, the library and pand, but couldnt
> really find anything...
>
> Do you have any hints? Is there any "unacknoledged packets" metric
> accessible from userland? Where is the code that destroys the bnep
> interface after x packets?
the link quality is vendor specific and we really only know how CSR
implemented it. The RSSI might be another indicator, but I assume some
chip manufacturers did a bad implementation. What chips are you using?
> PS: Are you interesed in a "zeroconf ip" patch for pand?
Go ahead and post the patch to the mailing list. We will review it.
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-10 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 16:41 [Bluez-devel] pan link quality Kosta Welke
2006-01-10 16:07 ` Marcel Holtmann [this message]
2006-01-18 0:58 ` [Bluez-devel] patch: custom devup script Kosta Welke
2006-01-18 13:20 ` Marcel Holtmann
2006-01-18 17:37 ` Claudio Takahasi
2006-01-18 22:18 ` Konstantin 'Kosta' Welke
2006-01-19 0:51 ` Marcel Holtmann
2006-01-19 1:55 ` Kosta Welk
2006-01-20 1:43 ` Marcel Holtmann
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=1136909256.7200.6.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.