@Farrinaf wrote:
I cannot help but think that if you intend to host the camera access directly on your home network it is inevitable that you will have to expose your WAN IP address in some form or other to the world!
Its a long time since I used dynamic DNS services, but as I recall when creating an account you are given a bespoke alias e.g. say fishbowl.no-ip.com which corresponds to your dynamic IP address.
I would try substituting this alias for the no-ip.com contained within your code rtsp://no-ip.com:554/11
Personally I would just pay the £5 for a static IP address.
Finally (at the risk of irritating you by repeating myself) may I once again stress, if you are directly port forwarding from your router to the webcam on your local network, in my opinion the importance of firewalling off the webcam in its own DMZ.
I have never in the past had to expose anything other than my ddns address in the code, so don't see why I should have to here? If the camera works on my ip address, I am lost as to why it won't work with the ddns address. I can access the admin functions of the camera using the ddns, just not the stream.
I could pay the fiver, but that still doesn't solve my problem 100% as the place I am "borrowing" the stream from could switch off any time. I have found a streaming piece of software, but I need to sit and think about what to do as it is quite involved.
Once everything is in place and I have finished playing with internal ip addresses and stuff, yes it will be secured. As it is usually only me or less than 5 visitors a week, I am reasonably ok with it until I get it right.
