Need extra help installing your Ooma Hub or Telo system? Let us know.
#3403 by snuggles
Tue Feb 24, 2009 4:03 am
I followed trim81's advice and for the most part it worked. Since adding
OpenDNS (208.67.222.222, 208.67.220.220) to my linksys router as main DNS when I go to the http://setup.ooma.com I get an openDND search page. How do I get around this?

I'm also trying to figure the best way to update my dyndns account since
the ooma hub is in front of my switch.

Any help will be appreciated,
#3404 by trim81
Tue Feb 24, 2009 4:20 am
Once you place your router on DMZ mode you can no longer access the Ooma setup page..

Reason being is that your LAN is now on a seperate subnet.

Only way to again access the Ooma setup page is to direct connect your Ooma hub, bypassing the router.

This shouldn't be an issue anyway, as I do not see a need to mess with the Ooma setup once you are properly configured
#3416 by inrame
Tue Feb 24, 2009 8:51 am
can you get to it by using the ip of the ooma hub? ie, 172.35.27.1
#3492 by BCNeuman
Tue Feb 24, 2009 10:38 pm
You can avoid placing your router in the DMZ yet still enable port forwarding by assigning the router a static IP address and then setting up port forwarding to the static address for all ports other than the range of ports used for the Ooma hub itself (if you assign a large range, you will get an error message telling you which ports you can't forward - and then assign around them).

If you do this, you will still be able to access the Ooma setup page from behind your router, and you will be able to access servers behind your router from the outside (assuming you had already set up port forwarding on your router - which I presume was set up in your pre-ooma configuration).

Note that you are loosing the firewall functionality of the Ooma hub in this configuration, but if the only device behind the hub is the router and you already have it set up as a firewall, this is no major loss.

What still does not work in this configuration, however, will be dyndns, which your router will still try to set as the private address behind the Ooma hub.

What would be nice (I guess for future versions of Ooma) would be if it allowed it to be configured NOT to be its own NAT firewall. i.e. it would provide a single address on the inside when queried by DHCP - i.e the same address that it received from your ISP on the outside. This would effectively pass the ISP assigned address through so that it would be visible to the router - which would then know the correct external address to use when calling up to dyndns. This would only work in the most common configuration where only a single device is connected on the HOME port (i.e. no connecting a bridge or hub - but a NAT box (most routers) are fine).

Who is online

Users browsing this forum: No registered users and 7 guests