Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roberto2212]

router auto mtu with network adapter 1492 mtu
on cmd:

C:\Windows\system32>ping -f -l 1464 212.69.63.47

Pinging 212.69.63.47 with 1464 bytes of data:
Reply from 212.69.63.47: bytes=1464 time=13ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=14ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=14ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=14ms TTL=254

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

C:\Windows\system32>ping -f -l 1465 212.69.63.47

Pinging 212.69.63.47 with 1465 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 212.69.63.47:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>tracert 212.69.63.47

Tracing route to telehouse-gw3-lo1.idnet.net [212.69.63.47]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Linksys00463-h [192.168.1.1]
  2    13 ms    13 ms    12 ms  telehouse-gw3-lo1.idnet.net [212.69.63.47]

Trace complete.

test on router wrt1900acs linksys with mtu auto:

see pics.

[roberto2212]

on router no reply trace route 212.69.63.47...why?

[ejs]

The Windows tracert program sends ICMP packets, the Linux traceroute program in the router sends UDP packets by default, so it'll be because 212.69.63.47 does not reply to UDP packets, but does reply to ICMP (ping) packets.

[roberto2212]

Also tryed with router auto mtu and network adapter 1500 mtu
cmd:

C:\Windows\system32>netsh interface ipv4 show subinterfaces

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
4294967295                1          0     171017  Loopback Pseudo-Interface
  1500                1       6207      21209  Ethernet 2


C:\Windows\system32>ping -f -l 1464 212.69.63.47

Pinging 212.69.63.47 with 1464 bytes of data:
Reply from 212.69.63.47: bytes=1464 time=14ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=14ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=13ms TTL=254
Reply from 212.69.63.47: bytes=1464 time=13ms TTL=254

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

C:\Windows\system32>ping -f -l 1465 212.69.63.47

Pinging 212.69.63.47 with 1465 bytes of data:
Reply from 91.135.0.53: 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 212.69.63.47:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>tracert 212.69.63.47

Tracing route to telehouse-gw3-lo1.idnet.net [212.69.63.47]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Linksys00463-h [192.168.1.1]
  2    12 ms    12 ms    12 ms  telehouse-gw3-lo1.idnet.net [212.69.63.47]

Trace complete.

[Chrysalis]

add -I flag to the linux command to mimic windows behaviour.

[roberto2212]

add -I flag to the linux command to mimic windows behaviour.

I dont understand what you mean.

[ejs]

It probably wouldn't work anyway, putting -I 212.69.63.47 into the box in the router web interface. In any case, it is not really a problem.

The ping results for 1464 bytes are what is expected with a 1492 MTU to 212.69.63.47.

[d2d4j]

Hi

Ejs is correct for 1492 mtu

I have tested your gateway and it responds upto 1472, which with 28, gives 1500

You need to test from pc to your router, as that has to be the limiter to 1460

So command prompt

Ping -f -l 1464 192.168.1.1

If your router is set to 1500 mtu, it should take packet of 1472

If the router fails on this test, check your pc mtu settings, just to double check your pc is not limiting

Many thanks

John

[Chrysalis]

add -I flag to the linux command to mimic windows behaviour.

I dont understand what you mean.

sorry I meant the linux traceroute command, but of course if you just running it in a router GUI then -I will likely break it.  Sorry.

[ejs]

You need to test from pc to your router, as that has to be the limiter to 1460

Not necessarily, it could be somewhere else on the route between the IDnet gateway and www.speedguide.net.

[d2d4j]

Hi ejs

Many thanks, but I believe roberto test to idnet gateway show 1464 fine, but 1465 failed

However, as you correctly stated, 1464 + 28 is 1492

Speedguide on our connection shows fine, on bt business and I thought idnet uses btw

However, I think I maybe getting confused a little, as I'm losing track over the exact issue, if the mtu is running to gateway correctly, then the issue has to be higher up the upstream and outside of roberto control, but whilst I can see there maybe an issue say on the route to speedguide, I would think it is unlikely to be on differing routes to other servers

Infact, it should be easy to test using roberto tracert until it leaves idnet network

Many thanks

John

[ejs]

idnet may well use BTWholesale to get traffic from the exchange to idnet, which is not visible in the traceroute, but then the routing from idnet to the Internet in general, and www.speedguide.net in particular, may be completely different.

I expect the MTU issue may be a total red herring, a lot of barking up the wrong tree.

[d2d4j]

Hi Ejs

I have run a few tests from our connection, which shows the idnet network and speedguide.net for MTU working fine on 1472

