AdguardForAndroid
AdguardForAndroid copied to clipboard
AdguardTeam
Automatically detect IPV6 to automatically switch on and off IPV6 filtering
Issue Details
In an IPV4 Only environment, some APPs cannot be opened after dual-stack DNS resolution. The reason is that they prioritize V6 access, but cannot be accessed because the network does not have an IPV6 address (cannot fall back to IPV4 result).
Proposed solution
Through the detection method, if it is detected that an existing connection (such as WiFi) only has an IPV4 address and the IPV6 address starts with fe80::, filtering of the IPV6 network will be automatically disabled and AAAA records will no longer be parsed. This function is automatically restored if there is an available IPV6 address (such as NAT6, 2000::/8).
Alternative solution
No response
@Extreme-Icer Thank you for suggestion! We have a couple questions about the current state of affairs.
Do these apps behave correctly on a IPv4 only network with AdGuard disabled? When these apps struggle to launch, is the IPv6 filtering option in AdGuard enabled or disabled?
Could you also provide examples of problematic apps?
@Extreme-Icer Thank you for suggestion! We have a couple questions about the current state of affairs.
Do these apps behave correctly on a IPv4 only network with AdGuard disabled? When these apps struggle to launch, is the IPv6 filtering option in AdGuard enabled or disabled?
Could you also provide examples of problematic apps?
1.disabled adguard,ipv4only network use app corretly; 2.IPV6 filter enabled,these use IPV6 First app in NO IPV6 Address environment will spend more time(seconds)to try IPV6,then use IPV4.disabled IPV6 filter will normally.the proxy has IPV4+V6 but local network v4only. example app:bilibili
@Extreme-Icer Thank you for providing additional info! We will consider the proposed solution and find the optimal way to solve this case.