If all went well, you should see something like this: Current MAC: a5:ae:f9:a4:b7:e3 (TP-LINK TECHNOLOGIES CO.,LTD.) Permanent MAC: a5:ae:f9:a4:b7:e3 (TP-LINK TECHNOLOGIES CO.,LTD.) New MAC: 00:d2:6b:d5:fe:bd (PHOTRON USA) ok Starting system message bus: dbus. ok Starting DNS forwarder and DHCP server: dnsmasq.
ok Starting advanced IEEE 802.11 management: hostapd. Proxy server listening at mitm-router transparently captures all HTTP traffic sent to the router at 10.0.0.1:80. It does not intercept HTTPS traffic (port 443) as doing so would alert a user that a possible man-in-the-middle attack was taking place. Traffic between URLs that begin with will not be captured. The mitm-router/data/ folder is shared with the docker container so that we can view the capture files that it places there on our host machine. By default, you will find the mitmdump capture file in mitm-router/data/http-traffic.cap.
You can also connect your INTERNETIFACE to a hostpot running on your phone your for mitm pwnage on the go 😉 Configuring Man-in-the-middle Supported environment variables are listed below with their default values.
This Is for the Script Kiddies: This tutorial is about a script written for the How to Conduct a Simple Man-in-the-Middle Attack written by the one and only OTW. WonderHowTo Null Byte.