From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Anycom USB-250 unseen by hcitool
Date: Sun, 18 May 2008 14:20:40 -0500 [thread overview]
Message-ID: <48308188.60706@earthlink.net> (raw)
In-Reply-To: <1210858654.7025.48.camel@violet.holtmann.net>
On 05/15/2008 08:37 AM, Marcel Holtmann wrote:
> Mumia wrote:
>>
>> Hmm, "hcitool" still doesn't see my bluetooth dongle:
>
> hciconfig hci0 up :)
>
> Regards
>
> Marcel
>
Thanks Marcel, but the network connection still doesn't work.
I do this:
hcid
sdpd
dund --nodetach --listen --persist --msdun call palm
And then I tell my Palm E2's bluetooth system to search for a network
connection, but the E2 never finds anything, and "dund" never displays
anything other than "dund[3984]: Bluetooth DUN daemon version 3.7."
How do I get dund communicating with my PDA?
Here is a listing of my /etc/bluetooth directory:
total 12
-rw-r--r-- 1 root root 1272 2008-05-17 07:18 hcid.conf
-rw-r--r-- 1 root root 5 2008-05-17 20:44 pin
-rw-r--r-- 1 root root 396 2008-05-17 07:49 rfcomm.conf
I've included below my hcid.conf, pin, and rfcomm.conf. Please help me
get my adapter working.
P.S.
I've been looking at this document:
http://howto.pilot-link.org/bluesync/ga.html . I follow the procedures,
but I never get any messages from dund like those in the document.
Below are the files in my /etc/bluetooth directory:
----------hcid.conf------------
#
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
# security user;
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "1234";
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
# name "%h-%d";
name "mybluetooth";
# Local device class
class 0x3e0100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
-------------pin------------
1234
------------rfccomm.conf-----------
#
# RFCOMM configuration file.
#
#rfcomm0 {
# # Automatically bind the device at startup
# bind no;
#
# # Bluetooth address of the device
# device 11:22:33:44:55:66;
#
# # RFCOMM channel for the connection
# channel 1;
#
# # Description of the connection
# comment "Example Bluetooth device";
#}
rfcomm0 {
bind yes;
device **:**:**:**:**:**;
channel 1;
comment "My Bluetooth device";
}
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-05-18 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 9:45 [Bluez-users] Anycom USB-250 unseen by hcitool Mumia W..
2008-05-15 9:41 ` Marcel Holtmann
2008-05-15 11:26 ` Mumia W..
2008-05-15 13:37 ` Marcel Holtmann
2008-05-15 22:00 ` Mumia W..
2008-05-18 2:05 ` Mumia W..
2008-05-18 19:20 ` Mumia W.. [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=48308188.60706@earthlink.net \
--to=paduille.4061.mumia.w+nospam@earthlink.net \
--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).