In reply to a post by gary333:

I tried it through the IP address for remote view, however as soon as the IP address changes I would assume it�s game over. I don�t use this method normally as I prefer the app and that works via P2P so doesn�t need any port changes.

Gotcha, fingers crossed similar situation this end - appreciate you sharing your experience, really helpful!

I've just rebooted the router to see what happens and now I can't get anything to work (using the new IP address i've been allocated). All ports show "not responding" when doing a port scan. Hmm, not my field of expertise so cannot figure it out but looks like it might be tempremental.

My router's IP address changes quite often. No problems are caused.

Oh - of course, I don't have their NVR. I don't have anyone's. Just camera, card in the camera, and the FTP uploads. If I chose to pay Reolink for their cloud storage, AIUI I still wouldn't need an NVR.

Everything just works, and will continue so to do as I add more cameras.

Oh - at the testing stage I did have the camera storing automatically via FTP on a laptop wired to the B311. Of course that was still file by file.

Maybe I didn't make it clear earlier that my phone has full remote access to live streaming as well, via the Android app.

Edited by RobertoS (Tue 30-Jul-19 01:06:02)

I�ve had no problems when using the Reolink app no matter how many times the WAN IP changes, been using them for years no probs.

I could access cameras via browser and IP address (was testing this for whether opening ports works) and until I rebooted it did. Now I cannot open up any ports after rebooting the B525 even though the rules are in place in the router. Wondering if I�m now hit CGNAT IP range, or three are blocking it somehow. Or maybe it�s just Huawei�s poor router software. Unfortunately no spare router to feed connection through to validate if it�s my B525 or Three.

App on the I phone and computer still work fine as that doesn�t require port forwarding as it uses Reolink as a middleman for shifting data. Issue here (well sort of as I don�t need this functionality as it was just for testing) is connecting directly to my Router via a browser and typing in my three/Smarty IL address + port number no longer routes directly to the NVR/cameras screen.

Edited by gary333 (Tue 30-Jul-19 01:22:56)

It's OK. I've just realised that you are only trying port forwarding for the OP. Not that you needed it for yourself.

Sorry for confusing things .

I'm on Smarty and as far as I can see I've always been given a CGNAT private IP address, meaning inbound port forwarding wouldn't be possible.

The main problem I can see with MVNO is when the network operator decides to reconfigure the transmitters "to give a better service", and makes things worse like EE has just done locally, so we now frequently loose all 2G,3G&4G at once, when we only use them via MVNO it can be awkward complain about the changes. At least when Three does it, we have direct contact with them.

You might find EE had no choice, a landlord may have decided to evict their equipment from the roof of a building, or decided to quadruple rent, so EE removed. This sort of thing happens all the time. The customer call centre can only say generically "reconfiguring" as they won't know the reason.

More a problem if you're in a city than in a residential / rural area with towers. In cities you find transmitters are hidden on buildings.