Print

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

[ejs]

All IDNet connections come with a static IPv4 address and static IPv6 addresses (native /48)

Perhaps enabling IPv6 on your router might give a better connection.

[d2d4j]

Hi

@ejs good call for IPv6

@roberto can you post a tracert to speedguide.net, then ping -f -l each hop IP address to show where it first drops mtu to 1460

Please set your mtu on router/pc to 1464 (1492 total, which is dsl pppoe)

Many thanks

John

[roberto2212]

ok I will do this tomorrow..and you mean manually mtu on router 1464 and pc network adapter 1464?..and also when I ordered new broadband two month ago I just received only ipv4 settings from idnet no ipv6.And anyway I m  not sure that ps4  support ipv6.

[niemand]

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. 

The DSLAMs do somewhat more than that. By the time the data leaves the DSLAM heading to the exchange it is inside a potentially Q-in-Q Ethernet frame. This carries a maximum frame size and hence a maximum unfragmented IP packet size. The size of the frame leaving depends on the one arriving from the customer. The DSLAM adds its own VLAN tags per configuration  and sends the frame on its way.

2.1.2 Ethernet Frame Size
The maximum supported Ethernet frame size is 1530 bytes (excluding IFG and pre-amble and single/double tag – see 2.1.3).

So a misconfiguration is possible, if unlikely. I also don't think it would cause these issues. Routers generate ICMP unreachable messages, switches just drop traffic if the frame is too large.

Apologies if you already knew this but you gave the impression the DSLAM was just a really big box of modems, when it's a fully fledged router.

Like most kit of that type now it's an edge router with access line cards in it to terminate the ADSL / VDSL / PON / PtP connections going into it, running an OS built with edge/access router duty in mind. Openreach have to run it in bridge mode for obvious reasons.

[niemand]

This issue strikes me as a problem with the Billion's firmware or configuration. Almost like there's a TCP adjust-mss like command in there.

[roberto2212]

@roberto can you post a tracert to speedguide.net, then ping -f -l each hop IP address to show where it first drops mtu to 1460

im really dont understand "  then ping -f -l each hop IP address to show where it first drops mtu to 1460" because if I set router to 1464 plus pc to 1464 then 1436 will pass and 1437 need fragmented because 1464-28=1436


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

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
  1464                1     809985     234178  Ethernet
4294967295                1          0       9300  Loopback Pseudo-Interface 1


C:\Windows\system32>tracert speedguide.net

Tracing route to speedguide.net [68.67.73.20]
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]
  3    12 ms    12 ms    11 ms  telehouse-gw8-v523.idnet.net [212.69.63.82]
  4    12 ms    12 ms    12 ms  telehouse-gw7-v505.idnet.net [212.69.63.72]
  5    12 ms    12 ms    12 ms  gi4-42-75-idnet.bdr-rt3.thdo.ncuk.net [80.249.97.109]
  6    12 ms    12 ms    12 ms  tge2-1-506.edge1.lon2.uk.as5580.net [195.66.237.111]
  7   116 ms   103 ms   103 ms  eth1-1.r1.jax1.us.as5580.net [78.152.35.222]
  8   103 ms   103 ms   103 ms  80.94.66.157
  9     *        *        *     Request timed out.
 10   103 ms   103 ms   103 ms  23.92.92.82
 11   105 ms   102 ms   102 ms  te-4-1-1131-40g-east.core-a.jcvnflcq.jax.as19844.net [216.238.150.207]
 12   103 ms   103 ms   103 ms  ve101.e15-1.dist-a.jcvnflcq.as19844.net [198.205.127.6]
 13   104 ms   104 ms   104 ms  speedguide.net [68.67.73.20]

Trace complete.

C:\Windows\system32>ping -f -l 1460 192.168.1.1

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

C:\Windows\system32>ping -f -l 1436 192.168.1.1

Pinging 192.168.1.1 with 1436 bytes of data:
Reply from 192.168.1.1: bytes=1436 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1436 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1436 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1436 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 1437 192.168.1.1

Pinging 192.168.1.1 with 1437 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),
 for billion router I using this firmware BiPAC 8800NL 2.32d.dh14 firmware and also I tryed 8800NL 2.32e firmware..still same problem..tryed on bridge mode and also on route mode with pppoe wan setup.
source : http://www.billion.uk.com/esupport/index.php?/Knowledgebase/List/Index/107/bipac-8800nl

[ejs]

Leave the router MTU set to 1492 and the PC MTU set to 1500.

[d2d4j]

Hi

Sorry, I may not have been fully clear

As ejs posted, set router to mtu 1492 and pc at 1500

Restart router and pc, then please post a ping -f -l 1472 192.168.1.1

Many thanks

John

[roberto2212]

So I change mtu on router to 1492 + pc network adapter to 1500
On speedguide again mtu=1460

Test:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

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

   MTU  MediaSenseState   Bytes In  Bytes Out  Interface
------  ---------------  ---------  ---------  -------------
  1500                1    1776515     635009  Ethernet
