Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: IPv6 vs IPv4 ping times  (Read 733 times)

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6086
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
IPv6 vs IPv4 ping times
« on: April 19, 2018, 04:30:39 AM »

My router, a Firebrick, can be asked to do a ping or traceroute itself. I decided to try this out as I was wondering about another way of checking how much delay the wireless LAN with WPA2 crypto adds when my iPad is using it to talk to a node on the wired LAN or wider internet.

From with the Firebrick, I ipv6-pinged bottomless.aa.net.uk which happens to be my first IP-visible hop after leaving the house, anyway it is the entry point to my ISP AA’s network. I noticed that when I ping the corresponding address 81.187.81.187 from the FB I get a ping time about 9ms less than IPv6. It's about 38-41ms for IPv4 and 47-49ms for IPv6 (2001:8b0:0:81::51bb:51bb).

So why is IPv6 taking 24% longer than IPv4?

Things I checked: I checked the visible hop counts, both are one IP hop. Can't see what is going on underneath though. It's all IPv6 inside PPP in this case so you might hope that the intermediate nodes don't care too much. I also checked for packet length effects by adding 20 more bytes on to the length of the IPv4 ping packets, 128 bytes for ipv6 and both 128 and 128+20 for IPv4. I'm not sure what it meant by ping 'length' whether that was including headers (which) or not. But it made no difference.

Weird.
« Last Edit: April 19, 2018, 06:30:58 AM by Weaver »
Logged

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 1038
Re: IPv6 vs IPv4 ping times
« Reply #1 on: April 19, 2018, 09:24:51 AM »

From my router:

PING bottomless.aa.net.uk (2001:8b0:0:81::51bb:51bb): 56 data bytes
64 bytes from 2001:8b0:0:81::51bb:51bb: seq=0 ttl=63 time=11.234 ms
64 bytes from 2001:8b0:0:81::51bb:51bb: seq=1 ttl=63 time=11.081 ms
64 bytes from 2001:8b0:0:81::51bb:51bb: seq=2 ttl=63 time=11.262 ms
64 bytes from 2001:8b0:0:81::51bb:51bb: seq=3 ttl=63 time=11.431 ms

--- bottomless.aa.net.uk ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 11.081/11.252/11.431 ms


PING bottomless.aa.net.uk (81.187.81.187): 56 data bytes
64 bytes from 81.187.81.187: seq=0 ttl=64 time=12.220 ms
64 bytes from 81.187.81.187: seq=1 ttl=64 time=10.423 ms
64 bytes from 81.187.81.187: seq=2 ttl=64 time=12.867 ms
64 bytes from 81.187.81.187: seq=3 ttl=64 time=10.439 ms

--- bottomless.aa.net.uk ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.423/11.487/12.867 ms


You could try connecting a PPPoE session direct from a PC to one of your lines to determine if it is a characteristic of the router or your line.
« Last Edit: April 19, 2018, 09:28:03 AM by jelv »
Logged
Line rental: Pulse8, Broadband: AAISP Home::1 FTTC 80/20, Mobile: id Mobile

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 5416
Re: IPv6 vs IPv4 ping times
« Reply #2 on: April 19, 2018, 04:23:34 PM »

ipv4 vs ipv6 can go over different peering/transit links, in terms of raw processing speed, at least on consumer equipment ipv6 should be faster because it doesnt have NAT as a requirement, although been on aaisp with your own ipv4 block its possible you not using NAT for your ipv4.

I have had times ipv4 is lower latency to the bbc than ipv6, and I have had times its the other way round. Right now ipv6 is quicker to the bbc for me.  Note this is just to the bbc, to another destination it may be the other way round, and yes currently on this machine ipv4 is preferenced.

Code: [Select]
F:\Users\Chris\Downloads\NEW\undefined\hashcat-3.6.0>ping bbc.co.uk

Pinging bbc.co.uk [151.101.0.81] with 32 bytes of data:
Reply from 151.101.0.81: bytes=32 time=9ms TTL=60
Reply from 151.101.0.81: bytes=32 time=9ms TTL=60
Reply from 151.101.0.81: bytes=32 time=9ms TTL=60
Reply from 151.101.0.81: bytes=32 time=9ms TTL=60

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

F:\Users\Chris\Downloads\NEW\undefined\hashcat-3.6.0>ping -6 bbc.co.uk

Pinging bbc.co.uk [2a04:4e42:600::81] with 32 bytes of data:
Reply from 2a04:4e42:600::81: time=6ms
Reply from 2a04:4e42:600::81: time=6ms
Reply from 2a04:4e42:600::81: time=7ms
Reply from 2a04:4e42:600::81: time=6ms

