Why would it not work? Any reasonable operating system that only has IPv4 connectivity will recognize that it won't be able to connect to IPv6 content and won't even try. You will only have a problem when the content is IPv6-only.
How about this: what happens when you try to visit http://ipv6.cnn.com from a IPv4-only machine? Or http://ipv6.he.net? Try it, and let me know what happens. Hint: the first one won't resolve since it's IPv6 only, the second will send you to their IPv4 address. Windows and Linux/*BSD will be fine. Macs are a whole other kettle of fish; I've seen reports that they have a whole lot of IPv6 goofiness to 'em. On 2/4/2011 12:44 PM, Ben Scott wrote: > On Fri, Feb 4, 2011 at 12:42 PM, <[email protected]> wrote: >> Should be able to NAT at the firewall so one could keep internal v4 >> addresses. At least, I hope so. > > I don't think that will work. > > 1. Browser is instructed to go www.example.com > 2. DNS returns only an IPv6 address record (AAAA) for that site > 3. Browser computer has only IPv4 connectivity > 4. Now what? > > The browser cannot plug an IPv6 address into the IPv4 stack. -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
