Re: DHCPv6 client in Windows 10 broken after anniversary update
Has this been confirmed? What is next? On Fri, Oct 14, 2016 at 5:59 AM, Harald F. Karlsen wrote: > On 11.10.2016 18:37, Marcus Keane wrote: > >> We've raised it with the product group and we are investigating further. >> > Great! Also feel free to keep us updated on any findings here on the list > (especially the ship vehicle and date for the fix). > > -- > Harald >
Re: Slow WiFi with Android Marshmallow & IPv6?
s/MUST no/MUST not/g On Sun, Apr 24, 2016 at 8:49 PM, Brzozowski, John Jason wrote: > Operators MUST no advertise DNS server IPv6 addresses if they do not > work. The fix is simple. I would like to see as much happening over IPv6 > as possible, the last thing I really want to see is more happy (happier) > eye ball implementations. > > On Sun, Apr 24, 2016 at 8:35 PM, Lorenzo Colitti > wrote: > >> Android does not behave well when configured with IPv6 DNS servers that >> do not work. This is because it prefers IPv6, does not (yet) ignore >> unresponsive DNS servers, and has quite high resolver timeouts. >> >> One infamous example is a German ISP whose CPE announces an IPv6 address >> in RDNSS but never responds to queries to that address. Perhaps because no >> other operating system has a problem in this situation, the ISP has not >> fixed this, and users have been blaming Android. This is by no means the >> only case, though. Some of you know who you are :) >> >> Future Android releases will likely ignore broken DNS servers. This is >> unfortunate; we'd hoped that ISPs that provision devices with IPv6 >> connectivity would be able to ensure that the DNS servers are responsive >> and that as IPv6 matured this problem would go away. Unfortunately it has >> not. >> >> As Erik said, the way to debug this problem would be to have someone >> running 6.0.1 on voo to run "adb shell dumpsys connectivity --diag" and >> open a bug as described at >> https://source.android.com/source/report-bugs.html . >> >> On Sun, Apr 24, 2016 at 11:21 PM, Brzozowski, John Jason >> wrote: >> >>> Android is properly trying to query DNS over IPv6 unlike other >>> devices/OSes. Most other mobile platforms still prefer the querying of DNS >>> over IPv4 for A/ RR query types. >>> >>> On Sun, Apr 24, 2016 at 10:17 AM, Eric Vyncke (evyncke) < >>> evyn...@cisco.com> wrote: >>> >>>> Jeroen, Erik and John, >>>> >>>> Thanks for the hint. I will advise the ISP to investigate any DNS issue >>>> (such as not returning an error message when requesting a non-existing >>>> ) but I wonder why it is linked to that specific Android Marshmallow >>>> version. >>>> >>>> -éric >>>> >>>> From: on behalf >>>> of "Brzozowski, John Jason" >>>> Date: Sunday 24 April 2016 at 16:01 >>>> To: Erik Kline >>>> Cc: Jeroen Massar , IPv6 Ops list < >>>> ipv6-ops@lists.cluenet.de> >>>> Subject: Re: Slow WiFi with Android Marshmallow & IPv6? >>>> >>>> My customers saw this issue at one point. We had issues with DNS over >>>> IPv6. Bad DNS and/or network configurations. Once these were fixed, the >>>> problems cleared up. >>>> >>>> On Sunday, April 24, 2016, Erik Kline wrote: >>>> >>>>> On 24 April 2016 at 19:53, Jeroen Massar wrote: >>>>> > On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote: >>>>> >> One of the first Belgian ISP to deploy IPv6 (VOO) is now >>>>> recommending to >>>>> >> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their >>>>> >> residential WiFi CPE... :-( >>>>> >> >>>>> >> It appears that the issue is about IPv6 web sites/apps being really >>>>> >> slower when using IPv6. >>>>> > >>>>> > Is it a DNS issue maybe? >>>>> > >>>>> > https://www.sixxs.net/faq/dns/?faq=ipv6slowconnect >>>>> > >>>>> > As that has been the general cause of "Disable IPv6!" around the >>>>> > world for many years already. >>>>> > >>>>> > Of course, without more details, little one really can say. Bug >>>>> number >>>>> > maybe? >>>>> > >>>>> > Greets, >>>>> > Jeroen >>>>> > >>>>> >>>>> Yeah, a link to something that eventually leads to a bug report would >>>>> be good. >>>>> >>>>> Also if anybody has adb installed they can just try "adb shell dumpsys >>>>> connectivity --diag" and see what the over-simplified diagnostic >>>>> output shows. >>>>> >>>> >>> >> >
Re: Slow WiFi with Android Marshmallow & IPv6?
Operators MUST no advertise DNS server IPv6 addresses if they do not work. The fix is simple. I would like to see as much happening over IPv6 as possible, the last thing I really want to see is more happy (happier) eye ball implementations. On Sun, Apr 24, 2016 at 8:35 PM, Lorenzo Colitti wrote: > Android does not behave well when configured with IPv6 DNS servers that do > not work. This is because it prefers IPv6, does not (yet) ignore > unresponsive DNS servers, and has quite high resolver timeouts. > > One infamous example is a German ISP whose CPE announces an IPv6 address > in RDNSS but never responds to queries to that address. Perhaps because no > other operating system has a problem in this situation, the ISP has not > fixed this, and users have been blaming Android. This is by no means the > only case, though. Some of you know who you are :) > > Future Android releases will likely ignore broken DNS servers. This is > unfortunate; we'd hoped that ISPs that provision devices with IPv6 > connectivity would be able to ensure that the DNS servers are responsive > and that as IPv6 matured this problem would go away. Unfortunately it has > not. > > As Erik said, the way to debug this problem would be to have someone > running 6.0.1 on voo to run "adb shell dumpsys connectivity --diag" and > open a bug as described at > https://source.android.com/source/report-bugs.html . > > On Sun, Apr 24, 2016 at 11:21 PM, Brzozowski, John Jason > wrote: > >> Android is properly trying to query DNS over IPv6 unlike other >> devices/OSes. Most other mobile platforms still prefer the querying of DNS >> over IPv4 for A/ RR query types. >> >> On Sun, Apr 24, 2016 at 10:17 AM, Eric Vyncke (evyncke) < >> evyn...@cisco.com> wrote: >> >>> Jeroen, Erik and John, >>> >>> Thanks for the hint. I will advise the ISP to investigate any DNS issue >>> (such as not returning an error message when requesting a non-existing >>> ) but I wonder why it is linked to that specific Android Marshmallow >>> version. >>> >>> -éric >>> >>> From: on behalf >>> of "Brzozowski, John Jason" >>> Date: Sunday 24 April 2016 at 16:01 >>> To: Erik Kline >>> Cc: Jeroen Massar , IPv6 Ops list < >>> ipv6-ops@lists.cluenet.de> >>> Subject: Re: Slow WiFi with Android Marshmallow & IPv6? >>> >>> My customers saw this issue at one point. We had issues with DNS over >>> IPv6. Bad DNS and/or network configurations. Once these were fixed, the >>> problems cleared up. >>> >>> On Sunday, April 24, 2016, Erik Kline wrote: >>> >>>> On 24 April 2016 at 19:53, Jeroen Massar wrote: >>>> > On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote: >>>> >> One of the first Belgian ISP to deploy IPv6 (VOO) is now >>>> recommending to >>>> >> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their >>>> >> residential WiFi CPE... :-( >>>> >> >>>> >> It appears that the issue is about IPv6 web sites/apps being really >>>> >> slower when using IPv6. >>>> > >>>> > Is it a DNS issue maybe? >>>> > >>>> > https://www.sixxs.net/faq/dns/?faq=ipv6slowconnect >>>> > >>>> > As that has been the general cause of "Disable IPv6!" around the >>>> > world for many years already. >>>> > >>>> > Of course, without more details, little one really can say. Bug number >>>> > maybe? >>>> > >>>> > Greets, >>>> > Jeroen >>>> > >>>> >>>> Yeah, a link to something that eventually leads to a bug report would >>>> be good. >>>> >>>> Also if anybody has adb installed they can just try "adb shell dumpsys >>>> connectivity --diag" and see what the over-simplified diagnostic >>>> output shows. >>>> >>> >> >
Re: Slow WiFi with Android Marshmallow & IPv6?
As long as we have either DHCPv6 or RFC6106 we can make this work to enable IPv6 only for devices like phones, etc. Between DHCPv6 and RFC6106 we have most devices covered. A co-worker recently introduced me to the Linux package for RDNSS. On Sun, Apr 24, 2016 at 11:37 AM, Matthew Huff wrote: > Remember, Android developers refuse to implement DHCPv6 and so can only > get DNS server info from RDDNS (rfc6106). Since the number RA devices > that support RFC6106 are limited, this provides another problem set for > Android devices and IPv6 > > > > > > Matthew Huff | 1 Manhattanville Rd > > Director of Operations | Purchase, NY 10577 > > OTA Management LLC | Phone: 914-460-4039 > > aim: matthewbhuff| Fax: 914-694-5669 > > > > *From:* ipv6-ops-bounces+mhuff=ox@lists.cluenet.de [mailto: > ipv6-ops-bounces+mhuff=ox@lists.cluenet.de] *On Behalf Of *Brzozowski, > John Jason > *Sent:* Sunday, April 24, 2016 10:21 AM > *To:* Eric Vyncke (evyncke) > *Cc:* Erik Kline ; Jeroen Massar ; IPv6 > Ops list > > *Subject:* Re: Slow WiFi with Android Marshmallow & IPv6? > > > > Android is properly trying to query DNS over IPv6 unlike other > devices/OSes. Most other mobile platforms still prefer the querying of DNS > over IPv4 for A/ RR query types. > > > > On Sun, Apr 24, 2016 at 10:17 AM, Eric Vyncke (evyncke) > wrote: > > Jeroen, Erik and John, > > > > Thanks for the hint. I will advise the ISP to investigate any DNS issue > (such as not returning an error message when requesting a non-existing > AAAA) but I wonder why it is linked to that specific Android Marshmallow > version. > > > > -éric > > > > *From: * on behalf > of "Brzozowski, John Jason" > *Date: *Sunday 24 April 2016 at 16:01 > *To: *Erik Kline > *Cc: *Jeroen Massar , IPv6 Ops list < > ipv6-ops@lists.cluenet.de> > *Subject: *Re: Slow WiFi with Android Marshmallow & IPv6? > > > > My customers saw this issue at one point. We had issues with DNS over > IPv6. Bad DNS and/or network configurations. Once these were fixed, the > problems cleared up. > > On Sunday, April 24, 2016, Erik Kline wrote: > > On 24 April 2016 at 19:53, Jeroen Massar wrote: > > On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote: > >> One of the first Belgian ISP to deploy IPv6 (VOO) is now recommending to > >> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their > >> residential WiFi CPE... :-( > >> > >> It appears that the issue is about IPv6 web sites/apps being really > >> slower when using IPv6. > > > > Is it a DNS issue maybe? > > > > https://www.sixxs.net/faq/dns/?faq=ipv6slowconnect > > > > As that has been the general cause of "Disable IPv6!" around the > > world for many years already. > > > > Of course, without more details, little one really can say. Bug number > > maybe? > > > > Greets, > > Jeroen > > > > Yeah, a link to something that eventually leads to a bug report would be > good. > > Also if anybody has adb installed they can just try "adb shell dumpsys > connectivity --diag" and see what the over-simplified diagnostic > output shows. > > >
Re: Slow WiFi with Android Marshmallow & IPv6?
Android is properly trying to query DNS over IPv6 unlike other devices/OSes. Most other mobile platforms still prefer the querying of DNS over IPv4 for A/ RR query types. On Sun, Apr 24, 2016 at 10:17 AM, Eric Vyncke (evyncke) wrote: > Jeroen, Erik and John, > > Thanks for the hint. I will advise the ISP to investigate any DNS issue > (such as not returning an error message when requesting a non-existing > ) but I wonder why it is linked to that specific Android Marshmallow > version. > > -éric > > From: on behalf of > "Brzozowski, John Jason" > Date: Sunday 24 April 2016 at 16:01 > To: Erik Kline > Cc: Jeroen Massar , IPv6 Ops list < > ipv6-ops@lists.cluenet.de> > Subject: Re: Slow WiFi with Android Marshmallow & IPv6? > > My customers saw this issue at one point. We had issues with DNS over > IPv6. Bad DNS and/or network configurations. Once these were fixed, the > problems cleared up. > > On Sunday, April 24, 2016, Erik Kline wrote: > >> On 24 April 2016 at 19:53, Jeroen Massar wrote: >> > On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote: >> >> One of the first Belgian ISP to deploy IPv6 (VOO) is now recommending >> to >> >> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their >> >> residential WiFi CPE... :-( >> >> >> >> It appears that the issue is about IPv6 web sites/apps being really >> >> slower when using IPv6. >> > >> > Is it a DNS issue maybe? >> > >> > https://www.sixxs.net/faq/dns/?faq=ipv6slowconnect >> > >> > As that has been the general cause of "Disable IPv6!" around the >> > world for many years already. >> > >> > Of course, without more details, little one really can say. Bug number >> > maybe? >> > >> > Greets, >> > Jeroen >> > >> >> Yeah, a link to something that eventually leads to a bug report would be >> good. >> >> Also if anybody has adb installed they can just try "adb shell dumpsys >> connectivity --diag" and see what the over-simplified diagnostic >> output shows. >> >
Re: Slow WiFi with Android Marshmallow & IPv6?
My customers saw this issue at one point. We had issues with DNS over IPv6. Bad DNS and/or network configurations. Once these were fixed, the problems cleared up. On Sunday, April 24, 2016, Erik Kline wrote: > On 24 April 2016 at 19:53, Jeroen Massar > > wrote: > > On 2016-04-24 11:51, Eric Vyncke (evyncke) wrote: > >> One of the first Belgian ISP to deploy IPv6 (VOO) is now recommending to > >> its Android Marshmallow (6.0.1) users to deactivate IPv6 on their > >> residential WiFi CPE... :-( > >> > >> It appears that the issue is about IPv6 web sites/apps being really > >> slower when using IPv6. > > > > Is it a DNS issue maybe? > > > > https://www.sixxs.net/faq/dns/?faq=ipv6slowconnect > > > > As that has been the general cause of "Disable IPv6!" around the > > world for many years already. > > > > Of course, without more details, little one really can say. Bug number > > maybe? > > > > Greets, > > Jeroen > > > > Yeah, a link to something that eventually leads to a bug report would be > good. > > Also if anybody has adb installed they can just try "adb shell dumpsys > connectivity --diag" and see what the over-simplified diagnostic > output shows. >
Re: Curious situation - not urgent, but I'd like to know more
I run the IPv6 program for Comcast. Let me know how I can help. Adding my work email so I don't miss these emails. John On Saturday, December 19, 2015, Kurt Buff wrote: > All, > > I ran into an interesting situation some months ago which still > baffles me, and though I was able to work around it, I expect it will > happen again. > > We implemented MSFT DirectAcess at our company quite some time ago > (using 2008R2 and Forefront 2010), and it works extremely well. > > At least it worked well for everyone until one of the employees got > his Comcast connection upgraded, and then DirectAccess didn't work for > that employee any more. > > We proved that if he tethered to his cell phone, that would work, and > if he used an SSL VPN client while on his Comcast connect that would > work, but DirectAccess would not work at home. > > Finally, I discovered that his Comcast-installed router was handing > our IPv6 addresses on his home LAN. Turning that off enabled > DirectAccess to work again. > > We do not have an assigned IPv6 block from our ISP, though of course > MSFT OSes use it, and auto-assign themselves addresses, but for now > we're ignoring it. > > Has anyone run into this problem and solved it - not by turning off > iIPv6 address assignment for the home LAN, but really solved it? If > so, how did you do that? > > Would getting and implementing an IPv6 assignment from our ISP cure > the problem, or make it worse? > > I've found little guidance from MSFT about DirectAccess in an IPv6 > environment, though I admit I haven't been terribly diligent in my > searches. > > Kurt >
Re: Microsoft: Give Xbox One users IPv6 connectivity
Chris can you share details of the brokenness check? What variables are considered? On Thu, Oct 10, 2013 at 12:02 AM, Christopher Palmer < christopher.pal...@microsoft.com> wrote: > John and Lorenzo beat me to it J. > > ** ** > > Example: > > Samantha has native IPv6 and Teredo. > > Albert has Teredo only. > > ** ** > > Albert, in destination address selection, will chose Samantha’s Teredo > address. Samantha, in source address selection, will use her Teredo > address. This will avoid relay traversal. > > ** ** > > Xbox P2P policy is a bit more sophisticated than RFC 6724, but I note that > the avoidance of Teredo relays is also part of Windows behavior. Windows > address selection is a fairly clean implementation of RFC 6724. In RFC 6724 > terms, Teredo -> Teredo is a label match (Rule 5), Teredo -> Native IPv6 is > not. The biggest difference between us and the standard is the brokenness > check. > > > > This does complicate the dream. In order for a set of peers to use native > IPv6 – BOTH peers have to have native available. In the pathological case, > if half of the world has IPv6 and connects only to the other half that only > has Teredo, and no one actually uses native IPv6. > > ** ** > > Realistically, matchmaking is going to prefer users “close to you” (and a > bunch of other things, like their gamer behavior and stuff). Naively I > expect IPv6 traffic to start as local pockets, Albert playing against his > neighbor, both with the same ISP. As IPv6 penetration grows hopefully we’ll > see significant P2P traffic across the Internet use native IPv6 transport. > > > ** ** > > ** ** > > *From:* > ipv6-ops-bounces+christopher.palmer=microsoft@lists.cluenet.de[mailto: > ipv6-ops-bounces+christopher.palmer=microsoft@lists.cluenet.de] *On > Behalf Of *Lorenzo Colitti > *Sent:* Wednesday, October 9, 2013 8:26 PM > *To:* Geoff Huston > *Cc:* IPv6 Ops list; Christopher Palmer > > *Subject:* Re: Microsoft: Give Xbox One users IPv6 connectivity > > ** ** > > On Thu, Oct 10, 2013 at 12:19 PM, Geoff Huston wrote: > > But I've thought about your response, and if I'm allowed to dream (!), and > in that dream where the efforts of COmcast, Google etc with IPv6 bear > fruit, and I'm allowed to contemplate a world of, say, 33% IPv6 and 66% V4, > then wouldn't we then see the remaining Teredo folk having 33% of their > peer sessions head into Teredo relays to get to those 33% who are using > unicast IPv6? And wouldn't that require these Teredo relays that we all > know have been such a performance headache? > > ** ** > > Can't you fix that by telling the app "if all you have is Teredo, prefer > Teredo even if the peer has native IPv6 as well"? > > ** ** > > Of course this breaks down when IPv4 goes away, once IPv4 starts going > away then there's really way to do peer-to-peer without relays, right? > (Also, IPv4 going away is relatively far away at this point.) >
Re: Microsoft: Give Xbox One users IPv6 connectivity
Agree kudos to Chris, however, I understand that Teredo still could be preferred over native IPv6? :( I am curious how might one participate in early adopter testing? Also Comcast launched residential native IPv6 in WA state it might be interesting to get some details around how testing is going? John On Wed, Oct 9, 2013 at 4:54 PM, Tore Anderson wrote: > http://www.nanog.org/sites/default/files/wed.general.palmer.xbox_.47.pdf > > Quoting from slide 2: > > «Network operators that want to provide the best possible user > experience for Xbox One Users: > * Provide IPv6 Connectivity» > > Gamers tend to be a demanding bunch. I can tell from a ton of forum > posts and such that a common problem of theirs is that the Xbox (360) > reports the «NAT Type» as being «Moderate» or even «Strict». If word > gets around in those communities that a reliable remedy for such > problems is to switch to an ISP that supports IPv6... > > Kudos to Chris and Microsoft! > > Anyone have any information on the PS4? > > Tore >
RE: Google's "unusual traffic" notification
My case was ISATAP related. Perhaps specific to my deployment. On Jul 24, 2013 1:52 PM, "Templin, Fred L" wrote: > Hi John - are saying that you are suspecting an ISATAP problem? > > ** ** > > Thanks - Fred > > ** ** > > *From:* ipv6-ops-bounces+fred.l.templin=boeing@lists.cluenet.de[mailto: > ipv6-ops-bounces+fred.l.templin=boeing@lists.cluenet.de] *On Behalf > Of *Brzozowski, John Jason > *Sent:* Wednesday, July 24, 2013 10:27 AM > *To:* Tore Anderson > *Cc:* ipv6-ops@lists.cluenet.de > *Subject:* Re: Google's "unusual traffic" notification > > ** ** > > We have seen this in the past from corporate desktop blocks used for > ISATAP. I found this to be strange. Note I have not seen this for some > time. > > ** ** > > John >
Re: Google's "unusual traffic" notification
We have seen this in the past from corporate desktop blocks used for ISATAP. I found this to be strange. Note I have not seen this for some time. John
