That is not true. There are plenty of routers that will not display their configuration UI if port 80 is not forwarded. For one, as a default, that is a security risk.kbern wrote:You wrote:
> You are testing the port forwarding from "outside", ie from a public IP address, as opposed to a computer that might be hanging off your ooma Hub or behind your router?
I don't think Ooma should behave that way because it means that it is changing the way my browser behaves/resolves vs. the way other people's do, it means some of my desktop links may not work when I'm at home (if, they point at my own server), and it makes it hard to test whether stuff really is accessible from outside.
The way routers and wireless access points/routers deal with port 80 issues like this is that if I want to get to the Ooma box's web UI page I would refer to it by its internal (downstream) name, e.g. 172.27.35.1. If I enter it's external (upstream) name (how the device before it sees it, in the case my cable modem) if it is not set up to forward a port, it should show its own UI, but if it *IS* set up to forward to port 80 on a downstream device, it should honor that request when it is called up via its "external" name.
This is how every router made works, and it really should be changed in Ooma.
My personal suggestion is if you have advanced networking needs you may want to consider Ooma's Advanced Networking Configuration. You'll get exactly what you want and Ooma won't need to compete against major router companies such as Cisco.
I have everything you are looking for in my network setup at home. I, and others on this forum, would be more than happy to walk you through how to do it.
As for the DNS loopback issue. This is a very common limitation in many residential routers. The last two routers I owned did not support DNS loopback.