Print

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

[burakkucat]

This is really strange.

Agreed. 

I have been reading all posts in this thread but have not contributed, for there is nothing I can add.

[d2d4j]

Hi

It would be good if same test could be made from your sky connection, but setting all mtu to 1460

Does it lag - I myself do not think it would that difference

Do you have another router other then billion to try - i.e. Remove the billion from the equation

Are you on an IPv6 address for Internet

It does appear strange on idnet but not strange that another isp works fine, with no apparent lag, as it is most likely taking a different route and/or on different equipment i.e. Bt business is higher ping tests then bt residential, so that part of test can be ignored to a degree. However, that is why the test using sky on an mtu of 1460 is important

I do not think it is an issue at the cabinet, i.e. Leg disconnected or wired wrongly, but could be a stuck port I suppose, albeit I'm only guessing here

If you run a speedtest, are the down/up results normal for your connection

Many thanks

John

[burakkucat]

I do not think it is an issue at the cabinet, i.e. Leg disconnected or wired wrongly, but could be a stuck port I suppose, albeit I'm only guessing here

It most definitely will not be a problem with the DSLAM in the cabinet. Its sole action is to act as one end of a G.993.2 link, nothing more, nothing less. The G.993.2 link will be totally unconcerned about higher level software protocols that may be traversing it. 

[roberto2212]

Well I didnt try 1460 mtu on sky.I need test this because it is friend internet.My connection is ipv4.Im not sure if ipv6 support ps4.Also I tryed replace billion for hg612 sp08 firmware but was same result.I checked my faceplate where cable is connected where orange is on A and white on B.Tryed swap this cable but no different.So maybe is outside cable wrong connected or I really dont know.

[kitz]

Wiring/faceplate and DSLAM etc wont be affecting your MTU.   That's hardware.  MTU is more of a software construct (part of a protocol) at a different layer.

It would have to be something set on networking related hardware that specifically deals with data transmission such as routers/network ports/network cards.

[roberto2212]

Well, then I dont know where is problem.Because I tryed 2 different modem, 3 different pc and still not worked.On ps4 got delay.Also tryed ddwrt firmware,still same problem.When I tested my ps4 with friends sky broadband then all is excellent.Tryed hard reseting modem, no help.So definitelly must be problem with MTU.Also tryed asus rt ac66u with normal firmware and merlin firmware or tp link tl-wr841n and still is same problem.Same on dsl modem/router asus ac66u.Still I got delay.Tryed change mtu on ps4 1400,1452,1458,1460,1473,1492 or auto but not different.

[kitz]

MTU is end-to-end point.   Could be any router between your PC and the destination server.
The fact you get same result on different PC's would appear to rule out the PC.

I note that you are using speedguide.net test.   Have you tried something more local that perhaps uses different routing just for the sake of elimination.
Your ISP should direct peer to BBC so if you do a manual check then at least you may be cutting out most external routing.

See "Working out your maximum MTU"
http://www.kitz.co.uk/adsl/MTU2.htm

[kitz]

PS, you could take this one step further.

In combination with a tracert to say the BBC, you should be able to get a list of the hops involved, so you could try then pinging them with the
 -f -l [packet size]  command.
So you could also check your ISP gateway this way.

[roberto2212]

I think that you not read my post.Like isaid before I used tcp optimizer with option mtu/latency and showed me you can set mtu to 1492.Then double check with cmd:
C:\Windows\system32>ping -f -l 1464 www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.68] with 1464 bytes of da
Reply from 212.58.244.68: bytes=1464 time=14ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=15ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=14ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=16ms TTL=57

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

C:\Windows\system32>ping -f -l 1465 www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.68] with 1465 bytes of da
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.58.244.68:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
So correct mtu is 1492.My router is mtu on auto and pc network adapter default 1500.

Again tested on http://www.speedguide.net SG TCP/IP Analyzer with result:
MTU = 1460
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput. If you are using a router, it could be limiting your MTU regardless of Registry settings.
MSS = 1420
Maximum useful data in each packet = 1420, which equals MSS.
So I change my network pc adapter to 1492 then restarted pc and again tested on http://www.speedguide.net SG TCP/IP..same result mtu=1460

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

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
  1492                1  473390229   86816660  Ethernet
4294967295                1          0      72568  Loopback Pseudo-Interface 1
Question is why still showed me 1460 if I set 1492?
I hope that you understand.Thanks

[kitz]

I think that you not read my post.

Obviously not - I'm so busy with other things, that I just scanned the thread and thought I'd chip in to see if I could help.
I didn't see any manual test results using the command ping -f -l in the thread. By suggesting the ISP gateway I was trying to eliminate any external routing. 
If I had seen so, I wouldn't have wasted time my time and yours advising it. :/

[d2d4j]

Hi

You could try same test to your router, if test correct, same test to your gateway

This should show if your internal network running correctly at 1492, and if gateway can run at 1492

If gateway fails, contact idnet and let them have your test results

Many thanks

John

[d2d4j]

Hi

@kitz, sorry I have same test to do, but I do not think roberto understands, and missed the tracert

Command prompt

tracert BBC.co.uk

Then run your mtu test from the start of the tracert result until you hit the IP address restricting you to mtu 1460

Many thanks

John

[roberto2212]

C:\Windows\system32>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.26]
over a maximum of 30 hops:

  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]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    12 ms    13 ms    12 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
  9    13 ms    13 ms    13 ms  132.185.255.148
 10    12 ms    12 ms    12 ms  bbc-vip145.telhc.bbc.co.uk [212.58.244.26]

[roberto2212]

On my pc looks everything ok but if I connect ps4 then connection laging and I got delay..looks like ps4 network needs correct mtu.

my network idnet:
http://www.speedguide.net SG TCP/IP Analyzer mtu 1460

router   ps4      result
1492     1492   lag,delay
1460     1460   lag,delay
auto      auto    lag,delay
1492     1473   lag,delay
1460     1473   lag,delay

friend network sky:
http://www.speedguide.net SG TCP/IP Analyzer mtu 1500

router    ps4     result
1500      1500  excellent
1500      auto   excellent
1500      1473  excellent,brilliant

[kitz]

@kitz, sorry I have same test to do, but I do not think roberto understands, and missed the tracert

Possibly so, the last test still indicates a test over the full route to speedguide.net.


@roberto - What we are trying to suggest is a test which eliminates all external routing and takes it back to the ISP gateway. 

Having performed the tracert to the BBC, we can now see that your ISP gateway is 212.69.63.47
What you need to do then is run the command on this gateway to find the max packet size between you and your ISP eg

ping -f -l [packet size] 212.69.63.47

We are attempting to find the maximum packet size between you and your ISP to see if it is ISP related. If you test with various packet sizes to find the max size, thus the MTU can be calculated.

John also suggested you could run it on your router, this way we can find out the point whereby MTU becomes the issue.