Router: TomatoUSB running on a RTN16 router is forwarding several ports to my Server.
Server: Windows Server 2012 is host to several VirtualBox Ubuntu VMs.
One VM, using NAT works great.
Another VM, using Bridged, works great on the internal network.
However, when I try to access the same location from the external network I am presented with the site hosted in IIS instead of my VM.
Change is not an option, this is about learning, not giving up.
I have considered the possibility that TomatoUSB is the culprit but do not have the technical expertise to prove it so if you can explain how it's at fault, that's a valid answer.
Tomato is configured to forward external port
8081 to internal port
80 on the Bridged IP (
192.168.1.124), and so what I'm seeing is that port
8081 is giving me port
80 on the Server's IP (
Per the comments, I attempted a ping to
220.127.116.11 from the bridged VM which returned fine, about 40ms response each time.
Per a request, here's a screenshot of the port forwarding screen on my TomatoUSB.
The screenshot tells what I have tested to be true. If I shut off the VM, then try to target port
8081 the site is not found. No redirection. So Tomato is pointing at the right IP. The culprit here is definitely bridged networking, either from the Router's perspective or the VMs.
For further clarification, Tomato clearly shows both the server box and the bridged VM with separate IPs and separate MAC Addresses. Here is another screenshot.
I've tested further per IRC. I disabled the NAT VM's port forwarding and the result was unchanged. This is further evidence that Tomato is at fault, and not VirtualBox.
I ran fiddler from a machine trying to access port
8081 and it shows the response header as a
301 redirect. This seems to be an after effect. I'm guessing
8081 is actually what's being sent to the Server IP (
192.168.1.200) and IIS is redirecting to
I have pcap files.