MrRCS também já tive a trabalhar com o vista e ele faz a mesma coisa , mas mesmo assim o sapo tem que dar suporte ao IPV6 senão nem sequer obtinhamos IP.
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:????:????:1c15:2537:aa0f:94a0(Preferred)
Link-local IPv6 Address . . . . . : fe80::1c15:2537:aa0f:94a0%13(Preferred)
Tecnologia: ADSL
Velocidade Contratada: 16Mbps
Tamanho do Ficheiro de Testes: 16 MB
Data de Inicio: 2009-10-12 00:39:28
Data de Fim: 2009-10-12 00:39:40
Dados Transmitidos: 16385.55 KB
Tempo de Download: 11.658 seg.
Protocolo: IPv6
Largura de banda útil: 11.24 Mbps
Pode realizar downloads a 1.41 MB/sec.
traceroute to www.nfsi.pt (2001:b18::211:43ff:fecd:8c3c) from (***), 30 hops max, 16 byte packets
1 (***) 19.627 ms 18.432 ms 18.85 ms
2 2001:b18:0:1000::1 (2001:b18:0:1000::1) 18.929 ms 19.469 ms 19.03 ms
3 2001:b18::211:43ff:fecd:8c3c (2001:b18::211:43ff:fecd:8c3c) 19.796 ms 19.292 ms 19.808 ms
traceroute to maya.ipv6.telepac.pt (2001:8a0:10:200::2) from (***), 30 hops max, 16 byte packets
1 (***) 18.877 ms 18.883 ms 18.4 ms
2 2001:b18:0:1000::1 (2001:b18:0:1000::1) 19.423 ms 19.753 ms 19.301 ms
3 * * *
4 2001:8a0:10:1fb::2 (2001:8a0:10:1fb::2) 21.799 ms 21.522 ms 22.069 ms
5 2001:8a0:10:1ff:: (2001:8a0:10:1ff: 25.411 ms 25.211 ms 24.525 ms
6 2001:8a0:10:200::2 (2001:8a0:10:200::2) 27.093 ms 26.689 ms 25.225 ms
traceroute to ipv6.l.google.com (2001:4860:a005::68) from (***), 30 hops max, 16 byte packets
1 (***) 19.666 ms 19.248 ms 18.851 ms
2 2001:b18:0:1000::1 (2001:b18:0:1000::1) 20.238 ms 19.222 ms 19.257 ms
3 2001:b18:0:1::11 (2001:b18:0:1::11) 19.758 ms 19.59 ms 19.284 ms
4 google.ipv6.panap.fr (2001:860:0:6:0:1:5169:1) 61.217 ms 61.205 ms 61.121 ms
5 * * *
6 * * *
7 * * *
8 * * ey-in-x68.google.com (2001:4860:a005::68) 81.031 ms
traceroute to heanet.ie (2001:770:18:2::c101:db39) from (***), 30 hops max, 16 byte packets
1 (***) 18.275 ms 19.241 ms 19.058 ms
2 2001:b18:0:1000::1 (2001:b18:0:1000::1) 19.257 ms 19.716 ms 19.283 ms
3 2001:b18:0:1::11 (2001:b18:0:1::11) 19.513 ms 19.408 ms 19.876 ms
4 he.ipv6.panap.fr (2001:860:0:6::6939:1) 63.544 ms 63.587 ms 63.457 ms
5 10gigabitethernet1-3.core1.lon1.he.net (2001:470:0:42::1) 70.182 ms 72.276 ms 69.687 ms
6 2001:7f8:4::cb9:1 (2001:7f8:4::cb9:1) 77.591 ms 78.78 ms 77.949 ms
7 xe-8-0-0.lon20.ip6.tinet.net (2001:668:0:2::1:1301) 77.466 ms 78.009 ms 78.177 ms
8 xe-0-1-0.lon21.ip6.tinet.net (2001:668:0:2::1:511) 100.065 ms 78.679 ms 76.73 ms
9 ge-2-1-0.lon22.ip6.tinet.net (2001:668:0:2::1:301) 78.676 ms 76.619 ms 78.751 ms
10 so-1-1-0.dub20.ip6.tinet.net (2001:668:0:2::1:831) 89.681 ms 90.808 ms 90.744 ms
11 heanet-gw.ip6.tinet.net (2001:668:0:3::c000:72) 93.186 ms 91.988 ms 91.524 ms
12 te5-1-blanch-sr1.services.hea.net (2001:770:400:60::2) 91.02 ms 92.221 ms 91.764 ms
13 samhain.heanet.ie (2001:770:18:2::c101:db39) 91.398 ms 91.558 ms 92.211 ms
...
What happens when IPv4 addresses run out?
The simple answer is: not a lot. The Internet will continue to function mostly as it does before; you'll still be able to browse new sites, and so on. However, what will happen is that no new businesses can start up on the net, at least, without multi-hosting on an existing IP address. In short, it could be a slowdown in the Internet economy that has ballooned over the last decade.
There are those who claim that NAT will solve the shortage at the client side (which hides a set of non-routable addresses behind a signle globally routable IP address) - but even this has limits. Assuming each computer is actively connecting to around 25 outgoing ports simultaneously (not a difficult number to achieve with a few web pages open, the odd mail client and social networking application), combined with the fact that most NAT-level routers can only handle mappings for up to 50,000 ports at a time, means that at best, a globally routable IPv4 address can only field another 50k items.
Furthermore, NAT can't be used for servers or other websites which need to be connected; they can only be applied on the client connecting in side. Regardless of whether this solves the problem of an ever growing list of clients, once the IPv4 addresses run out there can be no new servers.
...
Mantém-te atento ao IPv6 world day.Alguma info acerca da situação actual do IPv6 em Portugal? Que operadores estão a implementar e em que fase de implementação estão/prazos estabelecidos?