Hello everybody and thank you for reading.

At the moment I stay in Thailand and helping out some friends with their security cameras.

I can say I’m experienced and know how it works till now.

There are several camera-systems not reachable anymore thru the internet.

They have been working for months or even years but suddenly they can’t be accessed.

Believe me the ports and the DNS settings are ok.

If I ping to the domain name (I use dyndns) I get the IP number from the connection where the cameras are installed, so that is working fine.

Then I saw from all the not working camera systems a strange thing.

If I go on the internet and look up the IP-Address, with for example myip.nl, then I get another IP address as the WAN IP address I see in the connection status from the modem.

And all the internet connections from the not working camera systems have this strange issue.

I experimented with different ports but I can’t reach the cameras whatever I do.

Changed to port 80 what for sure is open but no connection.

Put the IP number from the camera in the DMZ still no connection.

I’m sure it has to do with the different WAN IP addresses and now I have no idea what to do next.

Anyone has an idea?

Thanks for your time

regards Alanso

100 range ip is carrier grade nat, recent thread on here about it with true.

If you are stuck with it then only solution would be a vpn...port forwarding impossible on carrier grade nat.

However the thread about true said their support can fix it though customer service know nothing...

Basically the issue is ipv4 addresses are a rare and limited commodity now so isps need to either pay a lot or take alternative routes to get new customers online...but they do still have ips so if you complain could get a normal home user moved instead who wouldnt even notice.

I manage several cams on 3bb and use 3bb at work and home and not observed this yet, hope its not the case....please report back your findings.

Thanks for replying.

I can assure you that you will get this problem also. Because i see this problem more and more.

Not only 3BB but with True cable and even CAT fiber.

Monday i will call 3BB and see what they can do for me.

I'm afraid other simple solutions does not exists.

100.64.0.0 – 100.127.255.255 WAN Port Addresses indicate Carrier-Grade-NAT IP Address has been issued to the router.

You can try power cycling the router (Off/On) and see if the ISP will issue the router a Public routable IP Address via DHCP on the next startup. But if after six attempts you still are only receiving a CG-NAT Reserved Private IP Address then you'll need to call up the ISP and ask (beg?) them to give you a working IP Address.

Many ISP's will just start moving whole groups of users over into CG-NAT addresses that then all share a common IP Address at a Proxy/Gateway to communicating with the Public Internet. Those that don't notice don't care, all is good. Those that notice and complain may get provisioned so they are back to being issued regular Public IP Addresses.

So try power cycling the WAN router first.

If that doesn't work after several attempts then call the ISP. Hopefully you'll reach someone who understands the words "Public IP Address".

You can try power cycling the router (Off/On) and see if the ISP will issue the router a Public routable IP Address via DHCP on the next startup.

Rebooting the modem has no effect on the IP numbers, they stay the same.

But public different then the WAN IP address in the modem.

This must create a lot of problems with the CCTV suppliers.

Many CCTV manufacturers try to offer different techniques for accessing cameras remotely.

While the option is to use UPnP or an open port on a Router is the easy one, other options include the CCTV sending a beacon to an external server that can used to communicate with the CCTV system. The manufacturers just need to broaden their connection options.

Many CCTV manufacturers try to offer different techniques for accessing cameras remotely.

Yes, I have been able to put some camera's back online with the P2P option.

But not all DVR are supporting this.

Today called True and they changed it. have now same public IP as the WAN ip in the modem.

And cameras up