I hope that helps and not makes it more confusing, and yes, I fully concur with you over MTU

Many thanks

John

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\****>ping -f -l 1472 212.69.63.47

Pinging 212.69.63.47 with 1472 bytes of data:
Reply from 212.69.63.47: bytes=1472 time=28ms TTL=243
Reply from 212.69.63.47: bytes=1472 time=29ms TTL=243
Reply from 212.69.63.47: bytes=1472 time=29ms TTL=243
Reply from 212.69.63.47: bytes=1472 time=29ms TTL=243

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

C:\Users\****>ping -f -l 1472 212.69.63.82

Pinging 212.69.63.82 with 1472 bytes of data:
Reply from 212.69.63.82: bytes=1472 time=26ms TTL=244
Reply from 212.69.63.82: bytes=1472 time=26ms TTL=244
Reply from 212.69.63.82: bytes=1472 time=26ms TTL=244
Reply from 212.69.63.82: bytes=1472 time=26ms TTL=244

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

C:\Users\****>ping -f -l 1472 212.69.63.72

Pinging 212.69.63.72 with 1472 bytes of data:
Reply from 212.69.63.72: bytes=1472 time=26ms TTL=245
Reply from 212.69.63.72: bytes=1472 time=26ms TTL=245
Reply from 212.69.63.72: bytes=1472 time=26ms TTL=245
Reply from 212.69.63.72: bytes=1472 time=25ms TTL=245

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

C:\Users\****>ping -f -l 1472 speedguide.net

Pinging speedguide.net [68.67.73.20] with 1472 bytes of data:
Reply from 68.67.73.20: bytes=1472 time=117ms TTL=47
Reply from 68.67.73.20: bytes=1472 time=118ms TTL=47
Reply from 68.67.73.20: bytes=1472 time=117ms TTL=47
Reply from 68.67.73.20: bytes=1472 time=117ms TTL=47

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

C:\Users\****>ping -f -l 1472 4.69.166.69

Pinging 4.69.166.69 with 1472 bytes of data:
Reply from 4.69.166.69: bytes=1472 time=28ms TTL=52
Reply from 4.69.166.69: bytes=1472 time=29ms TTL=52
Reply from 4.69.166.69: bytes=1472 time=29ms TTL=52
Reply from 4.69.166.69: bytes=1472 time=29ms TTL=52

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

C:\Users\****>ping -f -l 1472 212.113.9.66

Pinging 212.113.9.66 with 1472 bytes of data:
Reply from 212.113.9.66: bytes=1472 time=26ms TTL=245
Reply from 212.113.9.66: bytes=1472 time=26ms TTL=245
Reply from 212.113.9.66: bytes=1472 time=27ms TTL=245
Reply from 212.113.9.66: bytes=1472 time=26ms TTL=245

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

C:\Users\****>ping -f -l 1472 195.66.224.181

Pinging 195.66.224.181 with 1472 bytes of data:
Reply from 195.66.224.181: bytes=1472 time=25ms TTL=244
Reply from 195.66.224.181: bytes=1472 time=25ms TTL=244
Reply from 195.66.224.181: bytes=1472 time=25ms TTL=244
Reply from 195.66.224.181: bytes=1472 time=25ms TTL=244

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

Tracert idnet roberto (bbc not tested - only idnet)

1    <1 ms    <1 ms    <1 ms  Linksys00463-h [192.168.1.1]
2    24 ms    12 ms    12 ms  telehouse-gw3-lo1.idnet.net [212.69.63.47]
3    12 ms    12 ms    12 ms  telehouse-gw8-v523.idnet.net [212.69.63.82]
4    35 ms    12 ms    12 ms  telehouse-gw7-v505.idnet.net [212.69.63.72]
5    12 ms    12 ms    12 ms  rt-lonap-a.thdo.bbc.co.uk [5.57.80.90]

Vector trace from USA to idnet 212.69.63.47


