Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Latency through ipv6 tunnel
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Latency through ipv6 tunnel
Latency through ipv6 tunnel
20-09-2008 11:17 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
As there's no native ipv6 with plusnet, I'm running an aviya tunnel through to SIXXS.
Noticing it got a bit slow each evening, I thought I'd graph it for a while:
There's not too many enabled right now, but if I hit an ipv6 site in the evening, the navigation is a little frustrating.
I'm assuming this is network management kicking in... any chance of bumping the priority of aviya tunnels up a bit?
Noticing it got a bit slow each evening, I thought I'd graph it for a while:
There's not too many enabled right now, but if I hit an ipv6 site in the evening, the navigation is a little frustrating.
I'm assuming this is network management kicking in... any chance of bumping the priority of aviya tunnels up a bit?
Message 1 of 7
(1,715 Views)
6 REPLIES 6
Re: Latency through ipv6 tunnel
20-09-2008 11:36 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Can you do a trace through the tunnel and one in the clear please when you see these slow downs?
Is that possible for you to do?
Is that possible for you to do?
Message 2 of 7
(633 Views)
Re: Latency through ipv6 tunnel
20-09-2008 1:17 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Can do - won't be in tonight when it slows down, so I've just started recording a few things every 5 minutes:
traceroute6 www.sixxs.net
traceroute www.sixxs.net
traceroute6 2a01:348:6:12b::1 (tunnel endpoint - what's being graphed above)
traceroute gblon02.sixxs.net (ipv4 endpoint of the tunnel)
Let me know if you need anything else and I'll add it in.
traceroute6 www.sixxs.net
traceroute www.sixxs.net
traceroute6 2a01:348:6:12b::1 (tunnel endpoint - what's being graphed above)
traceroute gblon02.sixxs.net (ipv4 endpoint of the tunnel)
Let me know if you need anything else and I'll add it in.
Message 3 of 7
(633 Views)
Re: Latency through ipv6 tunnel
21-09-2008 1:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
OK, got some from lastnight, the following were all at 00:05:
traceroute to www.m.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2a01:348:6:12b::2, 30 hops max, 16 byte packets
1 * gw-300.lon-02.gb.sixxs.net (2a01:348:6:12b::1) 2521.74 ms 2927.01 ms
2 ae0-1235.rt2.the.uk.goscomb.net (2a01:348:0:4:0:3:0:1) 3007.38 ms 3306.99 ms 4201.29 ms
3 ge-0-0-0-1368.rt1.nik.nl.goscomb.net (2a01:348::10:1:1) 4435.88 ms 4506.71 ms 4551.8 ms
4 * ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 2540.8 ms 2061.62 ms
5 2001:838:0:13::1 (2001:838:0:13::1) 1778.17 ms 2088.61 ms 2558.86 ms
6 2001:838:0:12::2 (2001:838:0:12::2) 2203.32 ms 2310.85 ms 2701.73 ms
7 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 2997.8 ms 2982.38 ms 2639.79 ms
traceroute: Warning: www.sixxs.net has multiple addresses; using 193.109.122.244
traceroute to www.m.sixxs.net (193.109.122.244), 30 hops max, 40 byte packets
1 10.2.10.2 (10.2.10.2) 1.078 ms 1.049 ms 0.963 ms
2 lo0.plusnet.thn-ag1.plus.net (195.166.128.101) 33.221 ms 34.909 ms 35.163 ms
3 vl703.thn-gw1.plus.net (84.92.4.241) 33.357 ms 39.160 ms 35.335 ms
4 195.66.226.185 (195.66.226.185) 36.683 ms 35.401 ms 35.371 ms
5 te8-7.ccr01.ams03.atlas.cogentco.com (130.117.0.197) 43.778 ms 43.600 ms 41.189 ms
6 vl3490.mpd01.ams03.atlas.cogentco.com (130.117.3.106) 46.975 ms 42.207 ms 48.659 ms
7 cogent-1101.xe-0-0-0.jun1.kelvin.network.bit.nl (149.6.128.154) 42.322 ms 48.057 ms 44.011 ms
8 nlede01.sixxs.net (193.109.122.244) 45.969 ms 52.570 ms 43.139 ms
traceroute to 2a01:348:6:12b::1 (2a01:348:6:12b::1) from 2a01:348:6:12b::2, 30 hops max, 16 byte packets
1 gw-300.lon-02.gb.sixxs.net (2a01:348:6:12b::1) 2169.6 ms 2227.38 ms 2316.1 ms
traceroute to gblon02.sixxs.net (77.75.104.126), 30 hops max, 40 byte packets
1 10.2.10.2 (10.2.10.2) 1.036 ms 0.973 ms 0.950 ms
2 lo0.plusnet.thn-ag1.plus.net (195.166.128.101) 34.105 ms 38.506 ms 35.297 ms
3 vl703.thn-gw1.plus.net (84.92.4.241) 36.803 ms 36.026 ms 39.832 ms
4 ae0-461.rt0.sov.uk.goscomb.net (195.66.226.226) 34.780 ms 35.768 ms 37.849 ms
5 ae0-1624.rt2.the.uk.goscomb.net (77.75.109.161) 37.601 ms 35.388 ms 35.664 ms
6 gblon02.sixxs.net (77.75.104.126) 35.239 ms 36.579 ms 34.321 ms
Message 4 of 7
(633 Views)
Re: Latency through ipv6 tunnel
22-09-2008 6:18 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi James.
Yip prettly high response times evident there through the tunnel.
Can I ask what port (s) you are using for the Avaya client?
If it is not a standard VPN port is it possible for you to change this?
I've looked at the Avaya support info and trying to get a handle on which port (s) it uses is not proving to be easy.
I want to ensure that our traffic management is correctly identifying the ports in use as VPN, providing they are in the standard VPN range that is
Alernatively, a Wireshark capture of the traffic might help identify its classification.
Yip prettly high response times evident there through the tunnel.
Can I ask what port (s) you are using for the Avaya client?
If it is not a standard VPN port is it possible for you to change this?
I've looked at the Avaya support info and trying to get a handle on which port (s) it uses is not proving to be easy.
I want to ensure that our traffic management is correctly identifying the ports in use as VPN, providing they are in the standard VPN range that is
Alernatively, a Wireshark capture of the traffic might help identify its classification.
Message 5 of 7
(633 Views)
Re: Latency through ipv6 tunnel
23-09-2008 5:57 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Oops, it's ayiya, not aviya... and nothing atall to do with avaya. lol
All open, so plenty of documentation:
http://www.sixxs.net/tools/ayiya/
I could get you a capture, but I should imagine the draft will be easier to interpret...
All open, so plenty of documentation:
http://www.sixxs.net/tools/ayiya/
I could get you a capture, but I should imagine the draft will be easier to interpret...
Message 6 of 7
(633 Views)
Re: Latency through ipv6 tunnel
23-09-2008 8:54 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Doh. I need to learn to read properly.
Thats much more to go on. I'll get someone to take a look at this tomorrow.
Thats much more to go on. I'll get someone to take a look at this tomorrow.
Message 7 of 7
(633 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Latency through ipv6 tunnel