GL-XE3000 - torrent kills connection

Routers
1

Good day to you.

When I download a torrent (even one file) with a full speed (5G NSA around 600Mbps) after a few minutes it kills internet connection. The router says everything is fine but it is not. I need to restart the router to bring back the internet.

I tried to limit connections in torrent setup but it does not help.

Very rarely I also encoutered similar issue on Steam - but only when downloading with full 5G (NSA) speed - around 600Mbps.

Thanks. Have a good day.

6

Hello,

  1. What is your router current firmware version?

  2. When it occurs the Internet disconnect, is it able to access the router GL GUI? Or is ping [router LAN IP] (e.g. ping 192.168.8.1) reachable?

  3. Please try this firmware:
    openwrt-mediatek-mt7981-glinet_gl-x3000-squashfs-sysupgrade.bin

  4. Please PM me the issue syslog

7

Hello,

  1. I`m on the newest FW = 4.7.4.
  2. Yes, I`m able to log to GL GUI. All is green, I mean the router shows Internet connection is there, but in reality there is not.
  3. What kind of FW is that? A beta version or…?
8

Hello,

Thanks for your updates.

  1. On the LAN client (eg. PC), execute the following:
ping 192.168.8.1
ping 8.8.8.8
ping www.google.com
#Win:
tracert www.google.com
#Mac, Linux:
traceroute www.google.com

SSH to router, and check:

ping 8.8.8.8
ping www.google.com
  1. That is a beta version and is only for temporary testing.
9

C:\Users\jackiewigr>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Users\jackiewigr>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=24ms TTL=116
Reply from 8.8.8.8: bytes=32 time=45ms TTL=116
Reply from 8.8.8.8: bytes=32 time=40ms TTL=116
Reply from 8.8.8.8: bytes=32 time=38ms TTL=116

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 45ms, Average = 36ms

C:\Users\jackiewigr>ping www.google.com

Pinging www.google.com [142.250.186.196] with 32 bytes of data:
Reply from 142.250.186.196: bytes=32 time=30ms TTL=115
Reply from 142.250.186.196: bytes=32 time=21ms TTL=115
Reply from 142.250.186.196: bytes=32 time=32ms TTL=115
Reply from 142.250.186.196: bytes=32 time=16ms TTL=115

Ping statistics for 142.250.186.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 32ms, Average = 24ms

C:\Users\jackiewigr>ping www.google.com

Pinging www.google.com [142.250.186.196] with 32 bytes of data:
Reply from 142.250.186.196: bytes=32 time=37ms TTL=115
Reply from 142.250.186.196: bytes=32 time=46ms TTL=115
Reply from 142.250.186.196: bytes=32 time=27ms TTL=115
Reply from 142.250.186.196: bytes=32 time=27ms TTL=115

Ping statistics for 142.250.186.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 46ms, Average = 34ms

10

root@GL-XE3000:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=117 time=19.959 ms
64 bytes from 8.8.8.8: seq=1 ttl=117 time=30.811 ms
64 bytes from 8.8.8.8: seq=2 ttl=117 time=25.482 ms
64 bytes from 8.8.8.8: seq=3 ttl=117 time=25.502 ms
64 bytes from 8.8.8.8: seq=4 ttl=117 time=19.373 ms
64 bytes from 8.8.8.8: seq=5 ttl=117 time=30.263 ms
64 bytes from 8.8.8.8: seq=5 ttl=117 time=30.263 ms

11

root@GL-XE3000:~# ping www.google.com
PING www.google.com (142.250.186.196): 56 data bytes
64 bytes from 142.250.186.196: seq=0 ttl=116 time=16.082 ms
64 bytes from 142.250.186.196: seq=1 ttl=116 time=24.863 ms
64 bytes from 142.250.186.196: seq=2 ttl=116 time=22.732 ms
64 bytes from 142.250.186.196: seq=3 ttl=116 time=14.737 ms
64 bytes from 142.250.186.196: seq=4 ttl=116 time=24.974 ms

12

I think I will wait for the final version rather than beta :slight_smile:

13

Hello,

Thanks for the update.

Please do these check after the issue occurs, to help us determine which part of network has problems.

After the problem occurs and mark the occur time, please also export the issue syslog and send it to me via PM.