M5 issues after upgrade 1.3.0
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.M5 issues after upgrade 1.3.0
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
Last week I upgraded to 1.3.0 Build 20190419 Rel. 70702. I've had significant issues since. The most obvious of which is "internet down". It happened twice last night. My uplink was fine in both cases but the Deco showed a red light and reported down. In both cases a power cycle of the M5 fixed the issue. I've also seen packet loss (as per ping of the M5 gateway) as high as 80%.
Prior to this upgrade the system was generally working well. I'm wishing I did not upgrade. Is there an option to downgrade firmware?
Thanks,
Scott
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
What happened to me:
- After updating: nodes disconnecting all the time (altough they showed a green led, and also in the app they seemed online)
- I removed the whole network and re-added all nodes one by one.
-> worked stable for almost a week (until today).
So again my impression is: maybe the issue is not in the firmware itself, but somewhere in the updating-process.
However: today again 1 node (a node connected with ethernet to the main unit) had no internet, while the LED was green,
and also in the app it was said the unit was online -> after a reboot it worked again. (note that all other nodes were also still working correct)
Any ideas what i can do to improve stability of the nodes ?
I would expect that the node connected with ethernet would have no issues,
but as shown, also nodes connected with ethernet can show issues.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
In the advanced settings I did already disable IPv6, I assume that is applied to all nodes ?
Or is there somewhere i should also disable it per node ?
BTW:
I also found the web interface and the System log,
so please let me know if it would be handy to search for something there
Other settings:
IPv4
Static IP ->
Primary DNS: 1.1.1.1
Secondary DNS: 8.8.8.8
IPv6
Disabled
DHCP
Start ip: 192.168.100
End ip: 192.168.250
Default gateway: 192.168.68.1
Primary DNS: not entered -> Will now try to use 8.8.8.8, altough i assume this should not matter
Secondary DNS: not entered
VLAN
Disabled
IPTV
Disabled
MAC Clone
Disabled
SIP ALG
Disabled
Fast Roaming
Disabled
Beamforming
Disabled
Operating Mode
Router
- Copy Link
- Report Inappropriate Content
My settings are : (those different of yours settings)
IPv4
Static IP ->
Primary DNS: 8.8.8.8
Secondary DNS: 8.8.4.4
DHCP
Start ip: 192.168.100
End ip: 192.168.250
Default gateway: 192.168.68.1
Primary DNS: 8.8.8.8
Secondary DNS: 8.8.4.4
Fast Roaming
Enable
Beamforming
Enable
Zero issues here and blazing fast network with 4 deco units.
- Copy Link
- Report Inappropriate Content
Thx for providing the settings!
I added a DNS in the DHCP settings, maybe it helps, but since the whole node was offline, it would be weird if this setting maskes a difference.
Anyhow: i will report back how it goes!
Speed also is good for me, for me the main issue after 1.2.4 is stability.
- Copy Link
- Report Inappropriate Content
My Network topology:
[[ FIBER 300mbps ]] --- [[ OTN ]] -- [[ ARCHER C7v4 NETWORK 10/24 FOR SERVERS LAN (1/2/3) - LAN 4 FOR IPTV // DMZ SETTING ON MAIN DECO ]] -- [[ LAN 1 MAIN DECO AS ROUTER]] -cat6 cable - [[ DECO 2 ]] :: 2 other decos linked via WIFI.
- Copy Link
- Report Inappropriate Content
Hi,
Please connect your device to the Deco and check the IP address and default gateway when the led shows red.
Note： How to get IP/gateway:https://www.tp-link.com/support/faq/838/
At the same time, connect your computer to the modem directly to check the info mentioned above.
Please try to reboot the whole system, including the modem and the Deco units to check the stability.
Meanwhile, try to change the DNS of the Deco units. (8.8.8.8/8.8.4.4)
Note: https://www.tp-link.com/support/faq/1855/
Any updates, please let us know.
smoser wrote
Hi,
Last week I upgraded to 1.3.0 Build 20190419 Rel. 70702. I've had significant issues since. The most obvious of which is "internet down". It happened twice last night. My uplink was fine in both cases but the Deco showed a red light and reported down. In both cases a power cycle of the M5 fixed the issue. I've also seen packet loss (as per ping of the M5 gateway) as high as 80%.
Prior to this upgrade the system was generally working well. I'm wishing I did not upgrade. Is there an option to downgrade firmware?
Thanks,
Scott
- Copy Link
- Report Inappropriate Content
hi @leogz thanks for your sharing and response, and glad to hear that the Deco works properly now.
@janoosti you can change the DNS server of the Deco to give it a shot.
Meanwhile, you can reboot the whole system, including the modem and the Deco units.
With computer connected to the Deco when the connection drops out, please check the IP address and default gateway obtained by your computer.
To do a comparison analysis, you can connect your computer to the modem directly to check these info.
Good day.
- Copy Link
- Report Inappropriate Content
- This morning the internet on the node with ethernet backhoul was again offline, i could connect to to the node though, but the connected client does not get internet then
- The LED was still green, also in the app the node seemed online
- Also all other nodes were still online (connected with wifi)
IP i got when connecting to the offline device:
- IP: 192.168.68.100
- Gateway: 192.168.68.1 (which is also the gateway in the settings under "DHCP server"). Note my router has as ip: 192.168.178.1, so this looks OK ?
- DNS: 1.1.1.1
Questions:
- I added the DNS under iPv4 / WAN and under DHCP server. Is that OK? Or should I remove it from iPv4 / WAN ?
- Is the gateway i got indeed OK ?
- I saw this post: https://community.tp-link.com/us/home/forum/topic/161584?page=1&t=2019%2F05%2F28%2018%3A47%3A56%20%2B0000
there a user says: Setting a DNS server of anything other than the default could block nodes with ethernet backhoul ?
Yesterday i updated already the DNS, but i did not reboot.
After the lockup this morning, i rebooted all devices.
Anything else I can try ?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3474
Replies: 15
Voters 0
No one has voted for it yet.