In diesem Artikel sammle ich Informationen zur seriellen Konsolenverbindung via Bluetooth zum OmniSwitch mit AOS Release 8.

TODO/Notizen

• Kompatible Adapter: Ich habe einen Belkin „Mini Bluetooth v4.0 Adapter“ mit ID: 050d:065a
• 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

VINDHYA #-> lsusb -vvv
Bus 001 Device 002: ID 050d:065a <-- der Bluetooth Adapter
Bus 001 Device 001: ID 1d6b:0002

• Kein Adapter eingesteckt

Router-> show bluetooth status 
Admin Status       : enabled,
Transmit Power     : low,

Chassis      Operational Status
----------+---------------------------
 1          Not Present

• USB-Adapter eingesteckt

Router-> show bluetooth status 
Admin Status       : enabled,
Transmit Power     : low,

Chassis      Operational Status
----------+---------------------------
 1          Connection Inactive

• Ausgabe in dmesg

[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.649682] hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
[1183593.803626] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
[1183593.923627] usb 1-1: new full-speed USB device number 2 using orion-ehci
[1183593.961247] usb 1-1: skipped 1 descriptor after interface
[1183593.962243] usb 1-1: default language 0x0409
[1183593.965227] usb 1-1: udev 2, busnum 1, minor = 1
[1183593.965245] usb 1-1: New USB device found, idVendor=050d, idProduct=065a
[1183593.965259] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1183593.965271] usb 1-1: Product: BCM20702A0
[1183593.965282] usb 1-1: Manufacturer: Broadcom Corp
[1183593.965294] usb 1-1: SerialNumber: 000272CD7347
[1183593.966059] usb 1-1: usb_probe_device
[1183593.966078] usb 1-1: configuration #1 chosen from 1 choice
[1183593.967259] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[1183593.984447] btusb 1-1:1.0: usb_probe_interface
[1183593.984469] btusb 1-1:1.0: usb_probe_interface - got id
[1183593.987218] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[1183593.991362] usb 1-1: adding 1-1:1.2 (config #1, interface 2)
[1183593.995804] usb 1-1: link qh1-0e01/e57d5580 start 0 [1/2 us]
[1183594.009198] btusb 1-1:1.2: usb_probe_interface
[1183594.009224] btusb 1-1:1.2: usb_probe_interface - got id
[1183594.009371] usb 1-1: adding 1-1:1.3 (config #1, interface 3)
[1183594.014470] btusb 1-1:1.3: usb_probe_interface
[1183594.014494] btusb 1-1:1.3: usb_probe_interface - got id
[1183594.014653] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[1183595.188361] usb 1-1: unlink qh1-0e01/e57d5580 start 0 [1/2 us]
[1183595.189628] usb usb1: clear tt buffer port 1, a2 ep2 t04048d80
[1183595.268571] orion-ehci f1050000.usb: reused qh e57d5580 schedule
[1183595.268599] usb 1-1: link qh1-0e01/e57d5580 start 0 [1/2 us]

• Herausfinden welches BT-Device im OmniSwitch verwendet wird

VINDHYA #-> hcitool dev   
Devices:
	hci0	00:02:72:CD:73:47
VINDHYA #->

pi@powerpi:~ $ sudo hcitool scan
Scanning ...
	00:02:72:CD:73:47	Router

pi@powerpi:~ $ sudo hcitool info 00:02:72:CD:73:47
Requesting information ...
	BD Address:  00:02:72:CD:73:47
	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

pi@powerpi:~ $ sudo sdptool records 00:02:72:CD:73:47
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

pi@powerpi:~ $ sudo rfcomm connect hci0 00:02:72:CD:73:47
Connected /dev/rfcomm0 to 00:02:72:CD:73:47 on channel 1
Press CTRL-C for hangup

pi@powerpi:~ $ screen /dev/rfcomm0

Ich nutze Raspbian Buster und die Installation erfolgt wie folgt:

sudo apt install build-essential ruby-dev libpcap-dev
sudo gem install bettercap
pi@powerpi:~ $ sudo bettercap -h
 _          _   _
| |__   ___| |_| |_ ___ _ __ ___ __ _ _ __
| '_ \ / _ \ __| __/ _ \ '__/ __/ _` | '_ \
| |_) |  __/ |_| ||  __/ | | (_| (_| | |_) |
|_.__/ \___|\__|\__\___|_|  \___\__,_| .__/
                                     |_| v1.6.2
http://bettercap.org/
...