I have had nothing but problems with this router. A breeze to configure but regularly drops connection requiring hardware reset every couple days and chooses between letting phones connect or computers. We returned first unit after 3 weeks and replacement unit has the same behaviour. My hatred for this model is great
Sorry to hear about your problems. We initially had similar issues with this router and Xbox One consoles. So our first version of the review gave it a lower rating. A couple of weeks later, new firmware was launched, the problems were gone.
Drew
5 years ago
I have the EA7400 version of this router, and have had a great experience with it. I’m researching the EA7500 as well. There are plenty of refurbished units available (Amazon, Linksys), but I wish I knew more precisely the differences between the v.1 hardware and the v.2 hardware–especially since the v.2 hardware is on a different firmware path. Any ideas?
Hi Drew, the v2 has the MediaTek MT7621AT chipset running at 880 MHz (2 cores) while the original v1 has the Qualcomm Atheros IPQ8064 chipset running at 1.4 GHz (2 cores).
Yustianto
5 years ago
My office bought two of this. Somehow the 5ghz signal is mostly undetected (on both device!). In a rare ocassion, the 5ghz misteriously appears, but a simple powered off/on recurs the problem. The firmware also, seems to be buggy, even after an update. Disapointed..
Update: did some tweakings. Apparently my client devices can’t detect lower 5ghz channels (reg. policy). Once channel set manually to 149 or above, the 5ghz works just fine. The firmware is still buggy though, admin page occasionally inaccessible after setting tweaks, needs power restart.
Thank you for sharing your feedback. It will surely help other users. 😉
Dan
4 years ago
The thing about browsers complaining about security is expected and it is not possible to fix. Https consists of 2 parts (simplified):
1. sender and recipient establishes an encryption/decryption key that nobody else knows and starts talking using it, but neither at this point knows who the other one is, just that only 2 people understand the communication: sender and receiver
2. each verifies that the domain name of the other (routeradmin.com) is resolved to the correct IP of a certificate signed by a certification authority, which fails, thus the warning
no certificate authority would ever sign that anybody claiming to be routeradmin.com from ip 192.168.1.1 is always trusted
I have had nothing but problems with this router. A breeze to configure but regularly drops connection requiring hardware reset every couple days and chooses between letting phones connect or computers. We returned first unit after 3 weeks and replacement unit has the same behaviour. My hatred for this model is great
Sorry to hear about your problems. We initially had similar issues with this router and Xbox One consoles. So our first version of the review gave it a lower rating. A couple of weeks later, new firmware was launched, the problems were gone.
I have the EA7400 version of this router, and have had a great experience with it. I’m researching the EA7500 as well. There are plenty of refurbished units available (Amazon, Linksys), but I wish I knew more precisely the differences between the v.1 hardware and the v.2 hardware–especially since the v.2 hardware is on a different firmware path. Any ideas?
Hi Drew, the v2 has the MediaTek MT7621AT chipset running at 880 MHz (2 cores) while the original v1 has the Qualcomm Atheros IPQ8064 chipset running at 1.4 GHz (2 cores).
My office bought two of this. Somehow the 5ghz signal is mostly undetected (on both device!). In a rare ocassion, the 5ghz misteriously appears, but a simple powered off/on recurs the problem. The firmware also, seems to be buggy, even after an update. Disapointed..
Update: did some tweakings. Apparently my client devices can’t detect lower 5ghz channels (reg. policy). Once channel set manually to 149 or above, the 5ghz works just fine. The firmware is still buggy though, admin page occasionally inaccessible after setting tweaks, needs power restart.
Thank you for sharing your feedback. It will surely help other users. 😉
The thing about browsers complaining about security is expected and it is not possible to fix. Https consists of 2 parts (simplified):
1. sender and recipient establishes an encryption/decryption key that nobody else knows and starts talking using it, but neither at this point knows who the other one is, just that only 2 people understand the communication: sender and receiver
2. each verifies that the domain name of the other (routeradmin.com) is resolved to the correct IP of a certificate signed by a certification authority, which fails, thus the warning
no certificate authority would ever sign that anybody claiming to be routeradmin.com from ip 192.168.1.1 is always trusted