Replies: 1 comment
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I’m working on a project that involves packet injection on a Raspberry Pi 3B. My goal is to send custom packets and verify that they are received by another Raspberry Pi running in monitor mode. However, while I can see the packets being transmitted on the sender side using tcpdump, they are not being received by the other Raspberry Pi.
Setup Details:
Device: Raspberry Pi 3B
OS: Raspberry Pi OS (64-bit)
Nexmon patch installed and utilities built.
Setup interface mon0 like so:
iw dev wlan0 set power_save off
iw phy "$(iw dev wlan0 info | gawk '/wiphy/ {printf "phy" $2}')" interface add mon0 type monitor
ifconfig mon0 up
nexutil -m2
nexutil -k12
This is the same for both devices
Steps I’ve Taken:
Tried to verify monitor mode is working (using tcpdump I'm able to hear (not my) packets on channel 12) also airodump-ng mon0 recieves some packets.
Tried to confirm that packets are being transmitted on the sender side with tcpdump -i mon0 -xx on the sender.
Looks like in theory packets are being sent. When running ifconfig mon0 the TX packets count increases also.
The problem is the device listening does not pick up any packets from the devices sending.
It seems like I can't get the Raspberry Pi 3B to send any packets.
What I’m Trying to Verify:
Whether packets are being physically transmitted.
Why the receiver isn’t capturing these packets despite being in monitor mode.
The ultimate goal is to be able to send and receive custom packets on both devices.
Any advice or insights would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions