I am developing an app that needs to connect to a BLE device, but i cannot find them to establish a connection and read the bluetooth device(yes, it's on) and i can connect it to another app only from this app . So, i try to sniff the bluetooth connection with bettercap in my kali linux running in WSL2, but when i try "ble.recon on" i get:
bettercap v2.28 (built for linux amd64 with go1.14.4) [type 'help' for a list of commands]
eth0: You don't have permission to capture on that device (socket: Operation not permitted)
And, if i try: "hciconfig" i get this issue
Can't open HCI socket.: Address family not supported by protocol
I think that i need to enable my hci socket or something. I need help.
I'm open to other ideas to establish a connection with tis device
Device: M1001 mopeka
App(working): gascheck
WSL2 isn’t allowed access to the network or bluetooth card directly. It is give an internal bridge IP address. From the outside, windows is making the network connections not kali. So, if you need to use this, maybe you can try dual boot.
Related
While I'm connecting to AS400 via PCOMM emulator, in network traffic(using Wireshark) telnet protocol from source(client) to destination(server AS400) is showing as Will TN3270E, while I'm using TN5250j Emulator to connect AS400 in telnet protocol is showing as Wont TN3270E
This is telling you that one client supports TN3270E (TN3270 Enhanced) and the other one does not. This is only relevant if you are doing something that requires the Enhanced standard (defined here from what I can tell: https://www.rfc-editor.org/rfc/rfc2355#section-7.2.2).
Is this possible? Plug STM board into local USB port, configure sharing device under Remote Desktop settings ("Local Resources > More"), then remote into PC running STM debug software and try to access board through ST-LINK via shared USB port? When I try, the software doesn't see the device.
This sort of thing works with other shared devices (drives, etc), but the STM software doesn't see this particular device. The device is visible locally before I open remote desktop.
Your apprach is wrong.
Connect the STM on the target machine. Run OpenOCD on that machine and connect via TCP from your local machine.
It is called remote debugging.
No USB magic
I develop on my tablet using android studio.
The tablet is connected to the computer by wifi using
adb connect <ip_andress>:5555
My application contains listeners for USB devices attached/detached.
But unfourtunately, when I connect/disconnect usb device to/from the tablet, the adb connection is getting killed, and I can no longer see the device under "adb devices".
It is not a adb-connection-by-wifi what gets killed. It is just that USB enumerations affect the sys.usb.* system properties which on many devices is causing restart of adbd regardless whether it's being used over USB or tcpip.
Do grep "stop adbd" /init*rc to see what I mean.
You could either comment out those stop adbd lines or just disconnect the USB cable before running your adb connect command.
I was never able to connect my cellphone with my computar through wi-fi.
I had already given up. I followed all the instructions and tips, and nothing worked.
Finally, I did what no one said to do.
I've connected the phone to the WiFi network provided by the cable modem itself and not to some (not all) additional networks that are included in the router.
At home I use one of these networks, because I use a Deco Tp-Link router, which propagates the signal to my entire house, but this network is NOT compatible with ADB. It does not identify it as belonging to the same network.
After this, I use the normal procedure described here.
a) Connect cellphone with a USB cable
b) Find the IP_Phone depends on system in the cell phone. Here I use Settings, About Phone, Status and IP address.
c) Run the following adb commands in Command Prompt (Windows) or Terminal (Linux), where IP_Phone is the IP above mentioned. Normally adb.exe is an executable stored in computer path. adb is already included in Android Studio package.
adb tcpip 5555
adb connect IP_Phone
d) Now disconnect USB cable and it's ready. The cellphone model continues to appear in the status line in the top of Android Studio.
-/-
The best wifi is that defined in Cable Modem. It, unlike an any account defined in my router, answers to a ping command.
ping IP_Phone
Disconnect the usb cable just before running adb connect <*ip_address_of_your_phone*>
I'm developing a client/server app for my Android phone (server side is Java based), and what I need now is an UDP connection over USB.
I tried adb forward, but it give me only TCP protocol with ridiculous latency (6~800ms), so I need UDP.
I found adb ppp command, but I'm not able to get it working on my Linux machine (updated Debian). I tried tons of examples found looking for adb ppp connection like
adb ppp "shell:pppd nodetach noauth noipdefault /dev/tty" nodetach noauth noipdefault notty 192.168.254.2:192.168.254.1
no lucky.
So, how can I give UDP power to my app?? There is some possibility without Android tether and root permission both side (Android and desktop)? I'm not interested in internet, BT or WiFi solutions. Even because Android tether request me desktop root permission to keep adb working, and I need TCP forward too.
Thank for help
The solution to your problem might be the USB Tethering. Go to the Settings then Wireless then Tethering & portable hotspot. after that turn on the USB Tethering. This option only shows when USB cable is plugged in your device and its connected to your notebook. Recent android versions place this option in Settings -> Tethering & portable hotspot..
I would like to ask about the way how to establish remote connection to Linux based embedded device in the field.
I have a small linux board I want to place in remote location. It has an internet access through ethernet. Than I have a Linux server with public IP to be able to tunnel connection.
And finally, I want to connect from my PC to this device.
I don't feel yet competent enough to code my own tcp sockets etc. to reroute the connection :) So what would be the easiest way to do that only with available linux tools? And BusyBox toolset on endpoints.
Thank's a lot!
I think that using OpenVPN would be a easy way to tunnel to the device. You can cross compile it and set it up as a client on the embedded device. Then you install it on your Linux box and set it up as a server.
Finally you install it on your work PC and set up as a client there.
It gives you a virtual network where all clients can talk to each other like they would be on a local network.