From: "Harald Meier" <meh1@rts.at>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] PAND and RFCOMM simultaneously
Date: Tue, 30 Mar 2004 08:25:37 +0200 [thread overview]
Message-ID: <003201c4161f$d37a2050$4000fe0a@rtsviec64> (raw)
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Hi Marcel,
All PCs in the PAN are equipped with G+W Instruments PICO Bluetooth PCI
Adapter (class 1).
The Serial Devices are equipped with G+W Instruments Blue Serial Bluetooth
Adapter.
(www.gw-instruments.de)
The init script does the following:
insmod bt-pci.o # the driver for the BT-PCI card
insmod bluez.o
insmod hci_usb.o
insmod l2cap.o
insmod bnep.o
insmod rfcomm.o
hcid
sdpd
pand --listen --role NAP #
on the NAP
pand --connect <BT-address-of-NAP> --persist # in the PANU
The hcid.conf is attached (same for NAP and PANU).
When this is running, I get a "Function not implemented" if I try to connect
to
a different NAP (using pand) or if I try to establish a RFCOMM connection.
Is the sequence of loading the modules ok?
Thanks for help!
Harald.
[-- Attachment #2: hcid.conf --]
[-- Type: application/octet-stream, Size: 1491 bytes --]
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.3 2002/07/18 18:12:46 maxk Exp $
#
# 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 auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
#pin_helper /bin/bluepin;
pin_helper /etc/bluetooth/bluepin;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h (%d)";
# Local device class
class 0x100;
# 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,master;
#
lm accept,master;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
#
#lp hold,sniff;
#
lp rswitch,hold,sniff,park;
# Authentication and Encryption
auth enable;
encrypt enable;
}
next reply other threads:[~2004-03-30 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 6:25 Harald Meier [this message]
2004-03-30 7:14 ` [Bluez-users] PAND and RFCOMM simultaneously Marcel Holtmann
2004-03-30 13:31 ` Harald Meier
2004-04-01 6:13 ` Harald Meier
2004-04-01 7:09 ` Marcel Holtmann
2004-04-01 8:17 ` Harald Meier
2004-04-01 8:31 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 12:55 Harald Meier
2004-03-25 23:38 ` 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='003201c4161f$d37a2050$4000fe0a@rtsviec64' \
--to=meh1@rts.at \
--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