Yamaban wrote:
On Fri, 30 Jan 2015 22:18, James Knott wrote:
On 01/30/2015 04:14 PM, Per Jessen wrote:
There are conversion mechanisms as per RFC 6052 & 6145. Regular NAT
won't do it, as all it does is change the apparent address whether on IPv4 or IPv6. RFC6052 & RFC6145 - TL;DR most of it, but it seems to me that this is exactly what I set up this morning.
Nonetheless, do you have a better way of enabling an ipv6-only device to access ipv4 addresses? I'm learning, practical hints please.
The whole ipv4 address room is translated with a prefix into ipv6 addresses, some call this NAT46 some call that 4to6.
- Yamaban.
Isn't that called NAT64? I think that is done with this prefix: 64:ff9b::/96. The question is - does that by itself actually enable an ipv6-only device to communicate with an IPv4 site? http://de.wikipedia.org/wiki/NAT64 If we take "download.opensuse.org" = 195.135.221.134 and map it: 64:ff9b::195.135.221.134. I can't ping that, so I need a NAT64 router somewhere. That's what tayga does. It's an interesting topic - Apple's iPhone also seems to have a few issues with running ipv6-only. We have an elderly iPhone 3GS with iOS 6. With IPv6-only, the browser works fine, so it _is_ connected. However, iTunes claims there is no internet connection as does "software update" and the App Store ... the minute I let the dhcp server hand out an IPv4 address, voila! the app store springs back to life :-) An iPhone 5S with iOS7 - couldn't get it to work. It never acquires an IPv6 address via RA, only link-local. Is there a http://bugzilla.apple.com? :-) -- Per Jessen, Zürich (1.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org