Forum Replies Created
-
Posts
-
– I bought TP-Link Archer MR200 (as an LTE 4G Router) officially from my ISP (one of the biggest internet providers in Greece), in order to avoid incompatibility issues. (Previously, I had bought different routers from the market and faced compatibility issues.)
– Please consider the fact that I experience exactly the same problem/behavior with both the OS v2.3 controllers I have; I bought the 2nd several months later than the first, to be used only as a backup. Therefore, I believe that the chances to get rid of the problem by replacing the Ethernet module are very small.@Ray: Update regarding network issue:
Router’s (TP-Link Archer MR200) firmware is updated to the latest version.
After upgrading the OS controller to 2.1.9, I checked the router’s Log and noticed that there is a repeating exchange of the following sequence of 4 messages with the controller:
1) “Recv DISCOVER from {OS controller’s MAC addr.}”, 2) “Send OFFER with ip {Reserved IP for OS controller}”, 3) “Recv REQUEST from {OS controller’s MAC addr.}”, 4) “Send ACK to {Reserved IP for OS controller}”.
This sequence continuous forever, causing delay issues and network failures to the LAN.
When reverted back to OS version 2.1.7, the issue disappeared (the reserved IP was assigned during the first try, without any retries initiated by the OS controller).
I hope the the above information might help to resolve the issue.@Ray: Thanks for the (new) suggestions and information!
I am (and always was) using static IP for the OS controller. However, I ‘ll try to experiment more with the network configuration.@ray: Thanks for the recommendations!
I upgraded to 2.1.9 and then did a factory reset (without configuring anything else). I noticed again network delays and connection issues.
After approx. 10 hours, I imported the production configuration. The network problems continued. Actually, I experienced total (permanent) loss of connection and therefore I had to restart (power-off and on) the controller. Therefore, I returned back to 2.1.7.
It seems that there may be an issue with the Ethernet library. Could be a compatibility issue of the library Ethernet implementations with the router’s one(?)
Awaiting for any further news/suggestions.@Ray: Thanks for the immediate response!
In replying to your question, I imported previous configurations. However, in order to overcome the issues, I have tried all ‘Reset’ options, i.e., ‘Clear Log Data’, ‘Reset All Options’, ‘Reset All Station Data’; after the last options, I have imported previous configuration.
Regarding the Ethernet case (hoping that this information would help in resolving the issue), I am using the TL-MR200 4G Router.Hi,
I have an OS H/W v. 2.3 DC device and upgraded the firmware from v. 2.1.7 to 2.1.9 a week ago.
Since then, I faced the following problems:
1. Long delays in connecting the app (web and mobile) with the OS device, either on LAN or WAN.
2. Unexpected (very often) reboots of the OS device (Last reboot reason = 99 [i.e., ‘power-on’, which, obviously, was not the case]).
As a result of the above (constant) behavior and since I have not read for any bugs of v. 2.1.9, I thought that it was a H/W failure of the OS device. Therefore, I replaced it with a brand new one device (OS H/W v.2.3 DC, which I have bought as a backup) and installed firmware v. 2.1.9. To my surprise, I noticed exactly the same malfunctioning behavior.
As a consequence, I downgraded to v. 2.1.7 and the device is running smoothly.
Has this behavior been reported by anyone else? Should we expect a (minor) revision to v. 2.1.9, addressing these errors and when?
Thanks in advance,
MM
