|
Hi All, I have been having a lot of trouble with the inbuilt update client in my TP-Link MR-3420 router sending abusive updates. I have read that the solution is to install an update client on the router itself (or configure it as there is no actual software to install)... Problem is, I have no idea how to do this. Is there a basic guide somewhere? Regards, Sam |
|
Hello sparker, Actually there is already an update client in your router firmware. That is what you have hopefully configured correctly, but which is apparently causing the problem of abusive updates. I would first make sure that you have the most current firmware installed on you router. That would be version TL-MR3420_V1_110418. If your router's update client continues to cause problems, your other alternative is to use an embedded update client in another device on the same network (dvr, webcam, etc), or install a software update client on a computer (on 24/7) on the same network. There are a number of software update clients available. Check out this page for more information concerning update clients. Depending upon what it is you wish to accomplish by using an DynDNS hostname, you may wish to reference this guide. Hope this helps, regards... |
|
Thanks for the response. I have the option of using the update client in my NAS or either of my two Foscams. I am guesing that they will send the host IP address, not their individual static IP address to dyndns though? As in, if I removed this setting from my router and put it on one of my Foscams, would I still be able to access the other devices on the network? Or would I require seperate hosts for each of those? (as obviously the foscam wouldn't have port forwarding options) Thanks, You will still need to forward ports in your router for each of the devices you wish to reach. Each device must be on a unique port since the WAN IP will be the same for all devices. This requires that the hostname for the device on port 80 will be accessed with http://example.dyndns.org. Another device, on say port 81, is accessed with http://example.dyndns.org:81 etc. Use one of those devices as the update client and work your way through the guide. Get one device working on Port 80 (default http port). Then post back if you have trouble. Get one working then tackle adding other devices.
Feb 23 at 03:19 AM
Scarabaeus
OK - thanks again. I follow what your saying (thats how its setup at the moment, just with the router doing the dyndns stuff as well). I think I could get away with just turning that part off at the router (leaving the port forwarding on) and turning it on at one camera. Cheers, Sam
Feb 23 at 05:40 AM
sparker
|