WAI
Status Update
Comments
vi...@google.com <vi...@google.com> #2
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
vi...@google.com <vi...@google.com> #3
A network using a router lifetime of 108 seconds is misconfigured; this forces the access points to send very frequent router advertisements, which quickly drain batteries of connected devices. For this reason, recent implementations ignore the IPv6 RA if the lifetime is too short, to avoid draining the device battery.
So this is working as intended. The network should be fixed to use a reasonable router lifetime so that IPv6 can be used without draining the battery.
hu...@huaqin.corp-partner.google.com <hu...@huaqin.corp-partner.google.com> #4
Hi Google,
Thank you very much for your professional analysis.
I have a few more questions:
1.Regarding the router lifetime setting of RA, are there any similar cases for reference so that we can communicate with the router vendor?
2.For the current scenario, is it possible to avoid this situation in the software from the user's perspective? Such as:
- Current behaviour: ignore the IPv6 RA if the lifetime is too short, to avoid draining the device battery.
- Proposed behaviour: ignore the IPv6 RA lifetime if the lifetime is too short, to avoid draining the device battery.
Thank you.
Thank you very much for your professional analysis.
I have a few more questions:
1.Regarding the router lifetime setting of RA, are there any similar cases for reference so that we can communicate with the router vendor?
2.For the current scenario, is it possible to avoid this situation in the software from the user's perspective? Such as:
- Current behaviour: ignore the IPv6 RA if the lifetime is too short, to avoid draining the device battery.
- Proposed behaviour: ignore the IPv6 RA lifetime if the lifetime is too short, to avoid draining the device battery.
Thank you.
hu...@huaqin.corp-partner.google.com <hu...@huaqin.corp-partner.google.com> #5
Hi Google,
Additional question:
What do you mean by ignore the IPv6 RA?
Does this mean that I can get an IPv6 address normally but I can't use it?
Would you describe this mechanism?
Thanks.
Additional question:
What do you mean by ignore the IPv6 RA?
Does this mean that I can get an IPv6 address normally but I can't use it?
Would you describe this mechanism?
Thanks.
Description
DEVICE:Pixel 7a
ANDROID OS VERSION: 15
BUILD-ID:AP4A.250205.002
STEPS TO REPRODUCE: (please be specific)
Two APs were found in our customer's environment. Android 14 connected normally, but Android 15 could not open the ipv6 website after connecting. We found two differences by comparing the log and sniffer.
1.The differences between ICMPv6 RA packets between OK AP and Failed AP, we found that the configuration of Failed APs is the same, they'are both "Prf (Default Router Preference): Medium (0)" and Router lifetime (s): 108.
2.After connecting to Failed APs, A14's DNS request is normal (including DNS requests for IPV4 and IPV6), while A15 only has DNS requests for IPV4.
REPRODUCE RATE:
5 times out of 5 tries
OBSERVED RESULTS:
Android 15 could not open the ipv6 website
EXPECTED RESULTS:
Android 15 could open the ipv6 website normally.
REPRODUCIBLE on Pixel/SoC Reference Device (required):Yes
BUG REPORT (Please attach a full bugreport, Logcat isn't enough):
Please refer to the attached file - Pixel-Compare
ADDITIONAL INFORMATION (please investigate root cause and share findings):
The failed AP models used in the customer environment are: Buffalo WSR-5400XE6 and Buffalo WXR-1900DHP2
Please refer to the attachment. The problem was reproduced using the Android V version of Pixel 7a in the same environment, while the Android U version of Pixel 5a was normal.
Can you help us analyze the reasons?
Thanks.