AUSTIN

 1 0.88 *  0.57 10.10.0.1 NA not found Linux: 12:59:23

 2 0.93 *  0.54 74.115.12.2 NA US Unix: 12:59:23

 3 1.65 *  1.38 207.207.44.81 207-207-44-81.fwd.datafoundry.com. US Unix: 12:59:23

 4 0.86 *  0.56 207.207.35.185 207-207-35-185.fwd.datafoundry.com. US Unix: 12:59:23

 5 0.95 *  0.54 209.66.92.121 ae1.mpr1.aus3.us.above.net. US Linux: 12:59:23

 6 1.26 *  0.98 64.125.31.26 ae4.mpr2.aus1.us.zip.zayo.com. US Linux: 12:59:23

 7 6.62 *  6.36 64.125.31.251 ae2.cr2.iah1.us.zip.zayo.com. US Linux: 12:59:23

 8 110.03 *  109.76 64.125.30.240 ae27.cs2.iah1.us.eth.zayo.com. US unknown: 12:59:41

 9 114.51 *  114.36 64.125.29.44 ae3.cs2.dca2.us.eth.zayo.com. US unknown: 12:59:59

 10 104.80 *  104.61 64.125.29.228 ae0.cs1.dca2.us.eth.zayo.com. US unknown: 13:00:17

 11 104.93 *  104.78 64.125.29.130 ae5.cs1.lhr15.uk.eth.zayo.com. NL unknown: 13:00:36

 12 105.11 *  104.88 64.125.30.235 ae27.mpr3.lhr3.uk.zip.zayo.com. US Linux: 13:00:36

 13 104.82 *  104.52 64.125.30.55 ae13.mpr1.lhr15.uk.zip.zayo.com. US Linux: 13:00:36

 14 105.07 *  104.79 195.66.224.181 telehouse-gw.idnet.net. GB unknown: 13:00:44


 DENVER


 1 0.68 *  0.50 10.180.0.1 NA not found Linux: 12:59:22

 2 0.69 *  0.36 74.115.14.2 NA US Unix: 12:59:22

 3 0.71 *  0.42 209.235.29.117 117-209.235.29.appsitehosting.com. US Linux: 12:59:23

 4 24.26 *  24.08 173.209.228.13 NA US unknown: 12:59:29

 5 24.38 *  24.00 66.179.228.114 dal2cr1-te-0-0-0-2.sgns.net. US unknown: 12:59:35

 6 24.44 *  24.05 66.179.228.105 rch1br1-te-0-0-2-1.sgns.net. US Unix: 12:59:35

 7 * *  * 
Request Timed Out
NA unknown: undefined

 8 126.35 *  126.05 4.69.166.69 ae-128-3514.edge6.London1.Level3.net. GB unknown: 12:59:42

 9 126.42 *  126.16 212.113.9.66 IDNET.edge6.London1.Level3.net. GB Unix: 12:59:42
 

[roberto2212]

C:\Windows\system32>Ping -f -l 1464 192.168.1.1

Pinging 192.168.1.1 with 1464 bytes of data:
Reply from 192.168.1.1: bytes=1464 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1464 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1464 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1464 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 = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\system32>Ping -f -l 1465 192.168.1.1

Pinging 192.168.1.1 with 1465 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 192.168.1.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I thinking that, when I set router to auto,then mtu is 1492.I cannot set mtu manually to 1500 because showed me error that maximum mtu for pppoe is 1492.Im still waiting for reply from idnet why is on speedguige mtu 1460.Already I waiting 5 days.still not reply from idnet.And also if I set manually mtu less like 1460 then on speedguide showed me exactly same mtu like in router..say router 1452 then speedguide 1452,same 1458-1458..but router 1461 and speedguide only 1460.
Trace route to EA servers:

Host Name                        IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
Linksys00463-h                   192.168.1.1       1      0ms         0ms        0%        9 / 9      0ms / 0ms
telehouse-gw3-lo1.idnet.net      212.69.63.47      2      12ms        14ms       0%        9 / 9      12ms / 30ms
telehouse-gw8-v523.idnet.net     212.69.63.82      3      12ms        15ms       0%        9 / 9      12ms / 28ms
blackhole.prolexic.com           195.66.224.31     4      13ms        13ms       0%        9 / 9      13ms / 14ms
unknown.prolexic.com             72.52.60.200      5      13ms        13ms       0%        9 / 9      13ms / 13ms
unknown.prolexic.com             72.52.60.205      6      13ms        13ms       0%        9 / 9      13ms / 16ms
* Unknown Host *                 0.0.0.0           7      0ms
unknown.prolexic.com             209.200.168.132   8      85ms        85ms       0%        9 / 9      85ms / 86ms
* Unknown Host *                 159.153.93.2      9      92ms                   100%      0 / 8
* Unknown Host *                 159.153.226.70    10     93ms                   100%      0 / 8
* Unknown Host *                 159.153.226.67    11     93ms                   100%      0 / 8

Answer from EA:
Those last three hops after Prolexic are on our network and are configured to not return the packets you pinged to them, this does not indicate a problem as the are configured in this way on purpose.

[roberto2212]

https://help.ea.com/en-in/help/faq/connection-troubleshooting-basic/