You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been testing the ESP32-S2 firmware for the USB to UDP bridge functionality for Proxmark3 as described in this repository. Despite following the instructions, I am unable to establish a connection between the Proxmark3 client and the Proxmark3 device. Here are the steps I followed and the issues I encountered:
I successfully connected to the Wi-Fi hotspot created by the ESP32-S2 and was able to ping 192.168.4.1. An nmap scan confirmed that the UDP port 18888 on 192.168.4.1 is open.
However, when I attempt to connect to the Proxmark3 using the command pm3 -p udp:192.168.4.1:18888, the connection fails. The log output is as follows:
pm3 -p udp:192.168.4.1:18888
[=] Session log xxx.txt
[+] loaded `xxx/preferences.json`
[+] Using UART port udp:192.168.4.1:18888
[!!] 🚨 ERROR: cannot communicate with the Proxmark3
Both the client and device are running Proxmark3 firmware version v4.18589 - Aurora.
I would appreciate any guidance or suggestions to troubleshoot and resolve this issue. Thank you in advance for your help!
The text was updated successfully, but these errors were encountered:
I tested the TCP version, but had no luck. It appears that port 18888 is closed.
$ nmap 192.168.4.1 -p 18888
Starting Nmap 7.70 ( https://nmap.org ) at 2024-07-16 16:06 CST
Nmap scan report for 192.168.4.1
Host is up (0.018s latency).
PORT STATE SERVICE
18888/tcp closed apc-necmp
Nmap done: 1 IP address (1 host up) scanned in 13.08 seconds
Hello,
I have been testing the ESP32-S2 firmware for the USB to UDP bridge functionality for Proxmark3 as described in this repository. Despite following the instructions, I am unable to establish a connection between the Proxmark3 client and the Proxmark3 device. Here are the steps I followed and the issues I encountered:
pm3 -p udp:192.168.4.1:18888
, the connection fails. The log output is as follows:I would appreciate any guidance or suggestions to troubleshoot and resolve this issue. Thank you in advance for your help!
The text was updated successfully, but these errors were encountered: