If it's a supported router, you could always look at flashing a custom firmware, such as DD-WRT, OpenWRT, Tomato, etc. for all other "mission control" operations :) The cable modem itself doesn't support loopback, but when my internal router's WAN IP is set as a DMZ, that doesn't seem to matter. The cable modem provides a separated guest network and unfettered connection for my son (he's a gamer, ping time is god), while the router handles all the DHCP, firewall, PXE control, etc. My home network uses a cable modem operating as a standard gateway, and a router with DD-WRT firmware as my primary "control" unit. there may be other possibilities, depending on the setup. Well I see Luis and U3 beat me to the answer: it's a limitation of the router, and the only sure way around it, if the router doesn't have the option, is to replace the router with a suitable one. Partner with an IT company if you don't know how, because it can be a mess to setup if you don't know what you are doing. If your customer doesn't have sophisticated enough systems to do that, they'll just have to upgrade. We don't use DDNS as we have static IP addresses and our own domain name server, so I make the entries on our internal DNS server for inside name to IP resolution and our domain name registrar's (ie GoDaddy, Network Solutions,, etc) DNS server for outside name resolution so I only have to make one DNS address entry. When you are outside the network, the DDNS service should point you to the appropriate public IP address. When you are inside the network, the internal DNS service (whether it be an internal DNS server or on the router), should override what the outside DDNS service says and should point you to the correct IP address on the inside. Whatever you use to resolve DNS entries internally on the network, if you're able to, you need to set a static A record that essentially says something like: This is a limitation of the router, it's not a problem with the DVR. Anyone have any luck finding a solution to this issue?īob and Ethan's solutions are the correct ones. There doesn't seem to be a way to turn local loopback on or off. Some modems from certain ISP's seem to allow "local loopback" and the DDNS domain works locally - but most do not. This is not a problem unique to one DVR manufacturer of couse - every brand of IP device or NVR has the same issue. Just add two "sites" to the app, you say? Nope - this causes a constant error message to pop up on whichever site doesn't apply (when at home, the DDNS site errors and when at Starbucks the local site errors). The problem is, the local IP only works when they are on their network, and the DDNS domain only works when they are off their network. But when we configure the Mobile app, the customer has to choose between the local IP 192.168.1.200 or the DDNS domain name. Here's a quick recap of this typical scenario : Customer has a DVR at 192.168.1.200 and DDNS : - Port forwarding is set up no problem and remote access works great via the DDNS domain. The age old local loopback issue - has anyone found a solution for this?ĭespite loads of Googling, we have yet to discover a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |