Using bettercap, how can I intercept traffic which goes to a proxy server which is configured in browser?
With no proxy configured it is working fine. But as soon as a proxy is set in the browser connection settings, bettercap is unable to see traffic. I guess this is normal since with proxy traffic is going to the proxy server rather than the gateway.
Is it possible in such a setup to intercept traffic with bettercap? Is there any other way to achieve the same without bettercap?
bettercap -T 192.168.1.5 --proxy -P POST
- User IP: 192.168.1.5/24, G/w 192.168.1.1
- Proxy Server IP: 172.27.0.50
- Kali Linux (running bettercap): 192.168.1.10/24, G/w 192.168.1.1
My question is more towards topological scenario..and how to overcome that.? Bettercap is working perfectly.
I'm using this command.
bettercap -T x.x.x.x --proxy -P
and getting this output
[E] You're using bettercap as a normal HTTP(S) proxy, it wasn't designed to handle CONNECT requests: CONNECT sam.msn.com:443 HTTP/1.0 User-Agent: Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko Connection: Keep-Alive Content-Length: 0 Host: sam.msn.com Pragma: no-cache
my target is using IE 11 with on Windows 7 with proxy configured.
Proxy is on y.y.y.y:80
target machine is not multi-homed. All its traffic is passing through the gateway only.
I don't have any access to target machine.