[ipv6-wg at ripe.net] Actual IPv6 traffic
- Previous message (by thread): [ipv6-wg at ripe.net] Agenda for ipv6 wg RIPE48 (updated)
- Next message (by thread): [ipv6-wg at ripe.net] Actual IPv6 traffic
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Tue May 4 10:18:06 CEST 2004
From the agenda: > C. Report(s) about *actual* v6 traffic volume as compared to v4? > *what's real* out there, not what's on powerpoint? > (input from the audience) My input in advance: I've been running some web measurements using a small image that can be linked on web pages to see whether the visitors are v6-capable or not. (The host that has the image has an IPv6 address and notes whether the image is requested over v4 or v6.) The results over the past months: Site IPv4 IPv6 Total 0 151 ( 98.05%) 3 ( 1.95%) 154 3 334 ( 94.35%) 20 ( 5.65%) 354 6 1355 ( 82.02%) 297 ( 17.98%) 1652 7 57 ( 75.00%) 19 ( 25.00%) 76 8 20107 ( 99.85%) 31 ( 0.15%) 20138 10 2918 ( 84.43%) 538 ( 15.57%) 3456 Totals 24925 ( 96.49%) 908 ( 3.51%) 25833 Note that the numbers refer to different sites with very different usage and IPv6 interest levels. Only number 8 is a very mainstream non-networking site (in Dutch) so I think this one represents average IPv6 capability for the web surfing public fairly well, at around 1 user in 666 requesting the counter image over IPv6. :-) See http://www.muada.com/ to see the counter in action and for a link to the results page. (BTW, it would help if someone would type sysctl -w net.inet6.ip6.forwarding=1 on router.ripemtg.ripe.net, or, failing that, kill the rtadvd.)
- Previous message (by thread): [ipv6-wg at ripe.net] Agenda for ipv6 wg RIPE48 (updated)
- Next message (by thread): [ipv6-wg at ripe.net] Actual IPv6 traffic
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]