Portál AbcLinuxu, 27. července 2025 09:24
Mam mobil Samsung E250,adapter Bluetooth Sweex USB, Mandrivu 2009, program Gome Bluetooth pise ze nemuze pripojit obex, at pry pouziji jiny prohlizec. Rad bych to propojil jako modem pres Twist Internet. Mohl by nekdo poradit? V priloze jsou vypisy co jsem byl schopen ziskat. Diky.
Dal jsem yes, hcid, ale stejne pise:
Bluetooth Applet 0.28
A Bluetooth manager for the GNOME desktop
Could not display "obex://[00:23:39:BD:3D:3E]/".
Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Please select another viewer and try again.
zkusil jsem a vysledek:
[root@P3 log]# sdptool browse 00:23:39:BD:3D:3E
Failed to connect to SDP server on 00:23:39:BD:3D:3E: Connection timed out
Program KBlueMon vypise na obrazovku - viz priloha
Program KBluetooth vypise na obrazovku - viz priloha
ale pripojit ne a ne.
Já nechápu, o co se snažíš. Pokud to chceš použít na internet, nemusí tě OBEX vůbec zajímat. Spíš si nastav rfcomm a pppd.
Mě OBEX skutečně nezajímá, zkouším prostě připojit telefon přes bluetooth, jednak na GPRS, pokud by šel i přenos souborů, tím lépe, nejsem však schopen se ničím připojit, ani Wammu se nepřipojí, hcitool info telefon najde, ale hcitool auth už píše HCI authentication request failed: Input/output error. Nejsem schopen zjistit číslo kanálu, sdptool search DUN --bdaddr 00:23:39:BD:3D:3E mi píše Failed to connect to SDP server on 00:23:39:BD:3D:3E: Connection timed out.
A co sdptool browse 00:23:39:BD:3D:3E? A taky bych zkusil spustit démony jak hcid, sdpd a podobně.
Tak se mi konecne podarilo rozchodit sdptool, tentokrat na CD Live SUSE 11,
sdptool browse 00:23:39:BD:3D:3E vypise:
linux:/home/linux # sdptool browse 00:23:39:BD:3D:3E
Browsing 00:23:39:BD:3D:3E ...
Service Name: WBTEXT
Service RecHandle: 0x10000
Service Class ID List:
UUID 128: db1d8f12-95f3-402c-9b97-bc504c9a55c4
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x1cdb1d8f-1295-f340-2c9b-97bc504c9a55)
Version: 0x0100
Service Name: Serial Port
Service RecHandle: 0x10001
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Profile Descriptor List:
"Serial Port" (0x1101)
Version: 0x0100
Service Name: Dial-up Networking
Service RecHandle: 0x10002
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Voice GW
Service RecHandle: 0x10003
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Voice GW
Service RecHandle: 0x10004
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
Service Name: Advanced audio source
Service RecHandle: 0x10005
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100
Service RecHandle: 0x10006
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: OBEX File Transfer
Service RecHandle: 0x10007
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 6
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Service Name: Object Push
Service RecHandle: 0x10008
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 7
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
umi to i
linux:/home/linux # l2ping 00:23:39:BD:3D:3E
Ping: 00:23:39:BD:3D:3E from 00:11:67:B6:57:5F (data size 44) ...
44 bytes from 00:23:39:BD:3D:3E id 0 time 14.39ms
44 bytes from 00:23:39:BD:3D:3E id 1 time 46.33ms
44 bytes from 00:23:39:BD:3D:3E id 2 time 43.95ms
44 bytes from 00:23:39:BD:3D:3E id 3 time 44.91ms
44 bytes from 00:23:39:BD:3D:3E id 4 time 42.93ms
44 bytes from 00:23:39:BD:3D:3E id 5 time 46.93ms
^C6 sent, 6 received, 0% loss
ale kdyz zkousim rfcomm:
linux:/home/linux # rfcomm connect rfcomm0 00:23:39:BD:3D:3E
Can't connect RFCOMM socket: Connection refused
Proc refused, to se mi zatim nepodarilo zjistit.
Telefon mi najde bluetooth adapter vcetne hostname, chce na me pin, ale nespoji se.
To jsem samozrejme upravil, v rfcomm.conf je channel 3,
[root@P3 bluetooth]# rfcomm connect /dev/rfcomm0 00:23:39:BD:3D:3E
Can't connect RFCOMM socket: Operation now in progress
Ale sériák máš na kanálu 2, zkus ten
Tiskni
Sdílej:
ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.