Open lazna opened 7 years ago
After years, today same thing happens (now on windows 10). Run command
packetsender.com -quw 1500 -B 192.168.1.236 255.255.255.255 10001 "01 00 00 00"
over wifi adapter Ralink RT3070 but PS do not print any output. Two replies come according to wireshark (see attached capture). When perfom same command via ethernet adapter Intel(R) PRO/1000 GT (just changed IP address) same two devices reply, and replies are correctly outputted by PS.
What am I doing wrong?
Routers will sometimes filter out broadcast packets.
If the devices are connected to the Ethernet, the WiFi router may be filtering broadcasts and not letting those packets on to the Ethernet. Do you get responses if you unicast directly to the devices?
if you check the attached .pcap file, you will see there is a received response, but is not displayed by packetsender.com for some reason
Your Wireshark capture looks OK to me. If it worked on Ethernet, it should work on WiFi. Packet Sender behaves the same on each. I see a packet going out port 60121 via broadcast and a response coming in to 60121.
The incoming with source address "0.0.0.0" is strange to me. It could mean some device is not configured. The one with the proper source address looks OK.
Couple things to try...
Finaly have time to perform more testing, and this issue is definitelly NOT binded only to wireless adapters.
Today I am tried several PCI and USB ethernet adapters with exact same command as used in previous posts, and it dow work only onone [Intel(R) PRO/1000 GT Desktop Adapter], on rest PCI and USB ethernet adapters I have tested it dows not work, but on ALL of them both wireshark and windump see received packets. So my result is, this packets are no properly "routed" to packetsender OR packetsender not "see" them for some reason, OR packetsender see packets but do not send it to STDOUT for some reason
Testing configuration of both testing machines:
desktop PC - Windows 10 / 64bit
1.\Device\NPF{E0CBD3A5-CD3F-411A-A5E0-865A577960CA} (Realtek PCIe GBE Family Controller) 2.\Device\NPF{1DC7EF94-0F1D-47B2-ABB7-6859539DF5B0} (Realtek USB NIC) 3.\Device\NPF{D1BBB1AD-02D7-4243-B04B-E8EAC9F7C607} (Intel(R) PRO/1000 GT Desktop Adapter) 4.\Device\NPF{8B5BFD9D-AEE3-4E39-BA4C-4832A59D77E8} (MS NDIS 6.0 LoopBack Driver) 5.\Device\NPF{9EAD5B24-45C8-43DD-B4F4-929698F007DD} (TAP-Windows Adapter V9) 6.\Device\NPF{33D2D49A-5D02-44A8-872B-AC37057B4ADE} (Oracle) 7.\Device\NPF_{E144A15D-DF70-48E4-9AA0-9EEC42B0CFF4} (Qualcomm Atheros Ar81xx series PCI-E Ethernet Controller)
tested USB adapters:
Corechip SR9900 Realtek RTL8153 AXIS AX88179 MosChip MCS7830
laptop Windows 10 - 64 bit
1.\Device\NPF{203C263C-5461-48AD-8C07-F48722910CC4} (Microsoft) 2.\Device\NPF{CAD330E0-E8E4-4AF7-A16C-478D9E41A724} (Intel(R) Ethernet Connection (3) I218-LM)
this "Microsoft" device is RTL8192EE wifi adapter
what can I do test more?
This is really strange. Packet Sender has no code that is specific to adapters. It simply requests a socket from the OS to bind and the OS forwards incoming packet data to the app.
For the adapters that failed, did you disable all other adapters except the one you are testing with?
Juste tested on laptop: all other interfaces disabled, only Intel(R) Ethernet Connection (3) I218-LM enabled. No response, but windump.exe started in another cmd window see incomming packets..
I tested wifi on my local set up, and it worked. (Yes, I know that does not help you). I used another Packet Sender GUI to send automatic {{DATE}} {{TIME}}
replies on UDP.
My adapter: Realtek RTL8852AE WiFi 6 802.11ax PCIe Adapter
Another idea:
There is a fairly recent Intel driver pack that mentions that card: https://www.intel.com/content/www/us/en/download/15084/intel-ethernet-adapter-complete-driver-pack.html
Try force-binding to "AnyIPv4". That would be -B 0.0.0.0
.
Here is my exact command that gave replies:
PS C:\Program Files\PacketSender> ./packetsender.com -quw 1500 -B 0.0.0.0 macwifi 56259 "01 00 00 00"
32 30 32 34 2D 30 39 2D 32 39 20 30 36 3A 32 35 3A 33 34 20 70 6D
PS C:\Program Files\PacketSender>
UPDATE: its look like it depend on libraries present. When 'packetsender.com' started from directory where all libraries reside, than work fine. When started from direcory where only commandline necessary libraries reside, than failed (on some interfaces).
UPDATE2: Just download last version, unpacked WHOLE zip file into a new location, start command, but same situation. On Intel works, but not on others... So I am out of ideas now...
It depend on PS version !! tested on: Intel, Realtek and Qualcomm PCI adapters
Packet Sender Version 8.6.5 / SSL:OpenSSL 1.1.1m 14 Dec 2021 / Commit: de4f214 works on all adapters
Packet Sender Version 8.6.5 / Commit: de4f214 work on Intel only
Interesting thing is, that FileCompare program judge both .exe files as identical:
FC: no differences encountered
Using following command, packets are not going into wireless interface. Partialy confirmed by wireshark. Could someone else confirm this, please? Using actual version of program.
packetsender -uw 5000 255.255.255.255 10001 "01 00 00 00"
Windows 7/ 64bit