You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
[bluetooth]# scan on
[bluetooth]# menu scan
[bluetooth]# clear
[bluetooth]# transport le
[bluetooth]# back
then you get list of BLE devices around. Same what kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
[bluetooth]# pair <BTADDR>
[bluetooth]# menu gatt
[bluetooth]# list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.
It gives you the general message that you cannot connect to the device.
You can't connect to regular Bluetooth device if it is already connected or paired. BLE devices are different. In the list they show you could be only devices that ready for connection. Because to find BLE devices that already connected you need special hardware they clearly don't have.
Why don't you try it in a crowded place to confirm it instead of just theorizing?
I did. And it's exactly how BLE work.
"Why can't a doctor understand bluetooth like a 10-year-old kid?" Perhaps because they don't have the experience in this field.
Well, they somehow installed and get kismet working. It is a sophisticated tool, mostly for hackers, and they have enough expirience to use it. But somehow they don't have a clue what BLE is, what they see in kismet and how to connect and get info from BLE devices.
It's impossible.
You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
[bluetooth]# scan on
[bluetooth]# menu scan
[bluetooth]# clear
[bluetooth]# transport le
[bluetooth]# back
then you get list of BLE devices around. Same what kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
[bluetooth]# menu gatt
[bluetooth]# list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.
It gives you the general message that you cannot connect to the device.
You can't connect to regular Bluetooth device if it is already connected or paired. BLE devices are different. In the list they show you could be only devices that ready for connection. Because to find BLE devices that already connected you need special hardware they clearly don't have.
Why don't you try it in a crowded place to confirm it instead of just theorizing?
I did. And it's exactly how BLE work.
"Why can't a doctor understand bluetooth like a 10-year-old kid?" Perhaps because they don't have the experience in this field.
Well, they somehow installed and get kismet working. It is a sophisticated tool, mostly for hackers, and they have enough expirience to use it. But somehow they don't have a clue what BLE is, what they see in kismet and how to connect and get info from BLE devices.
It's impossible.
You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
[bluetooth]# scan on
[bluetooth]# menu scan
[bluetooth]# clear
[bluetooth]# transport le
[bluetooth]# back
then you get list of BLE devices around. Same that kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
[bluetooth]# menu gatt
[bluetooth]# list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.
It gives you the general message that you cannot connect to the device.
You can't connect to regular Bluetooth device if it is already connected or paired. BLE devices are different. In the list they show you could be only devices that ready for connection. Because to find BLE devices that already connected you need special hardware they clearly don't have.
Why don't you try it in a crowded place to confirm it instead of just theorizing?
I did. And it's exactly how BLE work.
"Why can't a doctor understand bluetooth like a 10-year-old kid?" Perhaps because they don't have the experience in this field.
Well, they somehow installed and get kismet working. It is a sophisticated tool, mostly for hackers, and they have enough expirience to use it. But somehow they don't have a clue what BLE is, what they see in kismet and how to connect and get info from BLE devices.
It's impossible.
You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
[bluetooth]# scan on
[bluetooth]# menu scan
[bluetooth]# clear
[bluetooth]# transport le
[bluetooth]# back
then you get list of BLE devices around. Same that kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
[bluetooth]# menu gatt
[bluetooth]# list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.
It gives you the general message that you cannot connect to the device.
You can't connect to regular Bluetooth device if it is already connected or paired. BLE devices are different. In the list they show you could be only devices that ready for connection. Because to find BLE devices that already connected you need special hardware.
Why don't you try it in a crowded place to confirm it instead of just theorizing?
I did. And it's exactly how BLE work.
"Why can't a doctor understand bluetooth like a 10-year-old kid?" Perhaps because they don't have the experience in this field.
Well, they somehow installed and get kismet working. It is a sophisticated tool, mostly for hackers, and they have enough expirience to use it. But somehow they don't have a clue what BLE is, what they see in kismet and how to connect and get info from BLE devices.
It's impossible.
You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
[bluetooth]# scan on
[bluetooth]# menu scan
[bluetooth]# clear
[bluetooth]# transport le
[bluetooth]# back
then you get list of BLE devices around. Same that kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
menu gatt
list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.
It gives you the general message that you cannot connect to the device.
You can't connect to regular Bluetooth device if it is already connected or paired. BLE devices are different. In the list they show you could be only devices that ready for connection. Because to find BLE devices that already connected you need special hardware.
Why don't you try it in a crowded place to confirm it instead of just theorizing?
I did. And it's exactly how BLE work.
"Why can't a doctor understand bluetooth like a 10-year-old kid?" Perhaps because they don't have the experience in this field.
Well, they somehow installed and get kismet working. It is a sophisticated tool, mostly for hackers, and they have enough expirience to use it. But somehow they don't have a clue what BLE is, what they see in kismet and how to connect and get info from BLE devices.
It's impossible.
You cannot connect to the bluetooth MAC addresses. I think you assumed something here...
That exactly how BLE devices work.
They run kismet. Kismet is only for linux. They don't have special hardware BLE sniffers like Ubertooth or nRF24 based one to sniff on established connections. So they have a list of BLE adresses retirned by linux HCI. This list contains addresses of devices you could connect to. If you see address in that list - you could connect to it.
Say, you use bluetoothctl (basic linux BT utility, you have it out of the box on any popular linux distribution).
you do
scan on
menu scan
clear
transport le
back
then you get list of BLE devices around. Same that kismet will show.
[NEW] Device <BTADDR>
Then you coudl do with <BTADDR> in form of 00:11:22:33:44:55
menu gatt
list-attributes <BTADDR>
You will get a list of attributes BLE device expose and some additional info like device class, name and so on.
somehting like that:
Device <BTADDR> (public)
Name: <somename>
Alias: <somealias>
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (3dda0001-957f-7d4a-34a6-74696673696d)
Then you could read and even write some attributes. Every attribute have UUID, most UUIDs are predefined and you could find how to read and interpret them.
And so on.