Investigating the IPv6 teredo tunnelling capability and performance of internet clients

Authors:
Sebastian Zander;Lachlan L.H. Andrew;Grenville Armitage;Geoff Huston;George Michaelson
Affiliations:
Swinburne University of Technology, Melbourne, Australia;Swinburne University of Technology, Melbourne, Australia;Swinburne University of Technology, Melbourne, Australia;Asia Pacific Network Information Centre, Brisbane, Australia;Asia Pacific Network Information Centre, Brisbane, Australia
Venue:
ACM SIGCOMM Computer Communication Review
Year:
2012

Citing 7
Cited 1

Tunneling IPv6 through NAT with Teredo Mechanism

AINA '05 Proceedings of the 19th International Conference on Advanced Information Networking and Applications - Volume 2
Quantifying the Extent of IPv6 Deployment

PAM '09 Proceedings of the 10th International Conference on Passive and Active Network Measurement
Observations of IPv6 addresses

PAM'08 Proceedings of the 9th international conference on Passive and active network measurement
Deployment and performance evaluation of Teredo and ISATAP over real test-bed setup

Proceedings of the International Conference on Management of Emergent Digital EcoSystems
NAT usage in residential broadband networks

PAM'11 Proceedings of the 12th international conference on Passive and active measurement
Tracking IPv6 evolution: data we have and data we need

ACM SIGCOMM Computer Communication Review
Mitigating sampling error when measuring internet client IPv6 capabilities

Proceedings of the 2012 ACM conference on Internet measurement conference

Mitigating sampling error when measuring internet client IPv6 capabilities

Proceedings of the 2012 ACM conference on Internet measurement conference

Quantified Score

Hi-index	0.00

Visualization

Abstract

The Teredo auto-tunnelling protocol allows IPv6 hosts behind IPv4 NATs to communicate with other IPv6 hosts. It is enabled by default on Windows Vista and Windows 7. But Windows clients are self-constrained: if their only IPv6 access is Teredo, they are unable to resolve host names to IPv6 addresses. We use web-based measurements to investigate the (latent) Teredo capability of Internet clients, and the delay introduced by Teredo. We compare this with native IPv6 and 6to4 tunnelling capability and delay. We find that only 6--7% of connections are from fully IPv6-capable clients, but an additional 15--16% of connections are from clients that would be IPv6-capable if Windows Teredo was not constrained. However, Teredo increases the median latency to fetch objects by 1--1.5 seconds compared to IPv4 or native IPv6, even with an optimally located Teredo relay. Furthermore, in many cases Teredo fails to establish a tunnel.