Remote Firmware Update
Hi Everyone,
I am hoping you can help as i am totally at a loss here!
To give you an overview - I have 2 sites connected via a Manual IPSec Tunnel using the ER605. The Software based controller is sitting at Site A and manages the Router at both sites along with a couple of Access Points.
Problem: I am unable to upgrade the firmware at the remote site to the latest version (2.2.3) from 2.1.2. I have gone through all of TP-LINK's online documentation and have port forwarded TCP/UDP 8043 and 29810 - 29816 through to the controller. The progress bar gets to about 99% sits for a while and then proceeds to re-send the upgrade file. Eventually it fails the upgrade and returns back to it's previous firmware version.
Using the onsite Windows Server there, i can confirm that i am able to telnet into the Controllers 8043 port from the other side so i am not sure as to what is going on to be totally honest. I would love some pointers as to where i may have gone wrong with this as it is driving me nuts :-)
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I had a similar issue on an ER605v1 going from 1.3.0 to 1.3.1 via the controller (and not over a tunnel either).
Have you tried doing a manual upgrade of the device (Device->Config->Manage Device)?
You can get the latest v2 firmware file here and don't forget to unzip to a .bin file before uploading:
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Is router adopted in vpn tunnel or via wan intereface and remote public ip?
this problem usually occurs if the device does not have contact with the controller management port.
if the router is adopted towards the WAN interface to the controller, the router must have access to this port, which is NATed into the controller.
If the router is adopted in the VPN tunnel, the router must have access to this port on the LAN interface to the controller.
- Copy Link
- Report Inappropriate Content
Thanks for your reply and apologies for the delay in getting back to you.
I believe the router is being adopted via the VPN Tunnel, I am trying to get the Router using the Discovery Tool to update to the Public IP but it wont discover despite having all software firewalls off.
- Copy Link
- Report Inappropriate Content
Pretty sure the Discovery Tool needs to be on the same L2 domain...which won't happen over a VPN tunnel.
- Copy Link
- Report Inappropriate Content
Are you sure you read the ports documentation? This says the hardware controller needs 443 for its upgrades and software controllers use 8043 (seems weird to me, but):
https://www.tp-link.com/us/support/faq/3265/
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 433
Replies: 9
Voters 0
No one has voted for it yet.