Ok, using this configuration my FTP port 21 is forwarding fine, my Bittorent port 6881 to 6889 forward fine, but my Linksys WVC54GCA Wireless Internet Home Monitoring Camera port 1024 is not working. I can access the camera's video stream from inside the network, but from outside it does not connect. I use no-ip.com for DNS service, but even keying the address direct does not connect. I would like to avoid moving the hub after the router if at all possible.bw1 wrote:bw1 wrote:bw1 wrote: Are you sure you got the DMZ setup correctly?
Here's what I have:
On the Advanced Settings page of http://setup.ooma.com:
The IP address of the Ooma hub is 172.27.35.1
The DHCP Configuration Start and End Addresses are both set to 172.27.35.10
The DMZ Address is 172.27.35.10
After reseting the hub and router, the router gets the address 172.27.35.10 and is placed in DMZ and is controlling and allowing access to the rest of the LAN.
Others have set it up differently with the hub after the router and can give more advice on that setup.
Telo with 2 Handsets, a Linx, and a Safety Phone
Telo2 with 2 Handsets and a Linx
no-ip has the same, client software that runs as a service updating the DNS on a regular basis. The DNS is not the issue, even if I type in the public address it will not connect. FTP using the DNS connects fine.murphy wrote:I have never used no-ip. I use DynDNS. I have yet to find a router that implements the required protocol properly. It is very likely that your router is sending the private IP address that it got from the hub to no-ip instead of the actual IP address. DynDNS has client software that runs on a 24/7 computer which does the update properly. I would think that no-ip would also have a client available.
Thank you to everyone that responded back to my inquiry. I believe I got the situation fixed. You can test it for me by connecting to http://www.watchchester.com and viewing the streaming video. This is just a webcam we setup to keep an eye on our dog when he was a puppy. Now he's 8 but we leave it up to watch him.scottlindner wrote:Can you describe your exact problem again? Is this a NAT loopback problem?
On my router just out of desperation I changed the port forward protocol from Both to TCP and that's when it began working again. All other port forwards are set to Both and work fine, but they are TCP based services such as FTP. I'm sure there is a technical reason why that worked, but I'm just happy being able to see my dog again.
BTW, he's Norwegian Elkhound not German Shepard like lot's of people think.
Ahh.. so your web cam is using UDP and you were previously just doing TCP. That makes sense. I would have gone through similar until I figured that one out.
Glad it's all working now.
So, in a nutshell, I have a cable modem getting my outside IP -> to the Telo, which is handing off a static IP to my router -> which is handing off a static IP to my laptop. My router is in the Telo's DMZ and ports are forwarded, but not showing as open from the Internet, to my laptop's IP. Any ideas why this wouldn't be working, especially when it was for a while? Thanks.
You need to blank the DMZ field in the Telo and double check on the rules for ports forwarding in the Advanced page of the telo setup page.
Hope this help, and please post back.
Are there better or worse practices in terms of how to setup the Telo and router and which port(s) to use? Here are some various combinations of techniques I think I've tried. In all cases, my router has the same port forwarding rules to my laptop's static IP address:
1) Telo first and last and DMZ all set to the same IP, outside of the usual DHCP range (which I've forgotten, but I think it starts at 172.27.35.10 and goes to .100 or .150). I've regularly tried one above the home port IP, that is 172.27.35.2. Router set to DHCP.
2) Same as above, but router set to static IP, with the WAN address the same as the address in the Telo's DMZ and first/last DHCP settings (all three the same, in my case 172.27.35.2), 255.255.255.0 subnet mask, and the home port's 172.27.35.1 for both default gateway and first static DNS.
3) Put Telo back to default DHCP settings and use the static router settings above to force the router to pick up a single address.
4) a) Have my router address in the Telo's DMZ *AND* have ports forwarded in the Telo to the same address (the one my router's using), b) use only the DMZ setting, or c) use only the port forwarding settings.
5) After making changes in setup.ooma.com a) reset the Telo by unplugging for 30 seconds and then letting it boot up again or b) don't bother, just save settings in setup.ooma.com.
6) [I haven't tried this lately] Use a static IP within the Telo's normal DCHP range, ie above 172.27.35.10. And does it matter - if you leave DHCP range settings on the Telo at their defaults - whether the IP you assign to your router is within or outside of this range?
7) Should I be rebooting my cable modem in the midst of all of this nonsense? My connection is fine, but I've had the same IP lease for several days, and maybe that's an issue?
Sorry, this is getting awfully confusing, but I just keep piling one thing on another and figure I'll never resolve the problem. Someone did write somewhere in the forums that it isn't a good idea to have you router in the Telo's DMZ and forward ports in the Telo to that same IP, but I don't know what the theory is behind that.