The simplest way to explain this is as follows. Your external IP address is the address that reaches your router from outside your house. That address is provided by your ISP (Internet Service Provider). It can be a dynamic address or a static address depending on the service you have agreed to with your ISP. If your address is dynamic, it can change at any time. A DDNS service like that provided for your cameras reports your WAN (external) IP address to that DDNS service. When you go to viewnetcam.com it knows what your WAN IP address and can use that to reach your router.
The internal mechanism you set up with static IPs and port forwarding is a way to route the communications from your WAN IP to specific internal devices. Those internal IPs (on your local network) have to be static in order for port forwarding rules to work. Since you only have one external IP address to reach you house from the internet, ports are used to determine how to route communications.
Let’s say that your WAN address is 217.96.111.45 and you have a camera on your local address of 192.168.0.212. If you want to reach that camera from the Internet there needs to be a rule to route traffic coming in on 217.96.111.45 to your local camera at 192.168.0.212. Port forwarding rules can route any external port to any single internal IP at the same or a different port.
The common way to express a port is with a colon following the IP address. With the proper rules in your router you could forward an external address of say 217.96.111.45:8080 to the internal HTTP port of your camera which would be 192.168.0.212:80. Now add into the mix another camera at 192.168.0.213:80 you set up a forwarding rule for another external port say 217.96.111.45:8081. That rule would allow you to access your second camera by using your same WAN IP with a different port number. Port 8080 would route you to camera 1 and 8081 would route to camera 2.
HomeSeer uses two different ports. By default the web browser answers on the standard HTTP port of 80 and HSTouch answers on the same IP address at port 10200. If you use the MyHS service, it takes care of a lot of the routing work without your intervention. If you chose to handle it yourself, you would set up two additional port forwarding rules – one for browser access and the other for HSTouch. The security is only provided by the HomeSeer user passwords you have set up. Since all of this (including your cameras) is taking place over a non-secure HTTP connection you have some vulnerability to external interception of communications to your network.
The MyHS service provides an additional layer of security. A lot of us set up a VPN (Virtual Private Network), so that we can enjoy reasonable security without counting on any cloud based providers.
So the short answer is you have several choices. With regard to a static IP, that falls into two categories, assigning static IP addresses to devices on your internal network, which is required if you use router based port forwarding. The other choice is your WAN IP which can be static or dynamic. If it is dynamic, a DDNS gives you the ability to find your home external address through a domain name, without needing to know the current IP address. Port forwarding will work with a DDNS service just like it will work with a static IP, you just add the port number to the domain name and your forwarding rules take care of routing information to the correct device on your home network.
Your camera access provided by viewnetcam.com probably does some manipulation behind the scenes taking care of port numbers relative to camera names, but always sending communications to your single WAN IP.
This may be clear as mud, but it might narrow the scope of future questions.
The internal mechanism you set up with static IPs and port forwarding is a way to route the communications from your WAN IP to specific internal devices. Those internal IPs (on your local network) have to be static in order for port forwarding rules to work. Since you only have one external IP address to reach you house from the internet, ports are used to determine how to route communications.
Let’s say that your WAN address is 217.96.111.45 and you have a camera on your local address of 192.168.0.212. If you want to reach that camera from the Internet there needs to be a rule to route traffic coming in on 217.96.111.45 to your local camera at 192.168.0.212. Port forwarding rules can route any external port to any single internal IP at the same or a different port.
The common way to express a port is with a colon following the IP address. With the proper rules in your router you could forward an external address of say 217.96.111.45:8080 to the internal HTTP port of your camera which would be 192.168.0.212:80. Now add into the mix another camera at 192.168.0.213:80 you set up a forwarding rule for another external port say 217.96.111.45:8081. That rule would allow you to access your second camera by using your same WAN IP with a different port number. Port 8080 would route you to camera 1 and 8081 would route to camera 2.
HomeSeer uses two different ports. By default the web browser answers on the standard HTTP port of 80 and HSTouch answers on the same IP address at port 10200. If you use the MyHS service, it takes care of a lot of the routing work without your intervention. If you chose to handle it yourself, you would set up two additional port forwarding rules – one for browser access and the other for HSTouch. The security is only provided by the HomeSeer user passwords you have set up. Since all of this (including your cameras) is taking place over a non-secure HTTP connection you have some vulnerability to external interception of communications to your network.
The MyHS service provides an additional layer of security. A lot of us set up a VPN (Virtual Private Network), so that we can enjoy reasonable security without counting on any cloud based providers.
So the short answer is you have several choices. With regard to a static IP, that falls into two categories, assigning static IP addresses to devices on your internal network, which is required if you use router based port forwarding. The other choice is your WAN IP which can be static or dynamic. If it is dynamic, a DDNS gives you the ability to find your home external address through a domain name, without needing to know the current IP address. Port forwarding will work with a DDNS service just like it will work with a static IP, you just add the port number to the domain name and your forwarding rules take care of routing information to the correct device on your home network.
Your camera access provided by viewnetcam.com probably does some manipulation behind the scenes taking care of port numbers relative to camera names, but always sending communications to your single WAN IP.
This may be clear as mud, but it might narrow the scope of future questions.
Comment