-
Notifications
You must be signed in to change notification settings - Fork 79
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
FAQ #1
Comments
Repository owner
locked and limited conversation to collaborators
Aug 31, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Before opening a ticket, ask yourself the following questions1:
Avoid emailing me, but open a ticket instead.
1. credit for this list goes to the senpai of my office . He sends me this list every time I ask him a question.
FAQ
Q: Help, I don't see the traffic in Burp.
A: Add a listener to the correct port. If Burp binds to a port lower than 1024, you probably would need to run Burp as Admin/root. If that is not the problem, run wireshark on your network to identify whether the packets are delivered to the machine running Burp. If that is the case, then you still have a Burp issue. If that is not the case, you may want to check your iptables rules.
Q: Usage of a Raspberry Pi/USB cards is not powerful enough for real use.
A: I mainly use this set-up to test a single IoT device that can be configured with a mobile app in my own lab. The traffic that these things produce, even the ones sending HD video, can easily handled by my Kali router. I use USB devices as they are portable.
Use an appropriate appliance if you want to redirect traffic in a real network. You may be able to reuse the iptables rules.
The text was updated successfully, but these errors were encountered: