![]() Once that's accomplished, move on to Port Forwarding and the public IP, while also noting, as tonydi did, that you cannot use the public IP while in your local network, due to the lack of NAT loopback in the AT&T Gateway. So, before you worry about Port Forwarding and Internet Access, I'd suggest you ensure that you can access it using the local private network. Then from the outside port should go to your camera. When you access the service at 127.0.0.1:61722, is this from a terminal session on the physical host for the container? Is there a firewall on the physical OS that might block an external user that wouldn't block a localhost user? What port forwardings do you have setup You should be able to port forward on the Orbi to the camera's Orbi-assigned IP as normal, also port forward on the ATT router to the Orbi's ATT-assigned IP address. None of this has anything to do with port forwarding on the Gateway, all though it can be similar in concept. However, the software in the container is offering up a virtual port number that might be remapped by the container software. From a network perspective, clients trying to connect to the software have to use the physical port number. Using Kubernetes and containers on a host machine to run a network service can get very complicated in terms of what the port is on the container, and how that port is virtually mapped to the physical machine's ports. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |