Re: Plusnet Slow web browsing MTU change!

On 1 Oct 2005 12:28:54 -0700, "mmmmm (alias : nicknick)"
<mik_love@xxxxxxxxx> wrote:

>ahhhh. ok. took a look again at my settings and looked at an article in
>computershopper mag. It states to ping -f -l packketsize Gateway of
>ISP.
>
>So I put my router back to automatic which now reports that auto is set
>to 1492. I then did a ping -f -l 1372 195.166.128.53 and got the DF
>message back.
>
>I had to drop away down to 1372 before I did not get a DF message.
>
>ping -f -l 1373 195.166.128.53
>
>Pinging 195.166.128.53 with 1373 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 195.166.128.53:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
>ping -f -l 1372 195.166.128.53
>
>Pinging 195.166.128.53 with 1372 bytes of data:
>
>Reply from 195.166.128.53: bytes=1372 time=94ms TTL=123
>Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123
>Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123
>Reply from 195.166.128.53: bytes=1372 time=95ms TTL=123
>
>Ping statistics for 195.166.128.53:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 94ms, Maximum = 95ms, Average = 94ms
>
>
>As you can see below, my router is going the whole way up to 1472
>before it sends the DF message.
>ping -f -l 1473 192.168.1.1
>
>Pinging 192.168.1.1 with 1473 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),
>
>ping -f -l 1472 192.168.1.1
>
>Pinging 192.168.1.1 with 1472 bytes of data:
>
>Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255
>Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255
>Reply from 192.168.1.1: bytes=1472 time=3ms TTL=255
>Reply from 192.168.1.1: bytes=1472 time=14ms TTL=255
>
>Ping statistics for 192.168.1.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 3ms, Maximum = 14ms, Average = 11ms
>
>What I don't know though is my PC, router, Exchange, ISP is at fault.
>
>Can someone shed some light on this please.

Something strange about this xx72 xx73 packet size threshold - I just
tried pinging the 195.166.128.53 address from my Plusnet line and I
had to go down to 1272 packet size before it would reply with DF set.
.

Relevant Pages

  • Re: Can browse LAN but not internet
    ... Approximate round trip times in milli-seconds: ... Pinging 66.94.230.33 with 32 bytes of data: ... Ping statistics for 66.94.230.33: ... Packet needs to be fragmented but DF set. ...
    (microsoft.public.windowsxp.network_web)
  • Re: IE Routing Problem
    ... Set the client box MTU to 1492 and the firewall's MTU to 1492. ... Here's what I get when I run the ping you describe: ... Packet needs to be fragmented but DF set. ... >> routers generally provide for an MTU setting? ...
    (microsoft.public.win2000.dns)
  • Re: IE Routing Problem
    ... Set the client box MTU to 1492 and the firewall's MTU to 1492. ... Here's what I get when I run the ping you describe: ... Packet needs to be fragmented but DF set. ... >> routers generally provide for an MTU setting? ...
    (microsoft.public.win2000.networking)
  • Re: Plusnet Slow web browsing MTU change!
    ... Pinging 195.166.128.53 with 1373 bytes of data: ... Packet needs to be fragmented but DF set. ... Ping statistics for 195.166.128.53: ...
    (uk.telecom.broadband)
  • Re: IE Routing Problem
    ... Kevin D. Goodknecht Sr. ... add 28 and set your MTU to that number. ... Ping statistics for 65.65.91.214: ... Packet needs to be fragmented but DF set. ...
    (microsoft.public.win2000.networking)