From: Dave Henriksen <dhenriksen@optibrand.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Quality Bluetooth access point
Date: Tue, 15 Feb 2005 09:21:54 -0700 [thread overview]
Message-ID: <421221A2.9060009@optibrand.com> (raw)
Does anyone know of a really good class 1 Bluetooth network access point ?
We have had fairly good luck with the AXIS access point, but it is no
longer being supported by AXIS. Also, it tends to go brain dead once
in a while, and sometimes even requires a hard reboot.
The Anycom access point looks decent, but doesn't provide much in terms
of logging and debugging of connection problems. Also, there is no
way to tell it not to save the link keys. The firmware also has a bug
in it where if you tell it to automatically check for new firmware on
startup, it becomes a boat anchor and has to be sent back to the
manufacturer (This is documented on their website).
I have seen a few others out there, but I don't believe that any of them
are Class 1 devices.
I would prefer to buy a really good access point, but I am now
considering just building my own using BlueZ, and a very small single
board computer running a 300MHZ Geode processor.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-02-15 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 16:21 Dave Henriksen [this message]
2005-02-15 23:29 ` AW: [Bluez-users] Quality Bluetooth access point Florian Kimpenhaus
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 16:21 Dave Henriksen
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=421221A2.9060009@optibrand.com \
--to=dhenriksen@optibrand.com \
--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 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.