New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wi-Fi calling issue with AdGuard (and other VPNs) and its solution #2550
Comments
Thanks ameshkov, Working with zzebrum I also added the exclusion: 88.82.11.0/24 And that was the first time I was able to get WiFi calling working on Vodafone UK without having to flick in to flight mode and disable AG for a moment to get connected. Should I leave that in the exceptions along with the 2 other you mention to add: 88.82.11.221/32 Thanks. |
@Lurchus |
Hi @ameshkov, Help wanted. I wish to enable From differnt issues, the IPv4 and IPv6 addresses for SFR VPN servers are publicly known:
But how to configure my device in the 1st place to add/configure VPN access and enable Many thanks, |
Was having trouble getting Wi-Fi calling to work while using AdGuard but I stumbled upon this post on how to fix it. (Smart Philippines) Sharing the folllowing ePDG IPs used by our carriers here in the Philippines for Wi-Fi calling activation: // epdg.epc.mnc003.mcc513.pub.3gppnetwork.org // weconnect.globe.com.ph (Globe uses a different domain for their ePDG servers. Similiar to how AT&T does it) // epdg.epc.mnc066.mcc513.pub.3gppnetwork.org |
I`m having issues getting Wi-Fi calling to work while using AdGuard v3.6.8 on Xiaomi Poco F3: // epdg.epc.mnc010.mcc724.pub.3gppnetwork.org Then I would like to know what is correct parameter (mask) to be add after IPs addresses: Regards, |
Yeah, Please let me know if this helped. |
Thank you for your inputs. //Vivo Brazil Wi-Fi calling VoLTE/Wi-Fi seem to be working fine know but I 'll let you know if have any issue. |
Hi @ameshkov // Vivo Brazil Wi-Fi calling But after a few days I realize that VoWiFi doesn't register when move from 4G network to WiFi if AdGuard filtering method (local VPN) is enabled. When VoWiFi is connected with local VPN the VoWiFi connection drops randomly or when answering an incoming call. |
Here are ePDGs of all major carriers in Czech Republic I double checked every IP using icann lookup tool Vodafone CZ ePDG O2 CZ ePDG T-Mobile CZ ePDG |
Tbh, no idea what could be causing this since the routes are excluded regardless of whether you're connected to 4G or Wi-Fi :( |
Maybe some IPv6 range configuration or exclusion is needed but I don't know how to handle it. Do you have any input about this issue? |
@Birraque the only more or less normal way to troubleshoot this is to capture the system bug report right after reproducing the issue. Here's the instruction. The log inside the bug report will contain lines from the process named Here's an example of what we're looking for:
|
I`ll do that. |
Hi there, I got a new phone and I'm using it with the same Adguard settings and SIM as my old one, which totally worked fine regarding WiFi Calling. With my new phone WiFi Calling doesn't work anymore when Adguard is activated. I figured out the ePDG for Vodafone Germany, at least the one which are in the Adguard logs: epdg.epc.mnc002.mcc262.pub.3gppnetwork.org Corresponding IPs are 139.7.117.168 and 139.7.117.169 So, I set them in pref.ipv4.routes.excluded and WiFi-Calling was on for 10 seconds than back off again. Did I miss something or what else can I do? Thanks a lot and best regards, |
Hi @ameshkov My carrier (Vivo Brazil) is currently on going rollout to 5G (DSS/NSA/SA) network and this has caused instabilities in services. // Vivo Brazil Wi-Fi calling Subnet Calc (Screenshots) for epdg.epc.mnc010.mcc724.pub.3gppnetwork.org AdGuard is running smoothly now with VoLTE/VoWiFi and I can confirm that both values are correct and could be included in the future AdGuard builds. |
I use Chunghwa Telecom LDM and excluded it NOT work for me, so now I turn off adguard in com.qualcomm.qti.cne at app management then look good. Unless you are adamant that all traffic has to go through adguard I think this is a solution too |
Hello, for Movistar Spain there are problems: MCC is 214, and MNC is 07 |
To the moment, we'd had multiple complaints on Wi-Fi calling being incompatible with AdGuard. In this issue, I'll explain what's going on and how we can solve this.
How it works
Any Wi-Fi network is considered untrusted (compared to the provider's own network) so in order to transfer voice data, your phone must establish a secure encrypted tunnel with the provider's server called ePDG [1].
The tunnel is encrypted and uses IPSec so basically this is another VPN. ePDG server discovery is simple: all ePDG server names look like
epdg.epc.mnc%MNC%.mcc%MCC%.pub.3gppnetwork.org
where%MNC%
is your provider's Mobile Network Code, and%MCC%
is its Mobile Country Code. You can find these values of your provider here: http://www.mcc-mnc.com/. Both values are padded with zeros to the length of 3.Why is there a problem with AdGuard (or other VPNs)
Android cannot establish a tunnel with the ePDG when this connection is routed through a VPN. Presumably, it happens due to a bug in the Android's IPSec client, and we should file a bug report about it. It shows connections as
0.0.0.0->ePDG IP
instead of something like192.168.11.x->ePDG IP
(the socket is not bound to a proper local interface), and that's why it can send data to the tunnel, but it cannot receive it.Example of a temporary solution (manual)
You can figure what your ePDG server is and exclude it from the VPN. In this case, the tunnel connection won't be routed through a VPN, and you won't run into this issue.
For instance, for Vodafone UK,
MCC
is234
, andMNC
is either15
or91
. Knowing this we can figure what IP addresses do ePDG servers have.We should simply lookup these two domains:
epdg.epc.mnc015.mcc234.pub.3gppnetwork.org
andepdg.epc.mnc091.mcc234.pub.3gppnetwork.org
. Only the first one of them resolves, and the IP addresses are88.82.11.221
and88.82.11.208
.Once you have these addresses, do the following:
pref.ipv4.routes.excluded
and tap on itAdGuard solution
This section is for devs.
We are yet to figure how to discover the current operator's ePDG server automatically. Once we know it, we can simply add it's IP addresses to the excluded routes. The problem here is that I don't want us to ask for Telephony permission, that'd be too much for such a simple thing.
Another possible solution would be to exclude the
UID
that establishes the ePDG tunnel. It seems that it's done by/system/bin/eris
(uid=1000).Android bug
I've filed a bug report to Android devs:
https://issuetracker.google.com/issues/124415915
The text was updated successfully, but these errors were encountered: