hello guys
i’m not english man , sorry !
my users is low speed
my bandwidth : 20Mbps
my download speed : 20Mbps
speed of page load : 4Mbps !!!
speed of mobile app : 1Mbps !!! ( example : WhatsApp , Instagram , Telegram and … )
speed of remote applications : 800Kbps ( Team Viewer , AnnyDesk , Ammy )
why ?
whats wrong ?
why my download speed is 20Mbps but speed of mobile app is 1 Mbps ?!?
how to calculate mtu for this network ?
Ping from end user using different packet size using the option “do not fragment “ (or use some free utility like https://elifulkerson.com/projects/mturoute.php).
If your client is a Mikrotik, leave all your pppoe settings to default: you can see in pppoe connection the mtu valute that the system have set.
Also be aware that In your schema, the bottleneckis represented by UPLOAD speed of vdsl.
thanks for the reply
Which IP address should I have ping ? ( Router ? DNS Server ? one hop after router ? )
my client have TP-LINK access point
All my users have 10Mb Upload
You can Ping 8.8.8.8
My Resualt :
G:\>mturoute www.google.com
* ICMP Fragmentation is not permitted. *
* Speed optimization is enabled. *
* Maximum payload is 10000 bytes. *
- ICMP payload of 1472 bytes is too big.
+ ICMP payload of 92 bytes succeeded.
+ ICMP payload of 782 bytes succeeded.
+ ICMP payload of 1127 bytes succeeded.
+ ICMP payload of 1299 bytes succeeded.
+ ICMP payload of 1385 bytes succeeded.
+ ICMP payload of 1428 bytes succeeded.
+ ICMP payload of 1450 bytes succeeded.
- ICMP payload of 1461 bytes is too big.
- ICMP payload of 1455 bytes is too big.
+ ICMP payload of 1452 bytes succeeded.
- ICMP payload of 1453 bytes is too big.
Path MTU: 1480 bytes.
G:\>mturoute -t www.google.com
mturoute to www.google.com, 30 hops max, variable sized packets
* ICMP Fragmentation is not permitted. *
* Speed optimization is enabled. *
* Maximum payload is 10000 bytes. *
1 +- host: 192.168.1.1 max: 1500 bytes
2 -+++++++--+- host: 1.1.1.1 max: 1480 bytes
3 +- host: 192.168.*.197 max: 1480 bytes
4 +- host: 192.168.*.1 max: 1480 bytes
5 No response from traceroute for this TTL. Tried 3 times
6 +- host: 192.168.*.241 max: 1480 bytes
7 +- host: 10.10.*.61 max: 1480 bytes
8 +- host: 10.201.*.142 max: 1480 bytes
9 +- host: 10.201.42.117 max: 1480 bytes
10 +- host: 10.202.4.6 max: 1480 bytes
11 +- host: 89.221.34.10 max: 1480 bytes
12 +- host: 195.22.211.38 max: 1480 bytes
13 +- host: 72.14.205.182 max: 1480 bytes
14 ...-.- host: 108.170.252.19 not responding
15 .-.- host: 108.170.236.249 not responding
16 .-.- host: 72.14.235.39 not responding
17 No response from traceroute for this TTL. Tried 3 times
18 .-.- host: 216.239.50.241 not responding
19 +- host: 216.58.198.4 max: 1480 bytes
ping www.google.com -f -l 1460
Pinging www.google.com [216.58.198.4] with 1460 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 216.58.198.4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
ping www.google.com -f -l 1452
Pinging www.google.com [216.58.198.4] with 1452 bytes of data:
Reply from 216.58.198.4: bytes=64 (sent 1452) time=94ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1452) time=91ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1452) time=114ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1452) time=88ms TTL=45
Ping statistics for 216.58.198.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 114ms, Average = 96ms
ping www.google.com -f -l 1400
Pinging www.google.com [216.58.198.4] with 1400 bytes of data:
Reply from 216.58.198.4: bytes=64 (sent 1400) time=100ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1400) time=96ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1400) time=89ms TTL=45
Reply from 216.58.198.4: bytes=64 (sent 1400) time=111ms TTL=45
Ping statistics for 216.58.198.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 111ms, Average = 99ms
refresh
refresh