Windows 8.1 prefers IPv4 over IPv6

Hi,
I face a strange issue regarding IPv6 networking on Windows 8.1 Pro. My local network runs a router with router advertising daemon to announce fc00::/7 unique local address as well as global adresses. It also runs DHCPv6 to assign static unique local address.
So all my machines in local LAN get multiple local IPv6 addresses:
IPv6 DHCP lease in fc00::/7 network
Auto-assigned IPv6 fc00::/7 address
Temporary IPv6 fec00::/7 address
Link-local IPv6 address in range fe80::64 network
Temporary global unicast IPv6 2000::/3 address
Link-local IPv6 fe80::/10 address
DHCP-assigned 10.0.0.0/8 IPv4 address
DNS servers: fc00::/7 IPv6 and 10.0.0.0/8 (same server with DNS listening on both interfaces)
Gateway: Link-local IPv6 fe80::/10 address of router, 10.0.0.0/8 server (same host as IPv6 gateway)
So far almost everything seems to work well:
Can ping and connect to IPv6-enabled web-hosts
ping www.google.com pings IPv6 interface on Google server
However Windows 8.1 decides to connect on IPv4 only local servers. E.g. the local web-service. Issuing "ping local-server" pings IPv4 only as well as Internet Explorer or Firefox only connect on IPv4 to the web service. It's not a DNS issue as
DNS resolves properly to link-local IPv6 address:
nslookup local-server
Server: UnKnown
Address: fdea:....:....:....::6
Name: local-server.example.local
Addresses: fdea:....:....:....::6
10.0.1.6
Also using the IP address within the browser like http://[fdea:....:....:....::6]/ works just fine.
Even more strange the same setup on Windows 7 Professional connects just fine to the same host on IPv6.
I thought this might be an issue with prefix policies (see 'netsh interface ipv6 show prefixpolicies') which were changed from Windows 7 to Windows 8(.1). But I messed with the rules at no avail.
Any explanation or hint what I am doing wrong or what has changed in Windows 8(.1) which makes Windows 8 prefer IPv4 over unique local fec0::/7 addresses?

