-
Notifications
You must be signed in to change notification settings - Fork 57
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
no internet access/traffic with mitmproxy (wireguard mode) #197
Comments
Does the script assume the VPN is external? I think that's what
Some extra info/tests: When the vpn is up:
from my normal home network (10.1.1.0/24) same laptop as I used for above)
from 10.1.1.8 (mitmproxy/wireguard server)
Throughout all of this, mitmproxy didn't record a single bit of traffic When the vpn is down, all these commands work fine |
Firstly, thanks for this awesome project!
I'm trying to use this to set up a vlan for mitmproxy/wireshark (i.e anything that connects to the vlan gets intercepted) to assist with some reverse engineering projects that I have on the go. I think I'm nearly there after searching through other issues, but I'm now properly stuck.
mitmproxy has a wireguard mode https://docs.mitmproxy.org/stable/concepts-modes/#wireguard-transparent-proxy which makes this project a great match (conceptually at least!)
some context:
I can connect to the "mitm" wireless network but my traffic is not showing up in mitmproxy and I can't access the internet from this network. My mobile has been assigned 10.6.6.196 on this network, so should be in the forced IP range. My DNS and mitmproxy/wireguard server are in the 10.1.1.0/24 (exempt destinations) range so should be accessible.
Can you see anything wrong with my config? Any hints/suggestions would be very much appreciated.
I've checked there's no network isolation or content filtering enabled on this vlan and there's no client isolation/guest portal etc enabled on the wireless network.
here are my config files:
wg0.conf
this is copied from mitmproxy startup then edited as follows:
vpn.conf
The text was updated successfully, but these errors were encountered: