Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add more ePDG IP subnets to the default routes exclusions #4049

Closed
ameshkov opened this issue Dec 6, 2021 · 1 comment
Closed

Add more ePDG IP subnets to the default routes exclusions #4049

ameshkov opened this issue Dec 6, 2021 · 1 comment
Assignees
@SergeyBerdov
Labels
Enhancement Junior+ P4: Low Resolution: Duplicate Status: Closed

Comments

@ameshkov
Copy link
Member

ameshkov commented Dec 6, 2021

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
// SMART Philippines Wi-Fi calling
203.87.172.0/24
121.54.55.0/24

// weconnect.globe.com.ph (Globe uses a different domain for their ePDG servers. Similiar to how AT&T does it)
// Globe Philippines Wi-Fi calling
112.198.111.0/24

// epdg.epc.mnc066.mcc513.pub.3gppnetwork.org
// DITO Telecommunity Wi-Fi calling
131.226.94.0/24
131.226.92.0/24

Originally posted by @carlosalbornoz in #2550 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SergeyBerdov SergeyBerdov

Labels
Enhancement Junior+ P4: Low Resolution: Duplicate Status: Closed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ameshkov @adguard-bot @SergeyBerdov