Portál AbcLinuxu, 9. května 2024 23:35
Dale potrebujes konf. soubory, takze toto:
/etc/bluetooth/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 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 /usr/bin/bluepin;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "falcon";
# 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;
}
Muzes si zmenit nazev name a jinak vse muzes nechat ... Dale je dulezity ten PIN_HELPER .... Ten vypada takto: ...
/usr/bin/bluepin:
#!/bin/sh#!/bin/sh
echo "PIN:3333"
Kde cislo 3333 je cislo, ktere zadas, az se te Siemens bude ptat na PIN ... )) Dale potrebujes toto:
/etc/bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#
rfcomm0 {
# Automatically bind the device at startup
bind no;
# Bluetooth address of the device
device 00:60:57:5F:83:9B;
# RFCOMM channel for the connection
channel 1;
# Description of the connection
comment "falcon";
}
Tento soubor je nejdulezitejsi !!!!!
Zde nas zajima "device" to ID cislo co tam mam je je totiz ID moji nokie, ty tam musis dat svoje !!!! ID tveho siemens zjistis takto:
hcitool inq (musis to udelat jako root), me to napise toto:
Inquiring ...
00:60:57:5F:83:9B clock offset: 0x56de class: 0x520204
Kde, 00:60:57:5F:83:9B je ID moje nokie a patri do toho radku "device"
Tak ted uz jen staci nahodit pri bootu demony hci a rfcomm ...
V balicku bluez-utils v adr. script jsou dva soubory ... jeden na udelani zarizeni v /dev (jmenuje se createdev) a druhy patri do /etc/rc.d/ (jmenuje se bluetooth.init), takze ten bluetooth.init nakopirujes do /etc/rc.d/ a prejmenujes na rc.bluetooth a das spustitelna prava ...., pak do /etc/rc.d/rc.M napises toto:
# Start the bluetooth.
if [ -x /etc/rc.d/rc.bluetooth ]; then
. /etc/rc.d/rc.bluetooth start
fi
Tak a po reboot (nebo nahozeni /etc/rc.d/rc.bluetooth) se pripojis k telefonu:
hciconfig hci0 up
rfcomm connect rfcomm0
Siemens po tobe bude chtit PIN, zadas ten, co mas v bluepin (davali jsme 3333) a je to jsi pripojeny ... ))) pak staci jen spustit pppd, moje options vypada takto:
etc/ppp/options:
/dev/rfcomm0
115200
xonxoff # XON/XOFF
#crtscts # RTS/CTS
defaultroute
debug
#modem
#ipcp-accept-local
novj
novjccomp
nobsdcomp
noipx
lcp-echo-interval 10
passive noproxyarp
noauth
nodetach
usepeerdns
noipdefault
local
connect "/usr/sbin/chat -v -f /etc/ppp/chat-script -v -r /tmp/connect.rpt "
/etc/ppp/chat-script vypada takto:
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT ERROR
ABORT "NO ANSWER"
ABORT BUSY
""
ATZ
OK
ATX3
OK
AT+CGDCONT=1,"IP","internet" OK
ATD*99#
TIMEOUT 120
CONNECT
""
To je vse, MUSI to bezet .... )))
Prikaz "hcitool inq" skonci okamzite take s hlaseni, ze nic nenasel.
Nevedel by nekdo, co jsem zapomel? Kernel mam 2.6.8, ale stejneho vysledku dosahuju i v 2.6.5. Diky za jakykoliv napad, Standa p.s. v Knoppixu i WinXP vse bezi OK
V knoppixu je na to utilitka, ktera to udela celkem sama a rfcomm0 mi pripoji na /dev/modem. V Gentoo jsem nenasel /dev/bluetooth apod., takze ani nevim, za co pripadne BT "uchopit" a nalinkovat na /dev/modem.
Muj rfcomm.conf vypada presne tak, jak je popsano vyse v tom navodu. Bluetooth startuju rucne: /etc/init.d/bluetooth start, vzdy uspesne. Rfcomm, hci a hotplug startuji sami.
hcitool dev najde muj BT
hcitool inq najde muj BT telefon
hcitool hci0 up probehne ok atd....
bohuzel problem je, jen pri zadavani PINu :(, neni nejaka moznost, jak PIN vzdy rucne zadat jak na PC, tak na founu? Mozna se jen nekde neco spatne cte, ale fakt nevim.
Standa
#!/bin/sh
echo "PIN:3333"
musi byt SPUSTITELNY .... no a v hcid.conf, musi byt toto:
# PIN helper
pin_helper /usr/bin/bluepin;
}
a to proste MUSI chodit, kdyz se te to pta na pin, zadas 3333 /dev/bluetooth, je blbost, TY POTREBUJES jen te /dev/rfcomm0, a ten staci, muzes ho zlinkovat s /dev/modem ..... ) Nebo v /etc/ppp/options dej jako zarizeni prave: /dev/rfcomm0. Dale doufam, za jsi vubec vytvoril nove zarizeni rfcomm v dev ??? Pomoci jednoho skrptu z balicku bluez-utils ???? Pak taky zkontroluj, zda ma uzivatel dostatecny prava na prave to /dev/rfcomm0 (chmod 662 /dev/rfcomm0), nebo to radsi testni pod root ...
Tiskni Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.