After 2 days of a better internet connection, tonight the lag returned, torrents are blocked again and the speed is generally low (not over 4 Mbps on a 25 Mbps connection). Back to square one it seems
wollyka wroteAfter 2 days of a better internet connection, tonight the lag returned, torrents are blocked again and the speed is generally low (not over 4 Mbps on a 25 Mbps connection. Back to square one it seems
I'm facing lags 300ms for 2 weeks. I see i'm not the only one.
Trauma wrote
wollyka wroteAfter 2 days of a better internet connection, tonight the lag returned, torrents are blocked again and the speed is generally low (not over 4 Mbps on a 25 Mbps connection. Back to square one it seems
I'm facing lags 300ms for 2 weeks. I see i'm not the only one.
You are not. Try torrents, I am sure that you will noticed that they are also blocked at nights. Same for battle.net downloads and sometimes steam downloads.
The latency was OK during the weekend - around 80-120 ms. Now it is around 200-250ms. In a nutshell, you cannot download and you cannot play online games at nights with that lag..
wollyka wroteAfter 2 days of a better internet connection, tonight the lag returned, torrents are blocked again and the speed is generally low (not over 4 Mbps on a 25 Mbps connection). Back to square one it seems
It seems i'm lucky as my connection has been very stable for the past few days. I'm on the 4 mbps unlimited plan and am getting ~57ms on European game servers while syncing on G.DMT (turns off interleaving I believe).
I am on VDSL2. I cannot sync on adsl2+, adsl2 or G.DMT at all.
I am pretty sure that they are blocking and throttling traffic. Since you have 4 Mbps , i don't think that you will notice the speed difference especially if you have a good latency.
wollyka wrote
Shix wroteHas anyone tried IDM's VDSL? What router do they provide? They said they provide a router for 55$. I told them to switch me over to VDSL but I will be getting my own modem/router. (Any modem + router / combo recommendations for me, loose budget as long as it will last)
Also what speeds are you getting with VDSL?
Yes, i have the VDSL modem
It is the Tecnhicolor TG589vac v2. I use it as modem only. I connected my AC68U router to it in bridge mode. It works perfectly.
I have a Asus DSL-N16 VDSL modem/router (price around 55$). I can use it to tweak the SNR and increase/decrease speed. However, it is less stable than the Technicolor modem (that has a Broadcom which is more suitable for weak lines line Lebanon than the MediaTek chip available in Asus).

You can get the Asus dsl AC68u modem/router (but it is expensive around 200$) or the TP link Archer VR900 (Broadcom chip) for 190$. I recommend the Archer since it has a Broadcom chip like i said. If you want cheaper get the Archer VR600 or the VR400)

The speed depends on your distance from the CO
I was getting 14 Mbps/ 1 Mbps on adsl2+. On VDSL2 i get between 24 - 30 Mbps(depends on the day.time) download and 7-8 Mbps upload.
Well those were before the coronovirus, now the modem is still synchronizing at those speeds but the actual download speed is half what it used to be due to the congestion and lack of international bandwidth. Things are now a little better since yesterday. I hope that things will return to normal when we get out of this virus crisis.
Oh, so should I tell them to get me their router and use it as a modem, that way I get more options for routers. Or maybe I get a modem and a router. Is there any modem better than what they offer in the market?
Or should I just go for a modem router combo like the DSL-AC68U or the VR900? Which has more tinkering options (bandwidth control ...)?
Hi
Since you don't have a powerful router now, get the VR900 and use it as a combo. No need for their modem.
Hey,
Is the VR900 better than the Asus? Does it allow bandwidth control? Like giving each Device x mbps bandwidth?
The VR900 has a better chipset for modem than the Asus but i don' t have it so someone else should shed some light.

The Asus have bandwidth control and it works just fine (but i am using it as router only)
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=292ms TTL=51
Reply from 8.8.8.8: bytes=32 time=292ms TTL=51
Reply from 8.8.8.8: bytes=32 time=290ms TTL=51
Reply from 8.8.8.8: bytes=32 time=395ms TTL=51
Reply from 8.8.8.8: bytes=32 time=308ms TTL=51
Reply from 8.8.8.8: bytes=32 time=363ms TTL=51
Reply from 8.8.8.8: bytes=32 time=285ms TTL=51
Reply from 8.8.8.8: bytes=32 time=330ms TTL=51
Reply from 8.8.8.8: bytes=32 time=294ms TTL=51
Reply from 8.8.8.8: bytes=32 time=403ms TTL=51
Reply from 8.8.8.8: bytes=32 time=306ms TTL=51

Ping statistics for 8.8.8.8:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 403ms, Average = 323ms

Good luck gaming on that ping.

Is anyone else getting those figures?

Time of test 12:08 AM
alcolopa wrotePinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=292ms TTL=51
Reply from 8.8.8.8: bytes=32 time=292ms TTL=51
Reply from 8.8.8.8: bytes=32 time=290ms TTL=51
Reply from 8.8.8.8: bytes=32 time=395ms TTL=51
Reply from 8.8.8.8: bytes=32 time=308ms TTL=51
Reply from 8.8.8.8: bytes=32 time=363ms TTL=51
Reply from 8.8.8.8: bytes=32 time=285ms TTL=51
Reply from 8.8.8.8: bytes=32 time=330ms TTL=51
Reply from 8.8.8.8: bytes=32 time=294ms TTL=51
Reply from 8.8.8.8: bytes=32 time=403ms TTL=51
Reply from 8.8.8.8: bytes=32 time=306ms TTL=51

Ping statistics for 8.8.8.8:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 403ms, Average = 323ms

Good luck gaming on that ping.

Is anyone else getting those figures?

Time of test 12:08 AM
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=53ms TTL=50
Reply from 8.8.8.8: bytes=32 time=153ms TTL=50
Reply from 8.8.8.8: bytes=32 time=55ms TTL=50
Reply from 8.8.8.8: bytes=32 time=50ms TTL=50
Reply from 8.8.8.8: bytes=32 time=46ms TTL=50
Reply from 8.8.8.8: bytes=32 time=55ms TTL=50
Reply from 8.8.8.8: bytes=32 time=54ms TTL=50
Reply from 8.8.8.8: bytes=32 time=58ms TTL=50 Ping statistics for 8.8.8.8:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 153ms, Average = 65ms

Everything seems okay here, a bit unstable but that's nothing out of the ordinary.
I noticed that variation in ping yesterday on Ogero for the first time. But download speeds seemed stable and consistent on 1200 kb/sec. More people are staying at home now I guess.
It is around 125 ms now (4:30 PM), it was around 80 ms in the morning
Reply from 8.8.8.8: bytes=32 time=106ms TTL=48
Reply from 8.8.8.8: bytes=32 time=155ms TTL=48
Reply from 8.8.8.8: bytes=32 time=183ms TTL=48
Reply from 8.8.8.8: bytes=32 time=109ms TTL=48
Reply from 8.8.8.8: bytes=32 time=135ms TTL=48
Reply from 8.8.8.8: bytes=32 time=111ms TTL=48
Reply from 8.8.8.8: bytes=32 time=116ms TTL=48
Reply from 8.8.8.8: bytes=32 time=106ms TTL=48
Reply from 8.8.8.8: bytes=32 time=105ms TTL=48
Reply from 8.8.8.8: bytes=32 time=111ms TTL=48
Reply from 8.8.8.8: bytes=32 time=106ms TTL=48
Reply from 8.8.8.8: bytes=32 time=111ms TTL=48
Reply from 8.8.8.8: bytes=32 time=108ms TTL=48
Reply from 8.8.8.8: bytes=32 time=117ms TTL=48
Reply from 8.8.8.8: bytes=32 time=106ms TTL=48
Reply from 8.8.8.8: bytes=32 time=161ms TTL=48
Reply from 8.8.8.8: bytes=32 time=134ms TTL=48
Reply from 8.8.8.8: bytes=32 time=104ms TTL=48
Reply from 8.8.8.8: bytes=32 time=109ms TTL=48
Reply from 8.8.8.8: bytes=32 time=135ms TTL=48
Reply from 8.8.8.8: bytes=32 time=138ms TTL=48
Reply from 8.8.8.8: bytes=32 time=139ms TTL=48
Reply from 8.8.8.8: bytes=32 time=147ms TTL=48
Reply from 8.8.8.8: bytes=32 time=119ms TTL=48
Reply from 8.8.8.8: bytes=32 time=148ms TTL=48
Reply from 8.8.8.8: bytes=32 time=112ms TTL=48
Reply from 8.8.8.8: bytes=32 time=107ms TTL=48

Ping statistics for 8.8.8.8:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 183ms, Average = 123ms
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=81ms TTL=51
Reply from 8.8.8.8: bytes=32 time=94ms TTL=51
Reply from 8.8.8.8: bytes=32 time=100ms TTL=51
Reply from 8.8.8.8: bytes=32 time=91ms TTL=51
Reply from 8.8.8.8: bytes=32 time=80ms TTL=51
Reply from 8.8.8.8: bytes=32 time=99ms TTL=51
Reply from 8.8.8.8: bytes=32 time=117ms TTL=51
Reply from 8.8.8.8: bytes=32 time=97ms TTL=51
Reply from 8.8.8.8: bytes=32 time=81ms TTL=51
Reply from 8.8.8.8: bytes=32 time=96ms TTL=51
Reply from 8.8.8.8: bytes=32 time=89ms TTL=51
Reply from 8.8.8.8: bytes=32 time=96ms TTL=51
Reply from 8.8.8.8: bytes=32 time=92ms TTL=51
Reply from 8.8.8.8: bytes=32 time=88ms TTL=51
Reply from 8.8.8.8: bytes=32 time=104ms TTL=51
Reply from 8.8.8.8: bytes=32 time=85ms TTL=51
Reply from 8.8.8.8: bytes=32 time=80ms TTL=51
Reply from 8.8.8.8: bytes=32 time=85ms TTL=51
Reply from 8.8.8.8: bytes=32 time=113ms TTL=51
Reply from 8.8.8.8: bytes=32 time=98ms TTL=51
Reply from 8.8.8.8: bytes=32 time=94ms TTL=51
Reply from 8.8.8.8: bytes=32 time=90ms TTL=51
Reply from 8.8.8.8: bytes=32 time=93ms TTL=51
Reply from 8.8.8.8: bytes=32 time=94ms TTL=51
Reply from 8.8.8.8: bytes=32 time=85ms TTL=51

Ping statistics for 8.8.8.8:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 117ms, Average = 92ms

Everything seems to be fine right now some spikes here and there but it's fine! Syncing on ADSL2
4 days later
29/03/2020 22:34:42.31

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

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

Pinging 212.36.211.163 with 32 bytes of data:
Reply from 212.36.211.163: bytes=32 time=50ms TTL=62
Reply from 212.36.211.163: bytes=32 time=43ms TTL=62
Reply from 212.36.211.163: bytes=32 time=42ms TTL=62
Reply from 212.36.211.163: bytes=32 time=44ms TTL=62
Request timed out.
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Request timed out.
Reply from 212.36.211.163: bytes=32 time=49ms TTL=62
Reply from 212.36.211.163: bytes=32 time=44ms TTL=62
Request timed out.
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Reply from 212.36.211.163: bytes=32 time=47ms TTL=62
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Reply from 212.36.211.163: bytes=32 time=44ms TTL=62
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62
Reply from 212.36.211.163: bytes=32 time=42ms TTL=62
Reply from 212.36.211.163: bytes=32 time=43ms TTL=62
Reply from 212.36.211.163: bytes=32 time=41ms TTL=62

Ping statistics for 212.36.211.163:
Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 50ms, Average = 43ms

Tracing route to 212.36.211.163 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 42 ms 42 ms 41 ms 172.17.18.1
3 42 ms 51 ms 41 ms 212.36.211.163

Trace complete.

Pinging 8.8.4.4 with 32 bytes of data:
Reply from 8.8.4.4: bytes=32 time=80ms TTL=51
Request timed out.
Reply from 8.8.4.4: bytes=32 time=81ms TTL=51
Reply from 8.8.4.4: bytes=32 time=80ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=82ms TTL=51
Request timed out.
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=79ms TTL=51
Reply from 8.8.4.4: bytes=32 time=85ms TTL=51

Ping statistics for 8.8.4.4:
Packets: Sent = 15, Received = 13, Lost = 2 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 85ms, Average = 80ms

Tracing route to 8.8.4.4 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 43 ms 42 ms 45 ms 172.17.18.1
3 * * * Request timed out.
4 42 ms 41 ms 41 ms 212.36.211.164
5 45 ms 41 ms 41 ms 212.36.211.201
6 * * 41 ms 172.16.50.1
7 * * * Request timed out.
8 43 ms 43 ms * 172.16.49.1
9 81 ms 92 ms 82 ms 212.73.201.129
10 78 ms 81 ms * 4.69.159.134
11 80 ms 80 ms * 72.14.214.210
12 81 ms 80 ms 80 ms 108.170.252.241
13 80 ms 80 ms 80 ms 72.14.233.67
14 81 ms 79 ms 82 ms 8.8.4.4

Trace complete.


I mean the ms is good now but the packet loss is killing me
5 days later
High ping is back to high this evening after 9 so no game is possible and even slow downloads. Anyone else?
Reaching 250-400. Even after modem restarts.

Edit: I thought to update. It's back to normal though high jumps during past days and certainly not steady. Hopefully at least it won't get worse again, good luck.
9 days later
Hello everyone, i used to have my IDM connection configured using bridge mode setup, with the technicolor modem (setup bridge mode) connected to tp-link router (setup pppoe). However, the connection stopped working without doing any change to the settings. I called them and they told me to reset the modem to factory setting. The modem still connects to the internet if it is set in pppoe setting and not in bridge mode. Do you think IDM is not allowing bridge mode connections? Would they assist in such a case?
I used to have the same setup but i had to change it a little when i switched to VDSL because the new modem supplied by IDM doesn't have bridge mode. So now, I let the modem connect using pppoe and i put the router in automatic IP mode. Also i put the router in the DMZ zone in the modem settings.
wollyka wroteI used to have the same setup but i has to change it a little when i switched to VDSL because the new modem supplied by IDM doesn't have bridge mode. So now, I let the modem connect using pppoe and i put the router in automatic IP mode. Also i put the router in the DMZ zone in the modem settings.
Thanks for the reply, I have dd-wrt firmware installed on my router, so I set it to Automatic Configuration - DHCP, and it worked with the modem. I don't have a DMZ mode on the modem, I only have a "Assign the public IP address of a connection to a device" option. After adding the router to this option, a popup informs me "to release the current private IP address of the device and then renew the IP address to acquire a public IP address". The connection then drops and no longer works. Any idea on what is happening?
StannisTheMannis wrote
wollyka wroteI used to have the same setup but i has to change it a little when i switched to VDSL because the new modem supplied by IDM doesn't have bridge mode. So now, I let the modem connect using pppoe and i put the router in automatic IP mode. Also i put the router in the DMZ zone in the modem settings.
Thanks for the reply, I have dd-wrt firmware installed on my router, so I set it to Automatic Configuration - DHCP, and it worked with the modem. I don't have a DMZ mode on the modem, I only have a "Assign the public IP address of a connection to a device" option. After adding the router to this option, a popup informs me "to release the current private IP address of the device and then renew the IP address to acquire a public IP address". The connection then drops and no longer works. Any idea on what is happening?
This is the DMZ option, the modem is ancient and must be changed the firmware is usually messed up along with its updates. Anyways to use this feature you should assign the DMZed device a static local IP usually not within the DHCP range.

Meaning if your range is 192.168.1.100-254 then pick 192.168.1.5 for example.