pete_c
Guru
Is it possible that the router puts restrictions on certain ports or ranges of ports?
no
Is there a problem with using 80xx?
no
Does the Elk software continue to work using the WAN address while connected to the WLAN address after about 30 minutes?
Wondering about maybe its caching the data. Guessing too that Elk and cams ports are configured as TCP (versus TCP/UDP?)
T-Mobile now is massaging the video data flow and restricting tethering to 3G versus LTE (4G) recently. IE: specifically for video streaming. AT&T may be doing similiar? There seems to be an about-face relating to net neutrality rules going on with the cellular carriers, much the same as the ISP's. They have been doing it all along and playing ignorant about it.
Not sure if this would have anything to do with your issue / NAT reflection / change from one router to another though.
RTSP typically utilizes two ports ...one for video and one for control of the video.
Video is video is video is video.
You have only mentioned that now this doesn't work with new Frontier router and it did work with old ISP router.
Test one camera in a DMZ and see what happens. IE: open the camera IP addess to the internet. - IE: no rules for a bit.
Googling found another reference to ISP routers and NAT reflection specific to models utilized by ISPs.
Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.
This is an issue since each region has to specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.
Here on Cocoontech brought up the issue (on another thread) that my Linux Firefox flash isn't working anymore for a bunch of news sites using the Home ISP connection and that it is been made dysfunctional due to security concerns. Odd thing is if I use the same laptop tethered to my T-Mobile account then the Linux Firefox Adobe flash videos work fine but if I do an IPSEC VPN tunnel to my home mothership then the Firefox Adobe Flash videos do not work.
no
Is there a problem with using 80xx?
no
Does the Elk software continue to work using the WAN address while connected to the WLAN address after about 30 minutes?
Wondering about maybe its caching the data. Guessing too that Elk and cams ports are configured as TCP (versus TCP/UDP?)
T-Mobile now is massaging the video data flow and restricting tethering to 3G versus LTE (4G) recently. IE: specifically for video streaming. AT&T may be doing similiar? There seems to be an about-face relating to net neutrality rules going on with the cellular carriers, much the same as the ISP's. They have been doing it all along and playing ignorant about it.
Not sure if this would have anything to do with your issue / NAT reflection / change from one router to another though.
RTSP typically utilizes two ports ...one for video and one for control of the video.
Video is video is video is video.
You have only mentioned that now this doesn't work with new Frontier router and it did work with old ISP router.
Test one camera in a DMZ and see what happens. IE: open the camera IP addess to the internet. - IE: no rules for a bit.
Googling found another reference to ISP routers and NAT reflection specific to models utilized by ISPs.
Many DSL routers/modems prevent loopback connections as a security feature. This means that a machine on your local network (e.g. behind your DSL router/modem) cannot connect to a forward facing IP address (such as 199.149.252.44) of a machine that it also on your local network. Connecting to the local IP address (such as 192.168.2.40) of that same machine works fine.
This is an issue since each region has to specify an IP address for the client to connect. This is the ExternalHostName parameter in a regions config file (e.g. bin/Regions/Regions.ini). In the absence of NAT loopback, if a forward facing IP address is specified (such as 199.149.252.44) then external clients will be able to connect to the region but clients on your local network will not. If the internal address were put in ExternalHostName instead (e.g. 192.168.2.40) then viewers on the local network will be able to connect but viewers from an external network would not.
Here on Cocoontech brought up the issue (on another thread) that my Linux Firefox flash isn't working anymore for a bunch of news sites using the Home ISP connection and that it is been made dysfunctional due to security concerns. Odd thing is if I use the same laptop tethered to my T-Mobile account then the Linux Firefox Adobe flash videos work fine but if I do an IPSEC VPN tunnel to my home mothership then the Firefox Adobe Flash videos do not work.