|WikiProject Computing / Networking|
- Quite obviously, it's an IPv6-over-IPv4 tunneling technology, but yes, it needs more elaboration on this.Jasper Deng (talk) 02:47, 26 August 2011 (UTC)
I agree, why does it exist? it connects two hosts over ipv4 networks via a tunnel, why does the tunnel exist if both hosts already have ipv4 adresses? especially when it can't do ipv4 to ipv6.. on top of that inside enterprises is breaks both QoS and WAN optimisation since there arn't any qos or wanop implementations that look inside protocol 41 — Preceding unsigned comment added by 188.8.131.52 (talk) 18:32, 22 November 2013 (UTC)
I've cleaned up in-line links to use ref tags and added references to their own reference list as well, I do not have a lot of knowledge on this particular field so if anyone could clarify the article that would be great :) Thor erik (talk|contrib) 09:17, 23 July 2010 (UTC)
It is an address appearing recurrently as an error in the Error Log in Windows 7 of a laptop connected exclusively through wi fi adapter/routers. There is no info other than general info on ISATAP. — Preceding unsigned comment added by 184.108.40.206 (talk) 02:19, 4 October 2012 (UTC)
What is it good for?
What are the scenarios for ISATAP? 2 Dual-stack hosts can communicate directly via IPv4 with each other. Or is it used on routers that connects two IPv6 networks over a IPv4 "link"? Are IPv6 packets encapsulated in IPv4? If yes: how? More questions than answers. ;-( --RokerHRO (talk) 12:45, 6 May 2013 (UTC)
Relations to W8. and W8.1
Any comments to Windows 8? Why Windows 8.1 (internal build 6.3.9600) installs both isatap and 6to4 gateway protocols? Is there a need to have both inside? Can anybody scetch the stack from W8.1 regarding the IP types? What is your opinion for the further near future of these solutions? What's going on with crucial need of IP4 DNS mechanisms?