Help to understand "Transparently proxify virtual machines" (docs tutorial)


#1

I have tired to follow the “Transparently proxify virtual machines” but it is quite confusing.

  1. Is ip address “192.168.3.1” random or where can I find it, what should I keep in mind?
  2. How can I check that Proxy server is OK before starting to setup clients?
  3. In the tutorial is a sentence “install the mitmproxy certificates on the proxied machine”. How should I configure the client machine if it is ubuntu server? What virtual box setting to use?
  4. How to debug when the connection in client(proxied machine) is not getting connection to server?
  5. I assume the tutorial is about two different virtual machines.

#2

We assign 192.168.3.1 as the IP address of the proxy machine in the internal network. You could use any other (local) IP address, you should need to make sure that you assign DHCP addresses in the same subnet in /etc/dnsmasq.conf.

When you invoke mitmproxy it should show up, other than that you need to add a client to view traffic.

This is unrelated of the virtualization technique you are using, see http://docs.mitmproxy.org/en/stable/certinstall.html.

Check if the proxied machine got an IP address verify in WireShark that it sends packets to the proxy machine.

Yes, proxy and proxied machine are differnt. You can have as many proxied machines in the internal network as you want.

Hope this helps!


#3

Thanks for your answer. I already managed to get it working (in Transparent mode and not with dnsmasq, but DNS, DDNS and DHCP. Connection between two Ubuntu LTS servers where one is proxy and other proxied).

Trying to find solution, about how to make mitmproxy work in Virtualbox. I was surprised about the lack of tutorials about virtual cluster creation.

I now understand that making mitmproxy run needs quite a lot knowledge about OS, OS debug and specially in computer network. Most confusing is virtual machine vs actual machine - how network configuration differs.