public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zbigniew Diaczyszyn \(gmx\)" <z.dia@gmx.de>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm socket message: function not implemented
Date: Tue, 24 Feb 2004 00:39:37 +0100	[thread overview]
Message-ID: <000b01c3fa66$4dccee30$4c4bb850@ULLA> (raw)
In-Reply-To: 1077486947.2832.20.camel@pegasus

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

Hi Marcel,

> I am pretty sure that you have the same PIN helper problem like many
> others do.

So I will not lose hope to get working the BT interface ...

Attached you will find the binary file in hcidump.log and the files for the pinhelper-stuff: bluepin is just an cat-command.

Thanks in advance!

Zbigniew




[-- Attachment #2: hcidump.log --]
[-- Type: application/octet-stream, Size: 95 bytes --]

[-- Attachment #3: bluepin --]
[-- Type: application/octet-stream, Size: 37 bytes --]

#!/bin/bash
cat /etc/bluetooth/pin

[-- Attachment #4: hcid.conf --]
[-- Type: application/octet-stream, Size: 1447 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;
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "Typhoon (%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;

	# 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 hold,sniff,park;

	# Authentication and Encryption
	#auth enable;
	#encrypt enable;
}

  reply	other threads:[~2004-02-23 23:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 21:45 [Bluez-users] rfcomm: permission denied Zbigniew Diaczyszyn (gmx)
2004-02-15 14:34 ` Marcel Holtmann
     [not found]   ` <000b01c3f599$04aaf520$de4bb850@ULLA>
2004-02-17 22:54     ` [Bluez-users] hcidump, was: " Marcel Holtmann
     [not found]       ` <003b01c3f65e$371ef400$dc4db850@ULLA>
2004-02-18 23:31         ` Marcel Holtmann
2004-02-21 22:24           ` Zbigniew Diaczyszyn (gmx)
2004-02-22  2:09             ` Marcel Holtmann
2004-02-22 21:54               ` [Bluez-users] rfcomm socket message: function not implemented Zbigniew Diaczyszyn (gmx)
2004-02-22 21:55                 ` Marcel Holtmann
2004-02-23 23:39                   ` Zbigniew Diaczyszyn (gmx) [this message]
2004-02-23 23:59                     ` Marcel Holtmann
     [not found]                       ` <006c01c3fb29$c2b4b700$184cb850@ULLA>
2004-02-24 23:03                         ` Marcel Holtmann
2004-02-25 21:53                           ` Zbigniew Diaczyszyn (gmx)

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='000b01c3fa66$4dccee30$4c4bb850@ULLA' \
    --to=z.dia@gmx.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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