you can run ipconfig /all, and paste the result here
Of course I can. See below. Note: I have removed static IPv6 site-local addresses (except the prefix).
Windows IP Configuration
Host Name . . . . . . . . . . . . : cyb64w8-hpnb
Primary Dns Suffix . . . . . . . : cyberdyne.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cyberdyne.local
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : cyberdyne.local
Description . . . . . . . . . . . : Intel(R) 82566MM Gigabit Network Connection
Physical Address. . . . . . . . . : 00-1A-4B-79-B0-18
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:120b:2c1a:9921:xxxx:xxxx:xxxx:xxxx(Preferred)
IPv6 Address. . . . . . . . . . . : fdea:5b48:d4c1:1:xxxx:xxxx:xxxx:xxxx(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:120b:2c1a:9921:b961:891b:ca9a:57c4(Preferred)
Temporary IPv6 Address. . . . . . : fdea:5b48:d4c1:1:b961:891b:ca9a:57c4(Preferred)
Link-local IPv6 Address . . . . . : fe80::d22:54df:c40d:50b0%3(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.1.186(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Dienstag, 24. Dezember 2013 15:16:03
Lease Expires . . . . . . . . . . : Donnerstag, 26. Dezember 2013 15:16:00
Default Gateway . . . . . . . . . : fe80::21f:d0ff:fe59:1baf%3
10.0.1.6
DHCP Server . . . . . . . . . . . : 10.0.1.6
DHCPv6 IAID . . . . . . . . . . . : 50338379
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-F3-54-E5-00-1A-4B-79-B0-18
DNS Servers . . . . . . . . . . . : 10.0.1.6
Primary WINS Server . . . . . . . : 10.0.1.6
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : cyberdyne.local
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-13-E8-E7-CD-41
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:120b:2c1a:9921:xxxx:xxxx:xxxx:xxxx(Preferred)
IPv6 Address. . . . . . . . . . . : fdea:5b48:d4c1:1:xxxx:xxxx:xxxx:xxxx(Preferred)
Lease Obtained. . . . . . . . . . : Dienstag, 24. Dezember 2013 15:15:59
Lease Expires . . . . . . . . . . : Donnerstag, 16. Januar 2014 21:23:54
IPv6 Address. . . . . . . . . . . : fdea:5b48:d4c1:1:448c:d39d:146a:8a10(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:120b:2c1a:9921:31a1:a957:a32a:3fd9(Preferred)
Temporary IPv6 Address. . . . . . : fdea:5b48:d4c1:1:31a1:a957:a32a:3fd9(Preferred)
Link-local IPv6 Address . . . . . : fe80::448c:d39d:146a:8a10%4(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.1.210(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Dienstag, 24. Dezember 2013 15:15:57
Lease Expires . . . . . . . . . . : Donnerstag, 26. Dezember 2013 15:15:57
Default Gateway . . . . . . . . . : fe80::21f:d0ff:fe59:1baf%4
10.0.1.6
DHCP Server . . . . . . . . . . . : 10.0.1.6
DHCPv6 IAID . . . . . . . . . . . : 67113960
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-F3-54-E5-00-1A-4B-79-B0-18
DNS Servers . . . . . . . . . . . : fdea:5b48:d4c1:1:1::6
10.0.1.6
Primary WINS Server . . . . . . . : 10.0.1.6
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
cyberdyne.local
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : cyberdyne.local
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-22-25-F2-4A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
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:5ef5:79fb:e8:c8c:f5ff:fe45(Preferred)
Link-local IPv6 Address . . . . . : fe80::e8:c8c:f5ff:fe45%6(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 218103808
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-F3-54-E5-00-1A-4B-79-B0-18
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.cyberdyne.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : cyberdyne.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Similar Messages

Prefer IPv4 over IPv6

Hi. I want use ipv4 before ipv6. For 2008 R2 i used fix "Microsoft Fix it 50410"
But this not support server 2012.
How i can correct change prefer on 2012?
Thank you!

Please, tell me, WHY man, who create IPv6 began use this fe80::6c02:573b:178c:dd8f naming.
Blame that on the Internet Engineering Task Force (IETF) standards committee that came up with this naming convention back in 1998 (http://tools.ietf.org/html/rfc2460). <grin>
Not sure what you mean by "reliable source with describe 'native IPv6 for 8\12'". Microsoft has lots of documentation on IPv6 - I think the majority of it came out with Windows Server 2008 because that was the first release with the dual-stack as a
default. IpV6 was available for Windows Server 2003, but it was an add-on. Go to Barnesandnoble.com or amazon.com to find a good reference book on IPv6 if you want to learn more - they are not small books. It is the way the industry is moving
because it offers many advantages over IPv4 (which, by the way, has officially run out of addresses which can be handed out). Microsoft is simply helping customers move into future by providing a dual-stack that can automatically switch back and forth
between IPv4 applications and IPv6 applications without the end-user even knowing it goes on. Some things, like Direct Access, would be almost impossible to implement on IPv4, but becomes (relatively) easy when using IPv6.
tim

Best way to pass IPv4 and IPv6 traffic over a GRE Tunnel

Hello,
We have two 3825 routers with Advanced Enterprise IOS 12.4.9(T). Each of them serves many IPv4 (private and public) and IPv6 networks on their respective site.
We have created a wireless link between the two, using 4 wireless devices, with IP Addresses 10.10.2.2, 3, 4, 5 respectively (1 and 6 are the two end Ethernet interfaces on the routers).
Then we created a GRE tunnel over this link using addresses 172.16.1.1 and 2 (for the two ends) to route traffic over this link.
Now we want to route IPv6 traffic over the same link. However, we found that simply routing the IPv6 traffic over the above GRE / IP tunnel did not work.
Questions:
Is there a way we can use the same (GRE / IP) tunnel to transport both IPv4 and IPv6 traffic?
If not, can we setup two GRE tunnels over the same wireless link, that is, one GRE / IP for IPv4 traffic and a second one GRE / IPv6 for IPv6 traffic?
In brief, what is the suggested way to transport IPv4 and IPv6 traffic over the aforementioned (wireless) link?
I have read http://www.cisco.com/c/en/us/td/docs/ios/12_4/interface/configuration/guide/inb_tun.html#wp1061361 and other Internet material, however I am still confused.
Please help.
Thanks in advance,
Nick

We have set up two tunnels over the same link, one GRE / IP for the IPv4 traffic and one IPv6 / IP ("manual") for the IPv6 traffic. This setup seems to be working OK.
If there are other suggestions, please advise.
Thanks,
Nick

Unexpected case IPv4 tunnel over IPv6 ?

hi,
I wonder if there is one use case one can think of that is not possible with Cisco IOS:
Establish a IPsec tunnel over an IPv6 network tranporting both IPv4 and Ipv6 traffic. Even IPsec tunnel over an IPv6 network transporting IPv4 only does not work.
I tried several things in my lab but couldn't get it running.
I tried to search the net for my use case but I only find the other way round.
Question: is it possible to achieve connectivity of the following IPv4 addresses over an IIPsec tunnel over Ipv6 network?
Ultimately, the same tunnel should be capable transporting both. A dedicated Tunnel for IPv4 and IPv6 tunnel on the same routers would also be OK.
     Svr A                ( )                Svr B
    +----+             , `,( .)              +----+
    |    |   +----+   ( .( ...)    +----+   |    |
    |    |---| R1 |---`    .....)---| R2 |---|    |
    |    |   +----+    ( ......)    +----+   |    |
    +----+                                   +----+
10.0.23.1/24          IPv6 only          10.0.42.1/24
                        network

Same/similar question but the case is instead of Site to Site VPN, it would be using the Cisco VPN Client. The host on the left side is connected to an IPv6-only network. They need to communicate with IPv4 devices across the Internet (behind a Cisco ASA).
Is this possible?
Cisco VPN Client         ( )                Cisco ASA    +----+             , `,( .)              +----+    |    |   +----+   ( .( ...)    +----+   |    |    |    |---| R1 |---`    .....)---| R2 |---|    |----IPv4 network    |    |   +----+    ( ......)    +----+   |    |    +----+                                   +----+IPv6-only HOST        IPv6 Network         has IPv6 Interface on public side
alexander.koeppe wrote:hi,I wonder if there is one use case one can think of that is not possible with Cisco IOS:Establish a IPsec tunnel over an IPv6 network tranporting both IPv4 and Ipv6 traffic. Even IPsec tunnel over an IPv6 network transporting IPv4 only does not work.I tried several things in my lab but couldn't get it running.I tried to search the net for my use case but I only find the other way round.Question: is it possible to achieve connectivity of the following IPv4 addresses over an IIPsec tunnel over Ipv6 network?Ultimately, the same tunnel should be capable transporting both. A dedicated Tunnel for IPv4 and IPv6 tunnel on the same routers would also be OK.                           ,_     Svr A                ( )                Svr B     +----+             , `,( .)              +----+    |    |   +----+   ( .( ...)    +----+   |    |     |    |---| R1 |---`    .....)---| R2 |---|    |     |    |   +----+    ( ......)    +----+   |    |     +----+                                   +----+ 10.0.23.1/24          IPv6 only          10.0.42.1/24                        network

IPv4 LAN over IPv6 WAN

With IPv6 I am most concerned today with receiving an IPv6 address from my ISP for my Spoke networks. I don't have plans to convert my Spoke LANs or Internal application servers to IPV6 anytime soon. Reviewing all the books and technical documentation out there, I don't see discussion about how to get my IPv4 traffic tunneled through the Internet via an IPv6 carrier, a 4to6 tunnel. Currently I'm running DMVPN which appears to support IPv6 tunnels, Native and 6to4. Can anyone provide direction or expertise on how to get IPv4 traffic between Enterprise locations with ISPs move to IPv6 addressing?
Thanks..

Ryan,
If this is a question of connecting LAN in different branches.
The decently scalable option is GRE (with DMVPN being the neatest).
On top ASA supports IPv4 in IPv6 IPsec (to other ASAs at this point).
You might have a bit more challanges if you want to provide access to non-intrernal resources, Internet, partner sites without IPv4 on WANs.
M.

Problem about the jmf when working over IPV6

I write a program about monitoring a RTP stream ,get the feedbacks about the stream by receving the RTCP reports and analysize the paramaters .Now the throny issues encountered is the code working perfect over the IPV4 network .but there are many exceptions when working over IPV6 the exceptions is as follows:
Exception in thread "RTCP Reporter" java.lang.NullPointerException
at com.sun.media.rtp.RTCPTransmitter.makereports(RTCPTransmitter.java:200)
at com.sun.media.rtp.RTCPTransmitter.report(RTCPTransmitter.java:106)
at com.sun.media.rtp.RTCPReporter.run(RTCPReporter.java:193)
at java.lang.Thread.run(Thread.java:619)
the session can be set up and can receive the stream .so I think it is ok of setting up the session with the IPV6 multicast address.strangely , the same particate in the session sends more than one feedbacks with different SSRC which is ought to be single.I cannot figure out.
I wonder whether there is any special setting when JMF working on the IPV6 network.I did not find materials about the JMF working on IPV6 network in Microsoft xp pc.
can any guys give me any tips?
Edited by: judyw115 on Sep 4, 2010 6:08 AM

judyw115 wrote:
Is there anyone giving me any advices?You realize this is a free forum and not paid tech support, right?
Drop the attitude and learn to be patient.

JDBC connection over IPv6

Hi
I have an MS SQL Server 2005 Database Server and a Client computer on two different subnets.
There is also a DNS Server, which contains both an IPv4 (A) and IPv6 (AAAA) DNS record for the Database Server.
I've disabled IPv4 routing between the two subnets so that the Database Server is only accessible by IPv6 from the Client computer.
I am then unable to connect to the Database Server from the Client using JDBC.
I have tried increasing the loginTimeout in the JDBC connection string, but this doesn't appear to make any difference.
I get a java.net.ConnectException in about 20 seconds.
If I remove the IPv4 (A) record of the Database Server from the DNS Server, the JDBC connection then succeeds.
Does JDBC iterate over all the possible addresses of the Database Server?
Is the loginTimeout the correct parameter to try to increase, to allow it to iterate over the possible addresses?
There is a similar problem with MS SQL Client - see http://msdn.microsoft.com/en-us/library/ms378428(SQL.90).aspx
But increasing the connection timeout allows a successful connection.
Thanks
Alain

jschell wrote:
ahkal01 wrote:
Alain: A machine may have multiple IPv6 addresses, as well as an IPv4 address.
You may not be able to get to the machine via all the addresses, depending on the network route.
If a driver gives up on the first DNS lookup (which probably will be the IPv4 address), it'll never try the IPv6 addresses. However that is NOT what you are testing.
As described in your first post there is a route. Routing works if the final location is found. After that a refused connection is a refused connection.
Alain: In my test, IPv4 routing is disabled between the two subnets. So there is no IPv4 routing between the two machines, only IPv6.
>
But even so, to me it is still two different IP addresses. Just as if you try to create your own replication by having two database servers on different IPv4 addresses. If the client is supposed to be using one address then the DNS should be set up that way.
Or use the address. Because the point is not the IP address, the point is the DNS look up.
Alain: With IPv6, it is common for computers to be assigned more than one address for routing under different hierarchies.
If you're saying that the DNS lookup should be set up to return only one IP address to client computers trying to connect to the DB Server, DNS will need to be set up differently depending on where the client computer is.
>
Again looking at it from the point of someone developing a driver the only option I would allow is that one might be able to specify a configuration value that says to try a IPv6 address first. That would be in the driver, not JDBC. So you can look to your driver for that.
There is a similar problem with MS SQL Client - see http://msdn.microsoft.com/en-us/library/ms378428(SQL.90).aspx
But increasing the connection timeout allows a successful connection.
I do not see anywhere in that link that it claims that the setup you are using would work Alain: apologies. It was the wrong url link.
I meant, http://blogs.msdn.com/sql_protocols/archive/2005/10/12/480192.aspx.The scenario there is SQL Server is configured to listen only on IPv6 addresses and disable all IPv4 addresses so that only IPv6 connection can be accepted. The workaround is to specify the IPv6 address of the target machine explicitly to force SNI to use IPv6 connection directly or to use longer timeout value. I don't see that in that blog.
It says that if you have addresses that some different behavior might result. It specifically refers to using an IPv4 address (not DNS) and failing on that and then attempting to use a IPv6 address (again not a DNS) and even in that case it might fail.
Alain: The blog is talking about a hostname resolving into multiple addresses. I quote from the blog, with bold for emphasis,
"In most cases, the connection string does not need to be modified if the <servername> is specified using server hostname or FQDN (Full Qualified Domain Name). If the server machine has dual-stack, *its hostname or FQDN will be resolved into multiple IP addresses*, including at lease one IPv4 address and multiple IPv6 addresses. *And SNI will attempt to establish connections using these IP addresses in order and use the first connection that succeeds*. IPv4 addresses are attempted first if both IPv4 and IPv6 addresses are present. This logic is transparent to the users of ODBC, OLEDB or ADO.NET.
And it doesn't say anything about that some clients already do this but merely that they can.
Alain: SNI does, from the quote above. A test also shows that it does try all the addresses that DNS returns, with the caveat that the connection timeout has to be increased.
Unfortunately it looks like the MS JDBC driver doesn't do likewise.
Myself I don't really consider that a valid option for most use cases for drivers. If I have a data center then I am not normally going to be using both types of addresses. And if I am both will work. And if there are variation in subnets then I would expect that if DNS is in use then it would be set up to correctly represent that.Thanks for your input on this thread. Much appreciated.

IPv4 to IPv6 RDP Access

Hi;
In our ınfrastructure we use dual-stack. We configured our cluster firewall and router (BGPv6).
Now we have an application server whichs 's run only over IPv6 address. We want to connect this server over RDP service from our edge sites which's run on IPv4 public address. Is it possible ? If possible what we're supposed to do ?
Best regards
Umut

If your firewall has NAT46 capability it is possible, but of all the possible NAT things you can try, that direction is the ugliest. The "right" answer is to dual-stack the edge networks, but that is presumably a long-run solution for you, not a short run one. I don't think RDP embeds IPv4 addresses in the content, so it can probably work. In general, doing protocol translation between IPv4 and IPv6 in either direction on things that aren't simple 1:1 TCP connections is a bad idea.
-- Jim Leinweber, WI State Lab of Hygiene

Uprading deployed Cluster from Ipv4 to Ipv6

Hi Friends,
i have already running and deployed a windows cluster for my SQL 2008 and Exchange 2010 Dag in different servers with ipv4 however the company management decided that we have to upgrade all servers connection from ipv4 to ipv6.
as you know that when we create a cluster it also create a virtual connection for connecting users in my case its created with ipv4.
now how am i suppose to change that virtual connection from ipv4 to ipv6 in windows 2008 R2 clustering i mean overall how to achieve my target without destroying anything.
please advise.
thanks greenman

Hi GreeMann,
Start with Windows Server 2008 IPv6 using in the Cluster service will support this functionality as well. This includes being able to support IPv6 IP address resources
and IPv4 IP address resources either alone or in combination in a failover cluster.
Failover clustering also supports 6-4 and Intra-site Automatic Tunneling Addressing Protocol (ISATAP). Additionally, failover clustering supports only IPv6 addresses that
allow for dynamic registration in Domain Name System (DNS) (AAAA host records and the IP6.ARPA reverse look-up zone). Currently, there are three types of IPv6 address types: global, site local, and link local. Dynamic DNS registrations will not occur for link
local addresses and therefore cannot be used in a failover cluster.
But there have some
application has the limited IPv6 support or full IPv6 support, the Exchange Server 2010 has the limited IPv6 support and general speaking, IPV6 is supported for SQL server 2005,2008,2008r2 and SQL 2012, the detail supported
service you can refer the following KB:
IPv6 Support in Microsoft Products and Services
http://technet.microsoft.com/en-us/network/hh994905.aspx
More information:
IPv6 Security Considerations and Recommendations
http://technet.microsoft.com/en-us/library/bb726956.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Getaddrinfo function returns IPv4-mapped IPv6 addresses in canonical name

When I use the getaddrinfo function with flag AI_CANONNAME, then in ai_canonname IPv4-mapped IPv6 addresses is returned even for IPV6 disabled machine.
So my question is that from where this canonical name is returned, I didn't found in /etc/nodename /etc/hosts or in /etc/inet/hosts or in /etc/interfacefile files.

It's only showing "unknown" for the IPv6 address.
Go into your IPv6 properties, and set the IP and DNS address settings to be obtained automatically.
Then in Manage network adapters windows, change the view options to show Menu, then click on Advanced, Advanced, and make sure IPv4 is on top instead of IPv6.
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights.

IPv4 to IPv6 transition thesis

             Hi,
I'm doing Bachelor thesis, the subject is :"IPv4 to IPv6 Transition". I hope you give me titles of books you recommend.
Also,I'd be happy if you give me a few tips.
right now,i need a topology for each transition mechansim with the configuration commands .
and how to configure an IPv4/IPv6 host?
i've already finished CCNA exploration 1 and 2,and now i'm enrolled in a CCNA exploration 3 class.my instructor has not been trained yet on using IPv6 . so,the whole subject is new for me
i'm sorry if this message was badly written , because i'm not that good in english.
yours faithfully,

You might consider the RFC series.
We have been thinking about what we originally called "IP Next Generation" and then called "IPv6" and the requirements for a transition for about 20 years. When we started, we thought about requirements, and over time we have described methodologies and experience with those methodologies. There is ongoing work, primarily in the IETF's IPv6 Operations Working Group (). The current "received wisdom" is probably summarized in RFCs 4213 (
http://www.ietf.org/rfc/rfc4213.txt) and 6180 (http://www.ietf.org/rfc/rfc6180.txt).
Walking through that history means walking through the following. Note that many of these are pretty old, and have been replaced or updated by other documents.
http://www.ietf.org/rfc/rfc1671.txt
1671 IPng White Paper on Transition and Other Considerations. B.
     Carpenter. August 1994. (Format: TXT=17631 bytes) (Status:
     INFORMATIONAL)
http://www.ietf.org/rfc/rfc1933.txt
1933 Transition Mechanisms for IPv6 Hosts and Routers. R. Gilligan, E.
     Nordmark. April 1996. (Format: TXT=47005 bytes) (Obsoleted by
     RFC2893) (Status: PROPOSED STANDARD)
http://www.ietf.org/rfc/rfc2185.txt
2185 Routing Aspects of IPv6 Transition. R. Callon, D. Haskin.
     September 1997. (Format: TXT=31281 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc2893.txt
2893 Transition Mechanisms for IPv6 Hosts and Routers. R. Gilligan, E.
     Nordmark. August 2000. (Format: TXT=62731 bytes) (Obsoletes RFC1933)
     (Obsoleted by RFC4213) (Status: PROPOSED STANDARD)
http://www.ietf.org/rfc/rfc3574.txt
3574 Transition Scenarios for 3GPP Networks. J. Soininen, Ed.. August
     2003. (Format: TXT=23359 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc3750.txt
3750 Unmanaged Networks IPv6 Transition Scenarios. C. Huitema, R.
     Austein, S. Satapati, R. van der Pol. April 2004. (Format: TXT=48153
     bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc3904.txt
3904 Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks.
     C. Huitema, R. Austein, S. Satapati, R. van der Pol. September 2004.
     (Format: TXT=46844 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc4038.txt
4038 Application Aspects of IPv6 Transition. M-K. Shin, Ed., Y-G.
     Hong, J. Hagino, P. Savola, E. M. Castro. March 2005. (Format:
     TXT=69727 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc4213.txt
4213 Basic Transition Mechanisms for IPv6 Hosts and Routers. E.
     Nordmark, R. Gilligan. October 2005. (Format: TXT=58575 bytes)
     (Obsoletes RFC2893) (Status: PROPOSED STANDARD)
http://www.ietf.org/rfc/rfc4215.txt
4215 Analysis on IPv6 Transition in Third Generation Partnership
     Project (3GPP) Networks. J. Wiljakka, Ed.. October 2005. (Format:
     TXT=52903 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc4942.txt
4942 IPv6 Transition/Co-existence Security Considerations. E. Davies,
     S. Krishnan, P. Savola. September 2007. (Format: TXT=102878 bytes)
     (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc5211.txt
5211 An Internet Transition Plan. J. Curran. July 2008. (Format:
     TXT=17158 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc6157.txt
6157 IPv6 Transition in the Session Initiation Protocol (SIP). G.
     Camarillo, K. El Malki, V. Gurbani. April 2011. (Format: TXT=32492
     bytes) (Updates RFC3264) (Status: PROPOSED STANDARD)
http://www.ietf.org/rfc/rfc6180.txt
6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6
     Deployment. J. Arkko, F. Baker. May 2011. (Format: TXT=49679 bytes)
     (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc6219.txt
6219 The China Education and Research Network (CERNET) IVI Translation
     Design and Deployment for the IPv4/IPv6 Coexistence and Transition.
     X. Li, C. Bao, M. Chen, H. Zhang, J. Wu. May 2011. (Format: TXT=44774
     bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc6264.txt
6264 An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition. S.
     Jiang, D. Guo, B. Carpenter. June 2011. (Format: TXT=31881 bytes)
     (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc6586.txt
6586 Experiences from an IPv6-Only Network. J. Arkko, A. Keranen.
     April 2012. (Format: TXT=52062 bytes) (Status: INFORMATIONAL)
http://www.ietf.org/rfc/rfc6589.txt
6589 Considerations for Transitioning Content to IPv6. J. Livingood.
     April 2012. (Format: TXT=68822 bytes) (Status: INFORMATIONAL)

How to make bonjour working on windows 7 to discover devices with ipv6 only?

I am working on a project with Windows 7 which discovers some devices with both ipv4 and ipv6. I have tried bonjour sdk which is very convenient, however I don't know if that support ipv6 as I see nothing ipv6 mdns request from wireshark. Does anyone know how to configure it to let it work?

>   * explorer.exe is blocked already, but users are able to enter the
>    Windows Explorer by clicking on the name which is visible on the
>    Start Menu.
You cannot block explorer.exe when you do not replace the shell - the
desktop you see effectively IS explorer.exe...
Your requirement sounds like you need a custom shell:
http://gpsearch.azurewebsites.net/#2812
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Cannot export nfs-share over ipv6 in OS X 10.8

I've successfully exported my nfs share over ipv4 and can access this with a nfs-client from a linux machine. However, I'm not able to export the same share over ipv6.
In my /etc/exports I have:
/Volumes/Harddisk
-network 10.0.0.0
-mask 255.255.255.0
/Volumes/Harddisk
-network fd60:760d:98ec:8588::/64
However, from the linux client I can only mount the ipv4 share, but not the ipv6 share.
Is it possible to export nfs-shares over ipv6 in OS X 10.8?

I would suggest testing a connection from a second Mac also running 10.8 via IPv6. At least then you know both will be using compatible versions. If that does not work then it would seem to be an IPv6 issue on the Mac server.

Do we support RADIUS over IPv6 in ACS 5.5?

Hi,
Could you please let me know if we support RADIUS over IPv6?

It is hard to see the information in your screen shot but ACS 5.4 and later support IPv6 for network devices:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/cisco_secure_access_control_system/5-4/user/guide/acsuserguide/net_resources.html
Also, if you type an invalid IP address in ACS you would get the following error:
A valid IPv4 address consists of four numbers (0-255) separated by periods, e.g. 123.0.255.3
A valid IPv6 address is n:n:n:n:n:n:n:n where the 'n's are either digits (0-9) or letters (A-F)
I hope this is what you were looking for!
Thank you for rating helpful posts!

ISCSI over IPv6

Can Cisco's iSCSI hardware be deployed on a Windows Server 2008 IPv6 network that uses InfiniBand as the underlying I/O fabric?
Thanks.

G'day,
Of course it can run over IPv6 - so long as your IB/Ethernet bridge is not going to do anything whacky you should be fine.
For more info:
http://www.cisco.com/en/US/products/ps5989/products_configuration_guide_chapter09186a0080664d94.html
and
http://www.cisco.com/en/US/technologies/tk648/tk872/tk373/technologies_white_paper09186a00802219bc.html
I would say however, depending on the size of your datacentre you might want to look at the nexus switches vs infiniband. I know the inifiband is very well priced a the moment but dual 10gbE cards these days are only ~1200(AUD)...

Windows 8.1 prefers IPv4 over IPv6

Similar Messages

Maybe you are looking for