4294967295                1          0      18024  Loopback Pseudo-Interface 1


C:\Windows\system32>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<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 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 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),

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

Pinging www.bbc.net.uk [212.58.244.68] with 1472 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.58.244.68:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

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

Pinging www.bbc.net.uk [212.58.244.68] 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.58.244.68:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

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

Pinging www.bbc.net.uk [212.58.244.68] with 1464 bytes of data:
Reply from 212.58.244.68: bytes=1464 time=14ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=14ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=14ms TTL=57
Reply from 212.58.244.68: bytes=1464 time=14ms 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 = 14ms, Average = 14ms


[attachment deleted by admin]

[ejs]

Although unusual, I think the value reported by speedguide.net really does not matter.

[roberto2212]

Then ejs please explain me why ps4 online gaming still laging and I got delay?If on sky worked perfect.I did all the same, I put static ip ps4 to dmz on sky hub on ps4 static ip, mtu auto,played 7 game a row and no lag or delay.On my connection again put static ip to dmz linksys router then on ps4 static ip plus mtu auto.Played 7 game a row with lag and delay.really frustrated and unplayable.Change mtu to 1492 or 1500 etc..No different always got delay.Tryed change router still same problem.Checked dmz if working by portforwarding utillies all ports opened.So where is problem then?Replaced all cable for new one no help.

[d2d4j]

Hi

@ejs could be

@roberto please do not change any equipment or settings

Can you now run same ping test to all ip addresses to speedguide.net from tracert

ping -f -l 1472 192.168.1.1

Etc and post result

This should find where your mtu is been lowered to 1460 but if result tests fine, it could be as ejs has posted

Please use a hardwired connection from pc to router, which I believe you have

There is 1 thing which I have not mentioned, and will do so after you post your full ping test on all ip addresses from speedguide tracert

Also, please do not panic or jump to conclusions if 1 or more ping do not respond, just post the result

Many thanks

John

[ejs]

Perhaps Sky is a better ISP for gaming than IDNet. I think IDNet is mainly aimed at businesses.

198.205.127.6 does not reply to me to ping packets larger than 1458 bytes, but speedguide.net itself still replies to 1500 byte ping packets.

[roberto2212]

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert www.speedguide.net

Tracing route to www.speedguide.net [68.67.73.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Linksys00463-h [192.168.1.1]
  2    13 ms    12 ms    12 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    13 ms    12 ms    12 ms  telehouse-gw8-v522.idnet.net [212.69.63.80]
  4    13 ms    12 ms    12 ms  telehouse-gw7-v505.idnet.net [212.69.63.72]
  5    12 ms    13 ms    12 ms  gi4-42-75-idnet.bdr-rt3.thdo.ncuk.net [80.249.97.1
  6    13 ms    12 ms    12 ms  tge2-1-506.edge1.lon2.uk.as5580.net [195.66.237.11
  7   107 ms   103 ms   103 ms  eth1-1.r1.jax1.us.as5580.net [78.152.35.222]
  8   103 ms   103 ms   103 ms  80.94.66.157
  9     *        *        *     Request timed out.
 10   104 ms   103 ms   104 ms  23.92.92.82
 11   112 ms   103 ms   103 ms  te-4-1-1131-40g-east.core-a.jcvnflcq.jax.as19844.n
 12   104 ms   104 ms   104 ms  ve101.e15-1.dist-a.jcvnflcq.as19844.net [198.205.1
 13   104 ms   104 ms   104 ms  speedguide.net [68.67.73.20]

Trace complete.

C:\Windows\system32>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<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.1: bytes=1472 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 1472 212.69.63.51

Pinging 212.69.63.51 with 1472 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.51:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 212.69.63.80

Pinging 212.69.63.80 with 1472 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.80:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 212.69.63.72

Pinging 212.69.63.72 with 1472 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.72:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 80.249.97.109

Pinging 80.249.97.109 with 1472 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 80.249.97.109:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 195.66.237.111

Pinging 195.66.237.111 with 1472 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 195.66.237.111:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 78.152.35.222

Pinging 78.152.35.222 with 1472 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 78.152.35.222:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 80.94.66.157

Pinging 80.94.66.157 with 1472 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 80.94.66.157:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 23.92.92.82

Pinging 23.92.92.82 with 1472 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 23.92.92.82:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 216.238.150.207

Pinging 216.238.150.207 with 1472 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 216.238.150.207:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 198.205.127.6

Pinging 198.205.127.6 with 1472 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 198.205.127.6:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping -f -l 1472 68.67.73.20

Pinging 68.67.73.20 with 1472 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 68.67.73.20:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

[roberto2212]

ejs
Perhaps Sky is a better ISP for gaming than IDNet. I think IDNet is mainly aimed at businesses.

With idnet I get better speed and ping and also I pay extra money for high trafic priority,So should be better like sky.I pay for 80/20 and I get 75/19 with ping 12.So for online gaming should be fine.