-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Peers not being detected #296
Comments
Try a higher number for auto-tune on extra channels. You can click the auto-tune plugin name when on the plugin page. It's at 3, try 9 or so. |
I was fixin to respond that didn't seem to help. I even setup my kali laptop to sniff beacons and wasn't seeing any. Decided to reboot all three instead of just using pwnkill and my kali laptop started seeing beacons and then my Pi3's started peering too. The Pi02W never did send any beacons and my Pi3's only sent a handful (5-12) and then stopped. Will revisit later. |
By sniffing beacons, I've come to the conclusion that beacons are sent for about a minute to a minute and a half after reboot and then stop. |
is "advertise" turned on (variable in personality)? ... it can be changed via auto_tune plugin too |
Yes, advertise is turned on. Using another device, I'm able to see the beacons get sent for about a minute or two after reboot and then it stops. It also seems like it stops receiving beacons around the same time. My current working theory is that something is set to delay starting (maybe something with bettercap) and that is affecting the ability to send/receive beacons. But I haven't really dug into it yet. |
Very similar issue to the one I reported a couple of months ago, but then only the Pi0W1 was affected. Never saw any beacons being sent and didn't manage to figure out the part of the code responsible to send them. |
Contact Details
N/A
What happened?
Peers aren't being detected. I've built 3 (2 on Pi4's and 1 on Pi02W) pwnagotchi's and none of them detect each other.
pwngrid-peer.log shows the api started and that advertisement is enabled:
I've ran wireshark from another device, and I don't see the beacons. I've also run tcpdump directly on the pwnagotchi and don't see the beacons there either. Looks like it's just not sending them out.
I tried to work through the code to try and debug but I don't know go. Guess I'll be trying to teach myself enough of that this weekend. LoL
Version
2.9.4-2
3rd Party Hardware
No
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: