DokuWiki

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Zuletzt angesehen:
bluetooth-console

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung		Vorhergehende Überarbeitung
bluetooth-console [2020/09/13 10:46] – bennybluetooth-console [2024/06/09 10:29] (aktuell) – Externe Bearbeitung 127.0.0.1
Zeile 3: Zeile 3:
 In diesem Artikel sammle ich Informationen zur seriellen Konsolenverbindung via Bluetooth zum OmniSwitch mit AOS Release 8. In diesem Artikel sammle ich Informationen zur seriellen Konsolenverbindung via Bluetooth zum OmniSwitch mit AOS Release 8.
  
-<WRAP center round tip 60%> +===== Kompatible/Getestete USB-Bluetooth-Adapter ===== 
-Bisher ist das nur mein copy/paste Ziel hier, also nicht nicht final formatiert. +Die im hier Artikel aufgeführten Ausgaben/Details wurden mit diesen Produkten/Modellen/Versionen erreicht! 
-</WRAP>+Die AOS Release Notes enhalten jeweils aktuelle Angaben zu den unterstützen OmniSwitch Modellen.
  
-TODO/Notizen +^  Produkt/Modell  ^    AOS Version (Modell)    ^    USB-ID      ^     Link      ^       
-  * Kompatible Adapter: Ich habe einen Belkin "Mini Bluetooth v4.0 Adapter" mit ID: 050d:065a +|  Belkin USB BT 4.0  |    8.7.280.R01 (OS6465T-P12)   |    050d:065a    |     [[https://www.amazon.de/Belkin-Mini-Bluetooth-V4-0-Adapter-USB-2-0/dp/B009IQB3US/|Belkin USB BT v4.0 Adapter]]     |
-  * In AOS 8.7.280.R1 ist Bluetooth standardmäßig "admin enabled" +
-  * Prüfen welche Plattformen BT unterstützen und hier aufführen +
-  * OS6465T-P12 unterstützt es zumindest schon einmal, davon stammen die Ausgaben in diesem Artikel+
  
-<code> +===== Schritte am OmniSwitch =====
-VINDHYA #-> lsusb -vvv +
-Bus 001 Device 002: ID 050d:065a <-- der Bluetooth Adapter +
-Bus 001 Device 001: ID 1d6b:0002 +
-</code>+
  
-  * Kein Adapter eingesteckt+<WRAP center round info 60%> 
 +In AOS Release 8.7 ist Bluetooth bei eingestecktem USB-Bluetooth-Adapter standardmäßig aktiv! 
 +</WRAP> 
 + 
 +=== Kein USB-BT-Adapter eingesteckt ===
 <code> <code>
 Router-> show bluetooth status  Router-> show bluetooth status 
Zeile 29: Zeile 26:
  1          Not Present  1          Not Present
 </code> </code>
-  * USB-Adapter eingesteckt+=== USB-BT-Adapter wurde eingesteckt ===
 <code> <code>
 Router-> show bluetooth status  Router-> show bluetooth status 
Zeile 40: Zeile 37:
 </code> </code>
  
-  * Ausgabe in dmesg+===== Verbindung via Raspberry Pi ===== 
 +Dieser Abschnitt des Artikels widmet sich den Ausgaben und Möglichkeiten mit dem Raspberry Pi. 
 + 
 +==== Welche Bluetooth-Geräte gibt es im Umfeld? ==== 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo hcitool scan 
 +Scanning ... 
 + 00:02:72:XX:YY:ZZ Router 
 +</code> 
 + 
 +==== Mehr Informationen zum "Router" herausfinden ==== 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo hcitool info 00:02:72:XX:YY:ZZ 
 +Requesting information ... 
 + BD Address:  00:02:72:XX:YY:ZZ 
 + OUI Company: CC&C Technologies, Inc. (00-02-72) 
 + Device Name: Router 
 + LMP Version: 4.0 (0x6) LMP Subversion: 0x220e 
 + Manufacturer: Broadcom Corporation (15) 
 + Features page 0: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 
 + <3-slot packets> <5-slot packets> <encryption> <slot offset>  
 + <timing accuracy> <role switch> <sniff mode> <RSSI>  
 + <channel quality> <SCO link> <HV2 packets> <HV3 packets>  
 + <u-law log> <A-law log> <CVSD> <paging scheme> <power control>  
 + <transparent SCO> <broadcast encrypt> <EDR ACL 2 Mbps>  
 + <EDR ACL 3 Mbps> <enhanced iscan> <interlaced iscan>  
 + <interlaced pscan> <inquiry with RSSI> <extended SCO>  
 + <EV4 packets> <EV5 packets> <AFH cap. slave>  
 + <AFH class. slave> <LE support> <3-slot EDR ACL>  
 + <5-slot EDR ACL> <sniff subrating> <pause encryption>  
 + <AFH cap. master> <AFH class. master> <EDR eSCO 2 Mbps>  
 + <EDR eSCO 3 Mbps> <3-slot EDR eSCO> <extended inquiry>  
 + <LE and BR/EDR> <simple pairing> <encapsulated PDU>  
 + <err. data report> <non-flush flag> <LSTO> <inquiry TX power>  
 + <EPC> <extended features>  
 + Features page 1: 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
 +</code> 
 + 
 +==== Welche Dienste bietet der "Router" uns an? ==== 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo sdptool records 00:02:72:XX:YY:ZZ 
 +Service Name: Serial Port 
 +Service Description: COM Port 
 +Service Provider: BlueZ 
 +Service RecHandle: 0x10000 
 +Service Class ID List: 
 +  "Serial Port" (0x1101) 
 +Protocol Descriptor List: 
 +  "L2CAP" (0x0100) 
 +  "RFCOMM" (0x0003) 
 +    Channel: 1 
 +Language Base Attr List: 
 +  code_ISO639: 0x656e 
 +  encoding:    0x6a 
 +  base_offset: 0x100 
 +Profile Descriptor List: 
 +  "Serial Port" (0x1101) 
 +    Version: 0x0100 
 +</code> 
 + 
 +==== Drahtlose Konsolenverbindung herstellen ==== 
 + 
 +<WRAP center round tip 60%> 
 +Wichtig ist im **rfcomm**-Kommando die Angabe von **-r** für **RAW**, da man sonst jede Menge **^J**-Steuerzeichen im Konsolenprogramm sieht! 
 +</WRAP> 
 + 
 + 
 +=== Verbindung vom Raspberry Pi zum ALE OmniSwitch aufbauen === 
 +<code> 
 +pi@powerpi:~ $ sudo rfcomm -r connect hci0 00:02:72:XX:YY:ZZ 
 +Connected /dev/rfcomm0 to 00:02:72:XX:YY:ZZ on channel 1 
 +Press CTRL-C for hangup 
 +</code> 
 + 
 +=== Verbindung via "screen" === 
 + 
 +<WRAP center round tip 60%> 
 +**screen** beendet man mit der Tastenkombination STRG+A und danach "K", gefolgt von "Y"! 
 +</WRAP> 
 + 
 +<code> 
 +pi@powerpi:~ $ screen /dev/rfcomm0 
 +</code> 
 + 
 +=== Verbindung via "minicom" === 
 +<WRAP center round tip 60%> 
 +**minicom** beendet man mit der Tastenkombination STRG+A und danach "X", gefolgt von "Y"! 
 +</WRAP> 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo minicom -D /dev/rfcomm0 -s 
 +</code> 
 + 
 +==== Anzeige von Details zu aktuellen Verbindung(en) ==== 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo rfcomm -a 
 +rfcomm0: DC:A6:32:55:4E:63 -> 00:02:72:XX:YY:ZZ channel 1 connected [reuse-dlc release-on-hup tty-attached] 
 +</code> 
 + 
 +===== Weitere Details und Fehlerbehebung zum Raspberry Pi ===== 
 +Hier sammle ich mögliche Fehlermeldung(en) sowie die Lösung. 
 + 
 +==== "^J"-Zeichen in "screen"- und "minicom"-Konsole ==== 
 + 
 +Rollt im Terminal **^J** in **screen** oder **minicom**, dann fehlt der "-r"-Parameter für die **rfcomm**-Verbindung! 
 + 
 +=== Exemplarische Ausgabe === 
 +<code> 
 +^J 
 + 
 +^J^J 
 +^J 
 + 
 +^J^J 
 +^J 
 + 
 +^J^J 
 +^J 
 + 
 +^JLogin incorrect 
 +Router login: 
 +</code> 
 + 
 +=== Lösung: "-r" (RAW) bei rfcomm verwenden === 
 +<code> 
 +sudo rfcomm -r connect hci0 00:02:72:XX:YY:ZZ 
 +</code> 
 + 
 +==== Fehlermeldung: "Can't connect RFCOMM socket: Invalid exchange"  ==== 
 +Zu dieser Fehlermeldung kam es bei mir in unregelmäßigen Abständen. Es hat geholfen in diesem Fall die lokale Bluetooth-Konfiguration zurückzusetzen (das sollte man aber vor dem copy/paste genau prüfen, in meinem Fall hängt bei mir nichts essentielles am BT-Stack). Damit werden Einstellungen und der Cache gelöscht! 
 +<code> 
 +sudo rm -rf /var/lib/bluetooth/* 
 +</code> 
 + 
 +==== Fehlermeldung: "Can't create RFCOMM TTY: Address already in use"  ==== 
 +Diese Fehlermeldung hatte ich regelmäßig nachdem ich erst **screen** oder **minicom** beendet habe und danach die **rfcomm**-Verbindung. In diesem [[https://bugs.launchpad.net/raspbian/+bug/1428548|Bug-Report]] wird beschrieben dass das folgende Kommando helfen soll, was bei mir aber auch nicht immer geholfen hat. Wenn der Fehler sich mit dem folgenden Kommando nicht beheben lässt, kann man nach meiner Erfahrung den Raspberry Pi nur neustarten um das Problem zu beheben (gefällt mir nicht, aber eine andere Lösung habe ich derzeit nicht anzubieten). 
 +<code> 
 +sudo hciconfig hci0 reset 
 +</code> 
 + 
 +==== Analyse mit hcidump ==== 
 + 
 +<WRAP center round tip 60%> 
 +Eventuell muss das Programm **hcidump** noch installiert werden: sudo apt install bluez-hcidump 
 +</WRAP> 
 + 
 +<code> 
 +pi@powerpi:~ $ sudo hcidump -X 
 +HCI sniffer - Bluetooth packet analyzer ver 5.50 
 +device: hci0 snap_len: 1500 filter: 0xffffffff 
 +< HCI Command: Create Connection (0x01|0x0005) plen 13 
 +    bdaddr 00:02:72:XX:YY:ZZ ptype 0xcc18 rswitch 0x01 clkoffset 0x0000 
 +    Packet type: DM1 DM3 DM5 DH1 DH3 DH5  
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Create Connection (0x01|0x0005) status 0x00 ncmd 1 
 +> HCI Event: Connect Complete (0x03) plen 11 
 +    status 0x00 handle 11 bdaddr 00:02:72:XX:YY:ZZ type ACL encrypt 0x00 
 +< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 
 +    handle 11 
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1 
 +> HCI Event: Read Remote Supported Features (0x0b) plen 11 
 +    status 0x00 handle 11 
 +    Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 
 +< HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3 
 +    handle 11 page 1 
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1 
 +> HCI Event: Read Remote Extended Features (0x23) plen 13 
 +    status 0x00 handle 11 page 1 max 1 
 +    Features: 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
 +> HCI Event: Max Slots Change (0x1b) plen 3 
 +    handle 11 slots 5 
 +< HCI Command: Remote Name Request (0x01|0x0019) plen 10 
 +    bdaddr 00:02:72:XX:YY:ZZ mode 2 clkoffset 0x0000 
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1 
 +> HCI Event: Remote Name Req Complete (0x07) plen 255 
 +    status 0x00 bdaddr 00:02:72:XX:YY:ZZ name 'Router' 
 +< HCI Command: Authentication Requested (0x01|0x0011) plen 2 
 +    handle 11 
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Authentication Requested (0x01|0x0011) status 0x00 ncmd 1 
 +> HCI Event: Link Key Request (0x17) plen 6 
 +    bdaddr 00:02:72:XX:YY:ZZ 
 +< HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6 
 +    bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: Command Complete (0x0e) plen 10 
 +    Link Key Request Negative Reply (0x01|0x000c) ncmd 1 
 +    status 0x00 bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: IO Capability Request (0x31) plen 6 
 +    bdaddr 00:02:72:XX:YY:ZZ 
 +< HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9 
 +    bdaddr 00:02:72:XX:YY:ZZ capability 0x03 oob 0x00 auth 0x00 
 +    Capability: NoInputNoOutput (OOB data not present) 
 +    Authentication: No Bonding (No MITM Protection) 
 +> HCI Event: Command Complete (0x0e) plen 10 
 +    IO Capability Request Reply (0x01|0x002b) ncmd 1 
 +    status 0x00 bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: IO Capability Response (0x32) plen 9 
 +    bdaddr 00:02:72:XX:YY:ZZ capability 0x01 oob 0x00 auth 0x00 
 +    Capability: DisplayYesNo (OOB data not present) 
 +    Authentication: No Bonding (No MITM Protection) 
 +> HCI Event: User Confirmation Request (0x33) plen 10 
 +    bdaddr 00:02:72:XX:YY:ZZ passkey 276893 
 +< HCI Command: User Confirmation Request Reply (0x01|0x002c) plen 6 
 +    bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: Command Complete (0x0e) plen 10 
 +    User Confirmation Request Reply (0x01|0x002c) ncmd 1 
 +    status 0x00 bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: Simple Pairing Complete (0x36) plen 7 
 +    status 0x00 bdaddr 00:02:72:XX:YY:ZZ 
 +> HCI Event: Link Key Notification (0x18) plen 23 
 +    bdaddr 00:02:72:XX:YY:ZZ key E37EA95B6739FB99DFA63A45226CA428 type 4 
 +    Type: Unauthenticated Combination Key 
 +> HCI Event: Auth Complete (0x06) plen 3 
 +    status 0x00 handle 11 
 +< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3 
 +    handle 11 encrypt 0x01 
 +> HCI Event: Command Status (0x0f) plen 4 
 +    Set Connection Encryption (0x01|0x0013) status 0x00 ncmd 1 
 +> HCI Event: Encrypt Change (0x08) plen 4 
 +    status 0x00 handle 11 encrypt 0x01 
 +< HCI Command: Read Encryption Key Size (0x05|0x0008) plen 2 
 +  0000: 0b 00                                             .. 
 +> HCI Event: Command Complete (0x0e) plen 7 
 +    Read Encryption Key Size (0x05|0x0008) ncmd 1 
 +    0000: 00 0b 00 10                                       .... 
 +< ACL data: handle 11 flags 0x00 dlen 10 
 +    L2CAP(s): Info req: type 2 
 +> ACL data: handle 11 flags 0x02 dlen 16 
 +    L2CAP(s): Info rsp: type 2 result 0 
 +      Extended feature mask 0x00b8 
 +        Enhanced Retransmission mode 
 +        Streaming mode 
 +        FCS Option 
 +        Fixed Channels 
 +< ACL data: handle 11 flags 0x00 dlen 10 
 +    L2CAP(s): Info req: type 3 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 20 
 +    L2CAP(s): Info rsp: type 3 result 0 
 +      Fixed channel list 0x00000002 
 +        L2CAP Signalling Channel 
 +< ACL data: handle 11 flags 0x00 dlen 12 
 +    L2CAP(s): Connect req: psm 3 scid 0x0040 
 +> ACL data: handle 11 flags 0x02 dlen 16 
 +    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0 
 +      Connection pending - No further information available 
 +> ACL data: handle 11 flags 0x02 dlen 10 
 +    L2CAP(s): Info req: type 2 
 +< ACL data: handle 11 flags 0x00 dlen 16 
 +    L2CAP(s): Info rsp: type 2 result 0 
 +      Extended feature mask 0x02b8 
 +        Enhanced Retransmission mode 
 +        Streaming mode 
 +        FCS Option 
 +        Fixed Channels 
 +        Unicast Connectless Data Reception 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 10 
 +    L2CAP(s): Info req: type 3 
 +< ACL data: handle 11 flags 0x00 dlen 20 
 +    L2CAP(s): Info rsp: type 3 result 0 
 +      Fixed channel list 0x00000086 
 +        L2CAP Signalling Channel 
 +        L2CAP Connless 
 +> ACL data: handle 11 flags 0x02 dlen 16 
 +    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0 
 +      Connection successful 
 +< ACL data: handle 11 flags 0x00 dlen 27 
 +    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 15 
 +      MTU 1013  
 +      RFC 0x00 (Basic)  
 +> ACL data: handle 11 flags 0x02 dlen 27 
 +    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 15 
 +      MTU 1013  
 +      RFC 0x00 (Basic)  
 +< ACL data: handle 11 flags 0x00 dlen 18 
 +    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4 
 +      MTU 1013  
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 18 
 +    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4 
 +      MTU 1013  
 +< ACL data: handle 11 flags 0x00 dlen 8 
 +    L2CAP(d): cid 0x0040 len 4 [psm 3] 
 +      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c  
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 8 
 +    L2CAP(d): cid 0x0040 len 4 [psm 3] 
 +      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7  
 +< ACL data: handle 11 flags 0x00 dlen 18 
 +    L2CAP(d): cid 0x0040 len 14 [psm 3] 
 +      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 
 +      dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 
 +      frame_size 1008 max_retrans 0 credits 7 
 +> ACL data: handle 11 flags 0x02 dlen 18 
 +    L2CAP(d): cid 0x0040 len 14 [psm 3] 
 +      RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 
 +      dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 
 +      frame_size 1008 max_retrans 0 credits 7 
 +< ACL data: handle 11 flags 0x00 dlen 8 
 +    L2CAP(d): cid 0x0040 len 4 [psm 3] 
 +      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59  
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 8 
 +    L2CAP(d): cid 0x0040 len 4 [psm 3] 
 +      RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92  
 +< ACL data: handle 11 flags 0x00 dlen 12 
 +    L2CAP(d): cid 0x0040 len 8 [psm 3] 
 +      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 
 +      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0 
 +< ACL data: handle 11 flags 0x00 dlen 18 
 +    L2CAP(d): cid 0x0040 len 14 [psm 3] 
 +      RFCOMM(s): RPN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 
 +      dlci 2 br 3 db 3 sb 0 p 0 pt 0 xi 0 xo 0 
 +      rtri 0 rtro 0 rtci 0 rtco 0 xon 0 xoff 0 pm 0x0061 
 +> ACL data: handle 11 flags 0x02 dlen 12 
 +    L2CAP(d): cid 0x0040 len 8 [psm 3] 
 +      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 
 +      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0 
 +< ACL data: handle 11 flags 0x00 dlen 12 
 +    L2CAP(d): cid 0x0040 len 8 [psm 3] 
 +      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 
 +      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 12 
 +    L2CAP(d): cid 0x0040 len 8 [psm 3] 
 +      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 
 +      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0 
 +< ACL data: handle 11 flags 0x00 dlen 9 
 +    L2CAP(d): cid 0x0040 len 5 [psm 3] 
 +      RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33 
 +> ACL data: handle 11 flags 0x02 dlen 18 
 +    L2CAP(d): cid 0x0040 len 14 [psm 3] 
 +      RFCOMM(s): RPN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 
 +      dlci 2 br 3 db 0 sb 0 p 0 pt 0 xi 0 xo 0 
 +      rtri 0 rtro 0 rtci 0 rtco 0 xon 17 xoff 19 pm 0x3f1f 
 +> ACL data: handle 11 flags 0x02 dlen 9 
 +    L2CAP(d): cid 0x0040 len 5 [psm 3] 
 +      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 33 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 9 
 +    L2CAP(d): cid 0x0040 len 5 [psm 3] 
 +      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 1 fcs 0x40  
 +      0000: 0d                                                . 
 +> ACL data: handle 11 flags 0x02 dlen 10 
 +    L2CAP(d): cid 0x0040 len 6 [psm 3] 
 +      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 2 fcs 0x40  
 +      0000: 0d 0a                                             .. 
 +> ACL data: handle 11 flags 0x02 dlen 22 
 +    L2CAP(d): cid 0x0040 len 18 [psm 3] 
 +      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 14 fcs 0x40  
 +      0000: 52 6f 75 74 65 72 20 6c  6f 67 69 6e 3a 20        Router login:  
 +< ACL data: handle 11 flags 0x00 dlen 12 
 +    L2CAP(s): Connect req: psm 1 scid 0x0041 
 +> ACL data: handle 11 flags 0x02 dlen 16 
 +    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0 
 +      Connection successful 
 +< ACL data: handle 11 flags 0x00 dlen 23 
 +    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 11 
 +      RFC 0x00 (Basic)  
 +> ACL data: handle 11 flags 0x02 dlen 23 
 +    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 11 
 +      RFC 0x00 (Basic)  
 +< ACL data: handle 11 flags 0x00 dlen 18 
 +    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4 
 +      MTU 672  
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 18 
 +    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4 
 +      MTU 672  
 +< ACL data: handle 11 flags 0x00 dlen 24 
 +    L2CAP(d): cid 0x0041 len 20 [psm 1] 
 +        SDP SSA Req: tid 0x0 len 0xf 
 +          pat uuid-16 0x0100 (L2CAP) 
 +          max 65535 
 +          aid(s) 0x0000 - 0xffff 
 +          cont 00 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 2 
 +> ACL data: handle 11 flags 0x02 dlen 228 
 +    L2CAP(d): cid 0x0041 len 224 [psm 1] 
 +        SDP SSA Rsp: tid 0x0 len 0xdb 
 +          count 216 
 +          record #0 
 +              aid 0x0000 (SrvRecHndl) 
 +                 uint 0x10000 
 +              aid 0x0001 (SrvClassIDList) 
 +                 < uuid-16 0x1101 (SP) > 
 +              aid 0x0002 (SrvRecState) 
 +                 uint 0x1234 
 +              aid 0x0003 (SrvID) 
 +                 uuid-16 0x1101 (SP) 
 +              aid 0x0004 (ProtocolDescList) 
 +                 < < uuid-16 0x0100 (L2CAP) > < 
 +                 uuid-16 0x0003 (RFCOMM) uint 0x1 > > 
 +              aid 0x0005 (BrwGrpList) 
 +                 < uuid-16 0x1002 (PubBrwsGrp) > 
 +              aid 0x0006 (LangBaseAttrIDList) 
 +                 < uint 0x656e uint 0x6a uint 0x100 > 
 +              aid 0x0007 (SrvInfoTimeToLive) 
 +                 uint 0xffff 
 +              aid 0x0008 (SrvAvail) 
 +                 uint 0xff 
 +              aid 0x0009 (BTProfileDescList) 
 +                 < < uuid-16 0x1101 (SP) uint 0x100 > > 
 +              aid 0x000a (DocURL) 
 +                 url "http://www.bluez.org/" 
 +              aid 0x000b (ClientExeURL) 
 +                 url "http://www.bluez.org/" 
 +              aid 0x000c (IconURL) 
 +                 url "http://www.bluez.org/" 
 +              aid 0x0100 (SrvName) 
 +                 str "Serial Port" 
 +              aid 0x0101 (SrvDesc) 
 +                 str "COM Port" 
 +              aid 0x0102 (ProviderName) 
 +                 str "BlueZ" 
 +          cont 00 
 +< ACL data: handle 11 flags 0x00 dlen 24 
 +    L2CAP(d): cid 0x0041 len 20 [psm 1] 
 +        SDP SSA Req: tid 0x1 len 0xf 
 +          pat uuid-16 0x1200 (PNPInfo) 
 +          max 65535 
 +          aid(s) 0x0000 - 0xffff 
 +          cont 00 
 +> ACL data: handle 11 flags 0x02 dlen 14 
 +    L2CAP(d): cid 0x0041 len 10 [psm 1] 
 +        SDP SSA Rsp: tid 0x1 len 0x5 
 +          count 2 
 +          cont 00 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 1 
 +< ACL data: handle 11 flags 0x00 dlen 12 
 +    L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041 
 +> ACL data: handle 11 flags 0x02 dlen 12 
 +    L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041 
 +> HCI Event: Number of Completed Packets (0x13) plen 5 
 +    handle 11 packets 1 
 +... 
 +</code> 
 + 
 +===== Details zum OmniSwitch mit AOS R8 ===== 
 + 
 +==== Ausgabe von "lsusb" am OmniSwitch ==== 
 +<code> 
 +VINDHYA #-> lsusb -vvv 
 +Bus 001 Device 002: ID 050d:065a <-- der Belkin Bluetooth Adapter 
 +Bus 001 Device 001: ID 1d6b:0002 
 +</code> 
 + 
 +==== Ausgabe in "dmesg" am OmniSwitch ==== 
 +Meldungen in **dmesg** wenn der USB-BT-Adapter eingesteckt wird.
 <code> <code>
 +Router-> su
 +Entering maintenance shell. Type 'exit' when you are done.
 +VINDHYA #-> dmesg
 +...
 [1183593.649609] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 [1183593.649609] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
 [1183593.649651] orion-ehci f1050000.usb: GetStatus port:1 status 001803 0  ACK POWER sig=j CSC CONNECT [1183593.649651] orion-ehci f1050000.usb: GetStatus port:1 status 001803 0  ACK POWER sig=j CSC CONNECT
Zeile 54: Zeile 521:
 [1183593.965271] usb 1-1: Product: BCM20702A0 [1183593.965271] usb 1-1: Product: BCM20702A0
 [1183593.965282] usb 1-1: Manufacturer: Broadcom Corp [1183593.965282] usb 1-1: Manufacturer: Broadcom Corp
-[1183593.965294] usb 1-1: SerialNumber: 000272CD7347+[1183593.965294] usb 1-1: SerialNumber: 000272XXYYZZ
 [1183593.966059] usb 1-1: usb_probe_device [1183593.966059] usb 1-1: usb_probe_device
 [1183593.966078] usb 1-1: configuration #1 chosen from 1 choice [1183593.966078] usb 1-1: configuration #1 chosen from 1 choice
Zeile 74: Zeile 541:
 [1183595.268599] usb 1-1: link qh1-0e01/e57d5580 start 0 [1/2 us] [1183595.268599] usb 1-1: link qh1-0e01/e57d5580 start 0 [1/2 us]
 </code> </code>
-  * Herausfinden welches BT-Device im OmniSwitch verwendet wird+ 
 +==== Herausfinden welcher USB-BT-Adapter im OmniSwitch verwendet wird ==== 
 + 
 +Um herauszufinden welche MAC-Adresse der USB-BT-Adapter im OmniSwitch verwendet, werden folgende Kommandos verwendet. 
 <code> <code>
 +Router-> su
 +Entering maintenance shell. Type 'exit' when you are done.
 +VINDHYA #-> 
 VINDHYA #-> hcitool dev    VINDHYA #-> hcitool dev   
 Devices: Devices:
- hci0 00:02:72:CD:73:47+ hci0 00:02:72:XX:YY:ZZ
 VINDHYA #-> VINDHYA #->
- 
 </code> </code>
- 
bluetooth-console.1599993997.txt.gz · Zuletzt geändert: (Externe Bearbeitung)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki