Network offline and down after ER707-M2 V1_1.2.0 Build 20231214 Official Firmware
I discovered that two sites were down after updating the new firmware last night.. another bad one, worse than usual...
the entire network is down and offline.
So after two hours driving in a snow storm on my spare hour to fix the damage that TP-Link has done to my networks everything is back to normal after a downgrade to a working beta version 1.1.1 Build 20230927 Rel.35167
what's the point of beta when untested official firmware is changed and broken.
I made several attempts to upgrade and downgrade before I had to give up
my setup.
Site-A where the controller of all sites is version 5.13.22 (ER8411)
Site-B remote site with ER707-M2
Site-C remote site with ER707-M2
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
hi, i having same problem with thr 1.2.0
- Copy Link
- Report Inappropriate Content
I used 2 hours of my spare time today to test a bit more, this time in stand alone. configure a single vpn site to site tunnel, the idea was to try to adopt the router in the vpn tunnel. with the beta version the tunnel worked as it should, I upgraded to 1.2.0 and the only thing that worked was ping, I tried to access a file share and a web service, none of this could be accessed in the vpn tunnel with 1.2.0. I downgraded again and the tunnel worked as it should, I tried to upgrade/downgrade a couple of times to be sure of the result.
so there are apparently more problems than adopt and offline network with this firmware,
router is back in controller mode and with 1.1.1 Build 20230927 Rel.35167, no problem with this beta firmware..
and please don't release beta firmware and make big changes to the official version without us on the forum having tested the final version, I thought that was kind of the point of beta that we can test for bugs before it goes into production.
EDIT: After removing OpenVPN Server and Client in site config device adopt to controller and site to site work as exepted in controller mode.
- Copy Link
- Report Inappropriate Content
Apparently they came out a new version for Omada controller version 5.13. No idea the 1.2.0 work with the new controller firmware.
Is frustrating each time i updated the firmware.
- Copy Link
- Report Inappropriate Content
Hello @MR.S,
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID231254110, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hello @Soon_KY,
Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID231254134, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Soon_KY wrote
Apparently they came out a new version for Omada controller version 5.13. No idea the 1.2.0 work with the new controller firmware.
Is frustrating each time i updated the firmware.
yes, there are a bit too many errors on the routers, it has been like this from the very beginning, it has slowly improved but there are still updates that do a lot of damage. I thought it would get better after they started releasing the beta version on the forum, but it doesn't help much when the official versions are heavily modified from beta and untested before release.
but today I took a copy of one of the sites for the ER707-M2 and slowly took it apart, all my openvpn servers and openvpn clients were disabled but even if they were disabled they prevented adoption to the controller.
so to compare a bit with you, do you have openvpn server or client configured on your site?
after I deleted everything from openvpn I was finally able to adopt a router with a new firmware in my site.
wooow not bad,, but I run it to se hvat happend the next day, my other site is far away and I dont want to drive to fix one more time in hevy snow as last time.
- Copy Link
- Report Inappropriate Content
My current setup is pretty basic because i'm testing how good this products compare to other router i used.
Yesterday, i successfully update the router to 1.2 using standalone mode. No issue when update the firmware.
After that i added to controller and it no longer give me adoption loop. Seem working in this way.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @MR.S
Thanks for posting in our business forum.
MR.S wrote
I did a test in my lab. So, I did not get this issue. Port forward on ER8411 V1.1.0, ER707-M2 from 1.1.0 to 1.2.0.
I need to upload the video to YouTube tomorrow(my time zone). I did not replicate this issue. It did not go into the offline or adoption loop.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 2083
Replies: 25