NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR50 Port Forwarding not working as expected
I am attempting to configure my Orbi RBR50 Mesh router to configure Port Forwarding to access a web page on a node in my network. My network is a little complex -- I'm running on Xfinity, attached to an XFinity modem configured to Bridge Mode, so that all of the "routing" is passed down to the Orbl. On the network, I have a Windows Laptop that is itself running an Oracle VirtualBox Virtual Machine VM, running Ubuntu. The VM is itself configured using a virtual Bridge network adapter, meaning that the VM shows up as a peer to all of the other systems on the Orbi network. Orbi has assigned the VM as 192.168.1.104, and my web server running on port 80. Orbi has assigned my Windows host system as 192.168.1.61, and my web server running on port 8080.
Using this, all of the nodes in my private network can access either web server.
- I can go to my host Windows machine browser and access http://192.168.1.104:80, and it successfully accesses the VM Web Server running on Port 80.
- I can also go to another independent laptop on my home private network and access http://192.168.1.104:80, and it, too, resolves correctly and shows the web page.
- Finally, I can also go to my VM and access the same address above, and successfully see the VM web content.
Given the test above, my VM bridge network appears to be working great. My real objective, however, is to see this from the public web. Using the Orbi Router Administrator, I configured two port forwards:
- First one, I port forward port 81 from my public internet IP to my host Windows 192.168.1.61:8080 . And this works -- when I hit my public IP, xx.xx.xx.xx:81, I see my host system web page from the public internet.
- Second one, I port forward port 82 from my public internet IP to my VM 192.168.1.104:80 . However, this one fails - "This Site Cannot be Reached". It does not appear to be forwarding, even though the "Bridge" can see it.
Is there any reason why the Orbi wouldn't forward to a Virtual Machine, but will forward to the hosting system?
3 Replies
Windows Firewall has separate settings for 'Private' and 'Public' network access. (it is pretty clear that the Windows machine firewall is allowing access from both types of network.)
Does Ubuntu Firewall have similar distinction between 'Private' and 'Public' network access?
(what I know about VM can be summed up easily.... nothing)
Thanks for the response -- the answer is No, my Ubuntu doesn't have it's firewall turned on at this point.
I figured out my own problem. Ultimately, I went back and re-configured the network adapters for the VM. While I got the dual adapter configuration recommendation from an article where someone was trying to do exactly what I was doing, it never sat well with me -- a VirtualBox Bridge network configuration is a bi-directional access to both your local network and to your public internet, so it didn't make sense to me that you needed to have both it and a NAT adapter as well (which is far more limited as to what it can see).
I disabled the NAT adapter, and ran all of my networking through the solo-Bridge adapter. And magically, my Orbi port forwards started to successfully pass through to the VM, and could be accessed from the public internet.
Done! Thanks for anyone who tried to help.