Ping statistics for 2a04:4e42:600::81:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 7ms, Average = 6ms
« Last Edit: April 19, 2018, 04:26:08 PM by Chrysalis »
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab - LINE STATISTICS CLICK HERE

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 1038
Re: IPv6 vs IPv4 ping times
« Reply #3 on: April 19, 2018, 04:51:54 PM »

Interesting! www.bbc.co.uk does not have an IPv6 address but bbc.co.uk does. When I try to visit http[s]://bbc.co.uk it redirects to https://www.bbc.co.uk so although there is an IPv6 address it can't be used.

I have a browser add-on that shows 4 or 6 so I was surprised when I saw your post as all I ever see when using any part of the BBC site is 4. That's why I starting digging.
Logged
Line rental: Pulse8, Broadband: AAISP Home::1 FTTC 80/20, Mobile: id Mobile

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 5416
Re: IPv6 vs IPv4 ping times
« Reply #4 on: April 19, 2018, 08:02:41 PM »

yeah is bit of an oddity, possibly a config error on their part.

I cant fully duplicate your guys tests with sky, it seems sky's internal routing changes based on ip address versioning.
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab - LINE STATISTICS CLICK HERE

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6086
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: IPv6 vs IPv4 ping times
« Reply #5 on: April 19, 2018, 08:21:50 PM »

Weirder. What is the difference between jelv's setup and mine?

I have three very slow ADSL2 lines with DLink DSL-320b-Z1 PPPoEoA modems connected to my firebrick.

To me, 9ms is a lot of time by the standards if these things and I am finding it difficult to think of things that could explain such a (relatively) large delay. I wonder if it is in the brick, in BT-land or in AA-land or even in the actual turnaround responsiveness of bottomless.
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6086
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: IPv6 vs IPv4 ping times
« Reply #6 on: April 19, 2018, 08:25:38 PM »

@Chrysalis say traceroute to your isp's dns servers. Then pick the nodes that are closest to you and try ping ipv4 vs ping ipv6 comparison.
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 5416
Re: IPv6 vs IPv4 ping times
« Reply #7 on: April 19, 2018, 09:55:22 PM »

Weaver my closest visible hop on ipv6 is 7ms, for ipv4 is 10ms. If thats what you mean.

 2     7 ms     7 ms     7 ms  2a01:4a0:1338:8b::1

  2    10 ms    10 ms    10 ms  be377.pr3.hobir.isp.sky.com [2.120.8.66]
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab - LINE STATISTICS CLICK HERE

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 1038
Re: IPv6 vs IPv4 ping times
« Reply #8 on: April 19, 2018, 11:06:43 PM »

I may have a better ping, but do you see the regular packet loss I see on IPv6 that is not on IPv4?



Logged
Line rental: Pulse8, Broadband: AAISP Home::1 FTTC 80/20, Mobile: id Mobile

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 5416
Re: IPv6 vs IPv4 ping times
« Reply #9 on: April 20, 2018, 12:53:56 AM »

I do, and last time I checked (week or so ago) I had packet loss on ipv6 tbb, which is what triggered me to preference ipv4 traffic as I had little time to diagnose it further.

I did confirm tho that the packet loss was not showing on my smokeping from hetzner in germany.

In my case it wasnt spread out over the entire day, just a few packet loss spikes at peak hours.
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab - LINE STATISTICS CLICK HERE

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6086
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: IPv6 vs IPv4 ping times
« Reply #10 on: April 21, 2018, 03:02:25 AM »

Chrys do you think there is a chance that the close ipv6 and close ipv4 addresses specified are in fact attached to the same box? PTR-lookup may or may not help.

Whatever it's very interesting that you get a 43% difference but in the other direction compared to me, in favour of ipv6. I would be interested to see if this remains true for the nodes slightly further upstream, further away from you, as mentioned before if you locate some such nodes with a traceroute to somewhere such as to the isp's dns servers because it must be ‘close’.
« Last Edit: April 21, 2018, 02:42:29 PM by Weaver »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 5416
Re: IPv6 vs IPv4 ping times
« Reply #11 on: April 21, 2018, 04:34:26 AM »

I got no idea but i do know my ipv4 and ipv6 performance metrics dont always match e.g. last week I had packet loss during peak times on ipv6 but not on ipv4.  So on skys network the routing of both is not the same.

In regards to this 43%, no it doesnt stay like that over higher distances so e.g. a 300ms latency wouldnt jump 43% between different protocols.
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab - LINE STATISTICS CLICK HERE
 

anything