(Copied back to the list, as the list filtered the original message with the 
screen capture attachment)

For the info of the list. This is what the rdisc6 provided:

Hop Limit:              64 (0x40)
Stateful address cons.: No
Stateful other cons.:   Yes
Router preference:      medium
Router lifetime:        1800 (0x00000708) seconds
Reachable time:         unspecified (0x00000000)
Retransmit time:                unspecified (0x00000000)

 MTU:                   1472 bytes (valid)
 Source link-layer address:     2C:CF:58:E5:7C:C0
 From fe80::1

Right, but how this is affecting IPv4 push notifications ?

My understanding is that the servers doing the “push”, as the WAN link has not 
got IPv6, are doing the push with IPv4.

I could understand that Android may be slower to react to dual-stack traffic 
because there is a default route announced by the router with no GUA, but 
getting the push ?

By the way, anyone got rdisc6 working in Mac OS X El Capitan ?

Regards,
Jordi









-----Mensaje original-----
De: Erik Kline <[email protected]>
Responder a: <[email protected]>
Fecha: martes, 10 de mayo de 2016, 4:41
Para: Jordi Palet Martinez <[email protected]>
CC: Lorenzo Colitti <[email protected]>
Asunto: Re: push apps failing in Android until you disable IPv6

>Uh...non-zero router lifetime means it's announcing a default route.
>That seems unwise.
>
>On 10 May 2016 at 02:49, JORDI PALET MARTINEZ
><[email protected]> wrote:
>> Just got a “screen” capture from one of those situations (rdisc6).
>>
>> Hopefully is useful ! They made it from a virtual machine in the same 
>> network as the Androids have the problema, having the VMware interfaces in 
>> bridge mode.
>>
>> Saludos,
>> Jordi
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -----Mensaje original-----
>> De: <[email protected]> en nombre 
>> de Erik Kline <[email protected]>
>> Responder a: <[email protected]>
>> Fecha: lunes, 9 de mayo de 2016, 10:59
>> Para: Jordi Palet Martinez <[email protected]>
>> CC: IPv6 Ops list <[email protected]>, Lorenzo Colitti 
>> <[email protected]>
>> Asunto: Re: push apps failing in Android until you disable IPv6
>>
>>>If this router were to send out an RA advertising itself as a default
>>>router in this configuration that would probably cause the symptoms
>>>you're seeing.  That's why I asked for a sample of any RAs seen on
>>>such a network.  (Such a configuration would of course be broken,
>>>effectively requiring Happy Eyeballs to function at all.)
>>>
>>>On 9 May 2016 at 17:52, JORDI PALET MARTINEZ <[email protected]> 
>>>wrote:
>>>> Hi Lorenzo,
>>>>
>>>> I don’t have an Android, so I can’t try myself, unfortunately, so I’m just 
>>>> replicating what several folks told me in a training (people from 
>>>> different ISPs, not just one).
>>>>
>>>> I’ve asked already a few days ago for more info, but still didn’t got it. 
>>>> I also asked to open a bug report as Erik suggested as well as the rdisc6 
>>>> from the same LAN.
>>>>
>>>> Let me try to write it down again the issue:
>>>>
>>>> 1) ISP NOT providing IPv6, but CPE supports IPv6, which can be seen in the 
>>>> router configs and the routers has link local, and you can ping with link 
>>>> local to the router in the LAN. Clearly, router has not GUA.
>>>>
>>>> 2) iPhone working fine.
>>>>
>>>> 3) Android fails to receive IPv4 push from whatsapp, Facebook, others, 
>>>> when screen is off.
>>>>
>>>> 4) Disabling IPv6 in the router the problem disappears.
>>>>
>>>> 5) Complains to ISPs are responded with “disable IPv6 in the router”, is 
>>>> not useful at all :-(
>>>>
>>>> I can provide links to web pages from at least one “big” ISP, where they 
>>>> talk about this, but is in Spanish …
>>>>
>>>> I will ping right now again for more info and come back asap.
>>>>
>>>> Thanks !
>>>>
>>>> Regards,
>>>> Jordi
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----Mensaje original-----
>>>> De: <[email protected]> en 
>>>> nombre de Lorenzo Colitti <[email protected]>
>>>> Responder a: <[email protected]>
>>>> Fecha: lunes, 9 de mayo de 2016, 10:41
>>>> Para: Jordi Palet Martinez <[email protected]>
>>>> CC: IPv6 Ops list <[email protected]>
>>>> Asunto: Re: push apps failing in Android until you disable IPv6
>>>>
>>>>>Jordi,
>>>>>from your report it's not clear what the problem is. You say that the 
>>>>>problem disappears when IPv6 is disabled on the router, but then you say 
>>>>>that it also happens on an IPv4-only network. How can those statements 
>>>>>both be true?
>>>>>
>>>>>It's not usually possible to disable IPv6 on an Android device unless the 
>>>>>device is rooted, which usually involves installing a non-stock build 
>>>>>which may behave differently.
>>>>>
>>>>>Also, please clarify what device you're talking about. Stock Android 
>>>>>should not have this problem, but some OEMs are known to drop IPv6 packets 
>>>>>when the screen is off.
>>>>>
>>>>>Cheers,
>>>>>Lorenzo
>>>>>
>>>>>On Sat, Apr 30, 2016 at 9:03 PM, JORDI PALET MARTINEZ 
>>>>><[email protected]> wrote:
>>>>>
>>>>>Hi,
>>>>>
>>>>>I’m not an Android user, but while doing and IPv6 training, many folks in 
>>>>>the meeting room told me that they needed to disable IPv6 in the 
>>>>>router/Android devices, otherwise they aren’t getting the notifications 
>>>>>from WhatsApp, Facebook, and many other apps.
>>>>>
>>>>>We have tried disabling energy saving options in Android, and it seems the 
>>>>>problems is not there. Basically, if the Android device is in stand-by, 
>>>>>notifications don’t come, until you “open” the Android. Apple and Windows 
>>>>>devices don’t have this problem.
>>>>>
>>>>>The scenario seems to happen regardless of the type of CPE (some observed 
>>>>>this with ADSL, others with GPON).
>>>>>
>>>>>Just for having a “stable scenario” were to try, we have actually 
>>>>>replicated this problem with Android 4.4 and 5.1, with an ONT Huawei 
>>>>>HG8245H, hw v 494.B and firmware v V3R013C00S106.
>>>>>
>>>>>We have tried using both the ONT as the wireless AP and also disabling the 
>>>>>WiFi on the ONT and using an external AP. Same problem in both situations.
>>>>>
>>>>>Don’t look like an issue related to a specific ISP, because the situation 
>>>>>happens in many different ISPs, and of course none of them provides IPv6 
>>>>>:-(
>>>>>
>>>>>I’m specially worried because the ISPs are telling the users to disable 
>>>>>IPv6 everywhere …
>>>>>
>>>>>Any hints ?
>>>>>
>>>>>Regards,
>>>>>Jordi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>


Reply via email to