[opensuse] slightly OT - do Androids support ipv6 ?
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address. -- Per Jessen, Zürich (1.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30/01/15 08:46, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
A quick google suggests support is incomplete and requires as app to make it function (and possibly a rooted device...) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dylan wrote:
On 30/01/15 08:46, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
A quick google suggests support is incomplete and requires as app to make it function (and possibly a rooted device...)
Wow. I had also googled some, but most answers seemed to be 1-2 years old so I figured a brand new Samsung would surely have advanced to a stage with working IPv6. -- Per Jessen, Zürich (2.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 05:52 AM, Dylan wrote:
On 30/01/15 08:46, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
A quick google suggests support is incomplete and requires as app to make it function (and possibly a rooted device...)
I guess someone forgot to tell all the various Android devices (5 at last count) that I've had that all got IPv6 addresses when on my network. Android has supported IPv6 for years. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 09:46 AM, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
Sure, Android has IPv6 support, but most telcos wont give you a IPv6 address. And i think Android does not support DHCPv6, but router advertisements. So try to connect your device to a wlan and if your router is linux based, check if it runs radvd.
Florian Gleixner wrote:
On 01/30/2015 09:46 AM, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
Sure, Android has IPv6 support, but most telcos wont give you a IPv6 address. And i think Android does not support DHCPv6, but router advertisements. So try to connect your device to a wlan and if your router is linux based, check if it runs radvd.
Ah, that is _good_ news. My telco (i.e. ISP) is up-to-date, I've had a /64 range since 2009. Yes I have radvd running on my openSUSE-based router. Still, my Samsung Galaxy with Android 4.4.2 doesn't seem to want to know. I've added it's link-local address to clients {} in radvd.conf, and I see the neighbor solicitations go out, but it's not responding. -- Per Jessen, Zürich (3.8°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
Per Jessen wrote:
Florian Gleixner wrote:
On 01/30/2015 09:46 AM, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
Sure, Android has IPv6 support, but most telcos wont give you a IPv6 address. And i think Android does not support DHCPv6, but router advertisements. So try to connect your device to a wlan and if your router is linux based, check if it runs radvd.
Ah, that is _good_ news.
My telco (i.e. ISP) is up-to-date, I've had a /64 range since 2009. Yes I have radvd running on my openSUSE-based router. Still, my Samsung Galaxy with Android 4.4.2 doesn't seem to want to know. I've added it's link-local address to clients {} in radvd.conf, and I see the neighbor solicitations go out, but it's not responding.
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. -- Per Jessen, Zürich (3.4°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
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird.
That's not good. IPv6 should not be dependent on IPv4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4.
I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon. I just checked with my notebook computer, running openSUSE 13.1. It gets just an IPv6 address when the IPv4 dhcp server is stopped. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 08:19 AM, James Knott wrote:
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4. I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon.
I just checked with my notebook computer, running openSUSE 13.1. It gets just an IPv6 address when the IPv4 dhcp server is stopped.
One thing though, while it connects with IPv6 only, the icon on the Network Manager keeps spinning, while it looks for an IPv4 address. The developers should get with what will be the future of IPv6 only. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/30/2015 08:19 AM, James Knott wrote:
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4. I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon.
I just checked with my notebook computer, running openSUSE 13.1. It gets just an IPv6 address when the IPv4 dhcp server is stopped.
One thing though, while it connects with IPv6 only, the icon on the Network Manager keeps spinning, while it looks for an IPv4 address. The developers should get with what will be the future of IPv6 only.
Just change the interface to ipv6-only? That's what I did. (with Yast, not Network Manager). -- Per Jessen, Zürich (3.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 09:03 AM, Per Jessen wrote:
One thing though, while it connects with IPv6 only, the icon on the
Network Manager keeps spinning, while it looks for an IPv4 address. The developers should get with what will be the future of IPv6 only. Just change the interface to ipv6-only? That's what I did. (with Yast, not Network Manager).
There's a setting for requiring IPv4 or not. It doesn't appear to make any difference. With is selected or not, I still get an IPv6 address, but also the error on the icon. So, it appears the KDE developers still have some work to do. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4.
I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon.
I guess there's an Android bug-tracking system somewhere? I really just wanted to test some NAT64 stuff I've been setting up, but as that is just as easily tested with a laptop, the Android situation, although serious, is not so important to me.
I just checked with my notebook computer, running openSUSE 13.1. It gets just an IPv6 address when the IPv4 dhcp server is stopped.
Yup, I have no problems with that either. -- Per Jessen, Zürich (3.9°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
On 01/30/2015 08:28 AM, Per Jessen wrote:
I really just wanted to test some NAT64 stuff
Why even bother? It doesn't get you much with IPv6. Or have you already used up all the addresses in your /64 subnet? ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/30/2015 08:28 AM, Per Jessen wrote:
I really just wanted to test some NAT64 stuff
Why even bother? It doesn't get you much with IPv6. Or have you already used up all the addresses in your /64 subnet? ;-)
Hehe, not quite. Have to be careful not to squander them left, right and center :-) However - what do you do with e.g. a smartphone that has only IPv6 ? How does it get access to IPv4 only websites, for instance? NAT64 seems to be an answer, but I guess it's not the only one. This morning I set up NAT64 with dns64 and tayga, works really well. -- Per Jessen, Zürich (2.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 12:50 PM, Per Jessen wrote:
James Knott wrote:
On 01/30/2015 08:28 AM, Per Jessen wrote:
I really just wanted to test some NAT64 stuff Why even bother? It doesn't get you much with IPv6. Or have you already used up all the addresses in your /64 subnet? ;-) Hehe, not quite. Have to be careful not to squander them left, right and center :-)
However - what do you do with e.g. a smartphone that has only IPv6 ? How does it get access to IPv4 only websites, for instance? NAT64 seems to be an answer, but I guess it's not the only one. This morning I set up NAT64 with dns64 and tayga, works really well.
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. I don't know if you have it, but there's an excellent IPv6 book, from O'Reilly called IPv6 Essentials that has a lot of useful info, including some discussion about converting between IPv4 and IPv6. http://shop.oreilly.com/product/0636920023432.do -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/30/2015 12:50 PM, Per Jessen wrote:
James Knott wrote:
On 01/30/2015 08:28 AM, Per Jessen wrote:
I really just wanted to test some NAT64 stuff Why even bother? It doesn't get you much with IPv6. Or have you already used up all the addresses in your /64 subnet? ;-) Hehe, not quite. Have to be careful not to squander them left, right and center :-)
However - what do you do with e.g. a smartphone that has only IPv6 ? How does it get access to IPv4 only websites, for instance? NAT64 seems to be an answer, but I guess it's not the only one. This morning I set up NAT64 with dns64 and tayga, works really well.
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. -- Per Jessen, Zürich (1.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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.
No, I really haven't looked at that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 04:23 PM, 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.
It's not quite that simple. While TCP generally works fine, there are some issues with UDP. One is a checksum is optional with IPv4 UDP, but mandatory with IPv6. There are also some ICMP kinks that have to be handled. There is also the issue of variable length IP headers on IPv4 vs extension headers on IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 01/31/2015 05:46 AM, Per Jessen wrote:
However, iTunes claims there is no internet connection as does "software update" and the App Store ...
Do those work over IPv6? Or are the apps just checking the IPv4 status? There are a lot of people who have to get up to speed on IPv6 because it's coming. In some parts of the world, IPv4 addresses are no longer avaiable. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/31/2015 05:46 AM, Per Jessen wrote:
However, iTunes claims there is no internet connection as does "software update" and the App Store ...
Do those work over IPv6? Or are the apps just checking the IPv4 status?
I don't know if they work over IPv6, but given that they're just applications, why should they care? It looks to me as if they're doing some sort of network check which only cares about ipv4 ... it's mindboggling.
There are a lot of people who have to get up to speed on IPv6 because it's coming. In some parts of the world, IPv4 addresses are no longer avaiable.
I'm quite surprised that Android and iPhone both have issues with IPv6. It just seems so unlikely. -- Per Jessen, Zürich (1.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/01/2015 03:09 AM, Per Jessen wrote:
I'm quite surprised that Android and iPhone both have issues with IPv6. It just seems so unlikely.
As I mentioned, even the KDE network manager isn't quite there yet. The developers have to think of IPv6 as the independent stand alone protocol that it is and not just an adjunct to IPv4. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
James Knott wrote:
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4.
I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon.
I guess there's an Android bug-tracking system somewhere?
https://code.google.com/p/android/issues/detail?id=123766 I guess we get to see if Google's developers are any faster than ours :-) -- Per Jessen, Zürich (2.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
James Knott wrote:
On 01/30/2015 08:03 AM, James Knott wrote:
On 01/30/2015 07:17 AM, Per Jessen wrote:
Ah, interesting - it seems that Android insists on acquiring an IPv4 address, only then will it also do IPv6. I had adjusted our DHCP server to deny IPv4 to this device; when I reverted to the previous config, the device got both addresses. Weird. That's not good. IPv6 should not be dependent on IPv4.
I just verified that. I turned off my IPv4 DHCP server and my tablet would not connect. As soon as I started dhcp again, my tablet connected with both IPv4 & IPv6 addresses. This is a serious flaw. I hope Google fixes it soon.
I guess there's an Android bug-tracking system somewhere?
https://code.google.com/p/android/issues/detail?id=123766
I guess we get to see if Google's developers are any faster than ours :-)
"Fixed in Android 5.0". Chances of that ever ending up on my brandnew Samsung are of course (approximately) nil. -- Per Jessen, Zürich (2.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/31/2015 05:49 AM, Per Jessen wrote:
I guess we get to see if Google's developers are any faster than
ours :-) "Fixed in Android 5.0". Chances of that ever ending up on my brandnew Samsung are of course (approximately) nil.
Ummm... The tablet I used to check this with yesterday is running Lollipop 5.0.2, so it appears it hasn't been fixed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/31/2015 05:49 AM, Per Jessen wrote:
I guess we get to see if Google's developers are any faster than
ours :-) "Fixed in Android 5.0". Chances of that ever ending up on my brandnew Samsung are of course (approximately) nil.
Ummm... The tablet I used to check this with yesterday is running Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that. https://code.google.com/p/android/issues/detail?id=123766 -- Per Jessen, Zürich (1.1°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
On 02/01/2015 03:11 AM, Per Jessen wrote:
You might want to update the bugreport with that.
Done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/01/2015 03:11 AM, Per Jessen wrote:
Ummm... The tablet I used to check this with yesterday is running
Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that.
If you've been following my comments and the responses, you'll see that the guy working on this is a bit "thick". He can't seem to tell the difference between IPv6 working and not getting a WiFi connection when IPv4 is not available. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/01/2015 03:11 AM, Per Jessen wrote:
Ummm... The tablet I used to check this with yesterday is running
Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that.
If you've been following my comments and the responses, you'll see that the guy working on this is a bit "thick". He can't seem to tell the difference between IPv6 working and not getting a WiFi connection when IPv4 is not available.
Oh dear. I've only just read it, he does seem to quite get the idea. Reproducing it couldn't be any easier. -- Per Jessen, Zürich (1.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
James Knott wrote:
On 02/01/2015 03:11 AM, Per Jessen wrote:
Ummm... The tablet I used to check this with yesterday is running
Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that.
If you've been following my comments and the responses, you'll see that the guy working on this is a bit "thick". He can't seem to tell the difference between IPv6 working and not getting a WiFi connection when IPv4 is not available.
Oh dear. I've only just read it, he does seem to quite get the idea.
the 'not' didn't make it through the email fliter. -- Per Jessen, Zürich (1.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/01/2015 02:03 PM, Per Jessen wrote:
James Knott wrote:
On 02/01/2015 03:11 AM, Per Jessen wrote:
Ummm... The tablet I used to check this with yesterday is running
Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that.
If you've been following my comments and the responses, you'll see that the guy working on this is a bit "thick". He can't seem to tell the difference between IPv6 working and not getting a WiFi connection when IPv4 is not available. Oh dear. I've only just read it, he does seem to quite get the idea. Reproducing it couldn't be any easier.
Do you use RDNSS to provide the DNS server address? This guy seems to think it's necessary. I use DHCPv4 to provide the DNS server address on my network. I haven't enabled DHCPv6 on my network. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/01/2015 02:03 PM, Per Jessen wrote:
James Knott wrote:
On 02/01/2015 03:11 AM, Per Jessen wrote:
Ummm... The tablet I used to check this with yesterday is running
Lollipop 5.0.2, so it appears it hasn't been fixed.
You might want to update the bugreport with that.
If you've been following my comments and the responses, you'll see that the guy working on this is a bit "thick". He can't seem to tell the difference between IPv6 working and not getting a WiFi connection when IPv4 is not available. Oh dear. I've only just read it, he does seem to quite get the idea. Reproducing it couldn't be any easier.
Do you use RDNSS to provide the DNS server address? This guy seems to think it's necessary. I use DHCPv4 to provide the DNS server address on my network. I haven't enabled DHCPv6 on my network.
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause. I don't use dhcpv6, this is my radvd.conf: interface eth0 { AdvSendAdvert on; prefix 2001:DB8:2010:1ff::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; clients { fe80::66b8:53ff:fe6c:865f; # samsung galaxy fe80::fad0:bdff:fe70:b500; # samsung galaxy S }; #RDNSS 2001:DB8:2010:1ff::f:1 { }; RDNSS 2001:DB8:2010:1ff::f:2 { }; }; -- Per Jessen, Zürich (1.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/02/2015 02:39 AM, Per Jessen wrote:
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause.
Perhaps you can provide the tcp dump info that support guy is looking for. BTW, what's the purpose of that clients section? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/02/2015 02:39 AM, Per Jessen wrote:
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause.
Perhaps you can provide the tcp dump info that support guy is looking for.
I would, except I don't have an Android 5.0 device.
BTW, what's the purpose of that clients section?
I'm just limiting the IPv6 access to a select group of clients. Just a testing precaution. -- Per Jessen, Zürich (-4.4°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
On 02/03/2015 02:39 AM, Per Jessen wrote:
James Knott wrote:
On 02/02/2015 02:39 AM, Per Jessen wrote:
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause.
Perhaps you can provide the tcp dump info that support guy is looking for. I would, except I don't have an Android 5.0 device.
BTW, what's the purpose of that clients section?
I'm just limiting the IPv6 access to a select group of clients. Just a testing precaution.
Are you running RDNSS on an older version of openSUSE? I can't seem to get it going on 13.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/03/2015 02:39 AM, Per Jessen wrote:
James Knott wrote:
On 02/02/2015 02:39 AM, Per Jessen wrote:
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause.
Perhaps you can provide the tcp dump info that support guy is looking for. I would, except I don't have an Android 5.0 device.
BTW, what's the purpose of that clients section?
I'm just limiting the IPv6 access to a select group of clients. Just a testing precaution.
Are you running RDNSS on an older version of openSUSE? I can't seem to get it going on 13.1.
The router with radvd is running 13.1, but it's not current with updates. -- Per Jessen, Zürich (1.4°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
On 02/03/2015 08:59 AM, Per Jessen wrote:
Are you running RDNSS on an older version of openSUSE? I can't seem
to get it going on 13.1. The router with radvd is running 13.1, but it's not current with updates.
Do you have ndisc6 installed? Does the command rdisc6 -1 work for you? I don't have it on my system and can't seem to find it for 13.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/03/2015 08:59 AM, Per Jessen wrote:
Are you running RDNSS on an older version of openSUSE? I can't seem
to get it going on 13.1. The router with radvd is running 13.1, but it's not current with updates.
Do you have ndisc6 installed? Does the command rdisc6 -1 work for you? I don't have it on my system and can't seem to find it for 13.1
Nope, I've got nothing like that installed. I see the tarball here though: http://www.remlab.net/ndisc6/ -- Per Jessen, Zürich (-2.2°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
Per Jessen wrote:
James Knott wrote:
On 02/03/2015 08:59 AM, Per Jessen wrote:
Are you running RDNSS on an older version of openSUSE? I can't seem
to get it going on 13.1. The router with radvd is running 13.1, but it's not current with updates.
Do you have ndisc6 installed? Does the command rdisc6 -1 work for you? I don't have it on my system and can't seem to find it for 13.1
Nope, I've got nothing like that installed. I see the tarball here though:
James, any chance you can build this and provide the google guys with the rdisc output? I've just built it: ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # rdisc6 -1 enp0s25 Soliciting ff02::2 (ff02::2) on enp0s25... Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:8e0:2010:1ff::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds Recursive DNS server : 2001:8e0:2010:1ff::f:1 DNS server lifetime : 600 (0x00000258) seconds Source link-layer address: 00:30:48:90:7F:C2 from fe80::230:48ff:fe90:7fc2 -- Per Jessen, Zürich (-1.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/05/2015 10:29 AM, Per Jessen wrote:
James, any chance you can build this and provide the google guys with the rdisc output? I've just built it:
Soliciting ff02::2 (ff02::2) on eth0... Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:5c0:1100:1000::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds MTU : 1280 bytes (valid) Source link-layer address: 00:16:17:A7:F2:D3 from fe80::216:17ff:fea7:f2d3 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/05/2015 10:29 AM, Per Jessen wrote:
James, any chance you can build this and provide the google guys with the rdisc output? I've just built it:
Soliciting ff02::2 (ff02::2) on eth0...
Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:5c0:1100:1000::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds MTU : 1280 bytes (valid) Source link-layer address: 00:16:17:A7:F2:D3 from fe80::216:17ff:fea7:f2d3
Ah, there's no DNS ? -- Per Jessen, Zürich (-1.1°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
On 02/06/2015 02:08 AM, Per Jessen wrote:
James Knott wrote:
On 02/05/2015 10:29 AM, Per Jessen wrote:
James, any chance you can build this and provide the google guys with the rdisc output? I've just built it: Soliciting ff02::2 (ff02::2) on eth0...
Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:5c0:1100:1000::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds MTU : 1280 bytes (valid) Source link-layer address: 00:16:17:A7:F2:D3 from fe80::216:17ff:fea7:f2d3
Ah, there's no DNS ?
That's what I mentioned earlier. I can't seem to get RDNSS working. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 02/06/2015 02:08 AM, Per Jessen wrote:
James Knott wrote:
On 02/05/2015 10:29 AM, Per Jessen wrote:
James, any chance you can build this and provide the google guys with the rdisc output? I've just built it: Soliciting ff02::2 (ff02::2) on eth0...
Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:5c0:1100:1000::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds MTU : 1280 bytes (valid) Source link-layer address: 00:16:17:A7:F2:D3 from fe80::216:17ff:fea7:f2d3
Ah, there's no DNS ?
That's what I mentioned earlier. I can't seem to get RDNSS working.
I don't remember doing anything special - I added the RDNSS statement in radvd.conf, that's all. -- Per Jessen, Zürich (-1.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 08:51 AM, Per Jessen wrote:
That's what I mentioned earlier. I can't seem to get RDNSS working.
I don't remember doing anything special - I added the RDNSS statement in radvd.conf, that's all.
I found an error in radvd.conf and now: rdisc6 -1 eth0 Soliciting ff02::2 (ff02::2) on eth0... Hop limit : 64 ( 0x40) Stateful address conf. : No Stateful other conf. : No Mobile home agent : No Router preference : medium Neighbor discovery proxy : No Router lifetime : 1800 (0x00000708) seconds Reachable time : unspecified (0x00000000) Retransmit time : unspecified (0x00000000) Prefix : 2001:5c0:1100:1000::/64 On-link : Yes Autonomous address conf.: Yes Valid time : 86400 (0x00015180) seconds Pref. time : 14400 (0x00003840) seconds Recursive DNS server : 2001:5c0:1100:1000::1 DNS server lifetime : 600 (0x00000258) seconds MTU : 1280 bytes (valid) Source link-layer address: 00:16:17:A7:F2:D3 from fe80::216:17ff:fea7:f2d3 I'll have to try shutting down my dhcp server to try with my tablet again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 09:58 AM, James Knott wrote:
I'll have to try shutting down my dhcp server to try with my tablet again.
I just did and now my tablet has IPv6 addresses, but no IPv4. So, it does work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 10:00 AM, James Knott wrote:
On 02/06/2015 09:58 AM, James Knott wrote:
I'll have to try shutting down my dhcp server to try with my tablet again. I just did and now my tablet has IPv6 addresses, but no IPv4. So, it does work.
I just tried an experiment with my notebook computer. When I have the dhcp server turned off, openSUSE 13.1 doesn't learn the IPv6 dns address with rdnss. On the other hand, when the dhcp server is turned off, Windows 7 uses rdnss, but prefers to use the dhcp IPv4 dns address when available. I'll have to do some more testing with openSUSE & Wireshark to verify what's happening. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/2015 10:22 AM, James Knott wrote:
On 02/06/2015 10:00 AM, James Knott wrote:
On 02/06/2015 09:58 AM, James Knott wrote:
I'll have to try shutting down my dhcp server to try with my tablet again. I just did and now my tablet has IPv6 addresses, but no IPv4. So, it does work. I just tried an experiment with my notebook computer. When I have the dhcp server turned off, openSUSE 13.1 doesn't learn the IPv6 dns address with rdnss. On the other hand, when the dhcp server is turned off, Windows 7 uses rdnss, but prefers to use the dhcp IPv4 dns address when available. I'll have to do some more testing with openSUSE & Wireshark to verify what's happening.
I have verified that 13.1 does not use RDNSS, at least when using the KDE network manager. I've filed a bug #916613. https://bugzilla.opensuse.org/show_bug.cgi?id=916613 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/02/2015 02:39 AM, Per Jessen wrote:
Yep, I use RDNSS to point all IPv6 lookups to a separate DNS that has a dns64 clause.
I don't use dhcpv6, this is my radvd.conf:
I have tried to enable it, but I don't see any DNS server info with Wireshark. Did anything else have to be installed? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/30/2015 03:46 AM, Per Jessen wrote:
see $SUBJ. I'm playing with a Samsung Galaxy and I'm trying to make it work over ipv6, but I don't seem to be getting very far. It just keeps asking for an ipv4 address.
Yes, Android devices have supported IPv6 for a few years. I've been running IPv6 on my home network for almost 5 years and all Android devices I've had, going back to a Nexus 1 smart phone get IPv6 addresses. If your computers automatically get IPv6 addresses, your Android devices should too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Dylan -
Florian Gleixner -
James Knott -
Per Jessen -
Yamaban