אין לי הוטבוקס.
מודם רגיל (ותיק...) של הוט ונתב TPLINK (אותה בעיה בשני נתבים שניסיתי, וגם בחיבור ישיר למודם)
בעייה מוזרה בטעינת אתרים מסויימים - בזק בינלאומי
- amirn (פותח השרשור)
-
- חבר ותיק
- הודעות: 1012
- הצטרף: ספטמבר 2005
- נתן תודות: 65 פעמים
- קיבל תודות: 34 פעמים
ה SPEEDTEST תמיד 30M בבדיקה
שיניתי MTU בנתב
אני גם רואה שהשינוי השפיע ע"י בדיקת פינג
>ping -f -l 1222 google.com
Pinging google.com [172.217.20.142] with 1222 bytes of data:
Reply from 172.217.20.142: bytes=64 (sent 1222) time=74ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=72ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Ping statistics for 172.217.20.142:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 74ms, Average = 73ms
>ping -f -l 1223 google.com
Pinging google.com [172.217.20.142] with 1223 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 172.217.20.142:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
1250-28=1222 (28 HEADER)
שיניתי MTU בנתב
אני גם רואה שהשינוי השפיע ע"י בדיקת פינג
>ping -f -l 1222 google.com
Pinging google.com [172.217.20.142] with 1222 bytes of data:
Reply from 172.217.20.142: bytes=64 (sent 1222) time=74ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=72ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Ping statistics for 172.217.20.142:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 74ms, Average = 73ms
>ping -f -l 1223 google.com
Pinging google.com [172.217.20.142] with 1223 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 172.217.20.142:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
1250-28=1222 (28 HEADER)
amirn כתב:ה SPEEDTEST תמיד 30M בבדיקה
שיניתי MTU בנתב
אני גם רואה שהשינוי השפיע ע"י בדיקת פינג
>ping -f -l 1222 google.com
Pinging google.com [172.217.20.142] with 1222 bytes of data:
Reply from 172.217.20.142: bytes=64 (sent 1222) time=74ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=72ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Reply from 172.217.20.142: bytes=64 (sent 1222) time=73ms TTL=54
Ping statistics for 172.217.20.142:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 74ms, Average = 73ms
>ping -f -l 1223 google.com
Pinging google.com [172.217.20.142] with 1223 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 172.217.20.142:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
1250-28=1222 (28 HEADER)...
תראה לי TRACE לגוגל.
אגב, אתה מקבל IP בתבנית 84.110.194?
- amirn (פותח השרשור)
-
- חבר ותיק
- הודעות: 1012
- הצטרף: ספטמבר 2005
- נתן תודות: 65 פעמים
- קיבל תודות: 34 פעמים
ה IP בד"כ בתבנית 84.110.194 / 84.110.184 / 84.110.185
>tracert google.com
Tracing route to google.com [172.217.22.110]
over a maximum of 30 hops:
1 2 7 ms 8 ms 9 ms bzq-84-110-194-1.red.bezeqint.net [84.110.194.1]
3 9 ms 23 ms 9 ms 10.250.4.14
4 75 ms 73 ms 79 ms bzq-25-77-10.cust.bezeqint.net [212.25.77.10]
5 69 ms 69 ms 68 ms bzq-219-189-154.cablep.bezeqint.net [62.219.189.154]
6 68 ms 68 ms 69 ms bzq-179-72-241.cust.bezeqint.net [212.179.72.241]
7 67 ms 69 ms 75 ms 72.14.219.61
8 71 ms 76 ms 73 ms 209.85.240.193
9 76 ms 76 ms 72 ms 108.170.232.121
10 78 ms 77 ms 79 ms 209.85.253.108
11 79 ms 83 ms 80 ms 74.125.37.102
12 79 ms 78 ms 80 ms 209.85.143.24
13 68 ms 81 ms 68 ms 216.239.57.126
14 71 ms 71 ms 72 ms 216.239.47.53
15 69 ms 69 ms 70 ms 72.14.234.115
16 69 ms 69 ms 71 ms fra15s18-in-f14.1e100.net [172.217.22.110]
Trace complete.
>tracert google.com
Tracing route to google.com [172.217.22.110]
over a maximum of 30 hops:
1 2 7 ms 8 ms 9 ms bzq-84-110-194-1.red.bezeqint.net [84.110.194.1]
3 9 ms 23 ms 9 ms 10.250.4.14
4 75 ms 73 ms 79 ms bzq-25-77-10.cust.bezeqint.net [212.25.77.10]
5 69 ms 69 ms 68 ms bzq-219-189-154.cablep.bezeqint.net [62.219.189.154]
6 68 ms 68 ms 69 ms bzq-179-72-241.cust.bezeqint.net [212.179.72.241]
7 67 ms 69 ms 75 ms 72.14.219.61
8 71 ms 76 ms 73 ms 209.85.240.193
9 76 ms 76 ms 72 ms 108.170.232.121
10 78 ms 77 ms 79 ms 209.85.253.108
11 79 ms 83 ms 80 ms 74.125.37.102
12 79 ms 78 ms 80 ms 209.85.143.24
13 68 ms 81 ms 68 ms 216.239.57.126
14 71 ms 71 ms 72 ms 216.239.47.53
15 69 ms 69 ms 70 ms 72.14.234.115
16 69 ms 69 ms 71 ms fra15s18-in-f14.1e100.net [172.217.22.110]
Trace complete.