Push notifications (FCM) stop working while the VPN is connected

Abierto
#67 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
android, kotlin

Línea de trabajo

Start by reading NetworkSettingsPoller.applySettingsToBuilder, the location named in the report, and review the proposed exclusion of Google Play Services from the VPN tunnel. Reproduce the failure with the reported ADB dumpsys command, then verify FCM reconnects after Wi-Fi and mobile network changes while private resources remain reachable.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the Bug

With the Pangolin VPN connected, Google push notifications (FCM) stop arriving after a while. This affects every app (messaging, Home Assistant, etc.) and happens on Wi-Fi and mobile data alike. As soon as the VPN is disconnected, FCM reconnects within seconds and delivers the queued messages.

I tested with adb:
adb shell dumpsys activity service com.google.android.gms/.gcm.GcmService

With the VPN connected:

not connected:
Next backoff interval per network:
  GcmNetwork{215 VPN(17) [WiFi(1)]}, PT4H
...
Connecting using McsConnection{GcmNetwork{215 VPN(17) [WiFi(1)]}, type=1, isVpnConnected=true}
Failed connection err:3
Connecting using McsConnection{GcmNetwork{215 VPN(17) [Cell(0)]}, type=0, isVpnConnected=true}
Failed connection err:3

Every attempt on the VPN network failed usually within 15–50 ms, and the backoff grows to 4 hours. An FCM connection opened before the VPN came up keeps working until it drops, which is why it looks like "after a while".

When the VPN is disconnected, the same dumpsys immediately shows Is client connected: true followed by Successful broadcast to ... for the queued messages.****

Here some pointers:

  1. dumpsys connectivity shows the VPN as VpnTransportInfo{type=1, sessionId=pangolin, bypassable=false ...} covering all UIDs. FCM uses a bypass for its push channel only on VPNs that allow it (Firebase docs); here it has to connect through the VPN network, and that fails.
  2. Ordinary sockets through the same VPN work: from adb shell, nc -4 mtalk.google.com 5228 succeeds and DNS resolves normally (the client's DNS proxy forwards to the upstream). So the tunnel itself passes traffic; only the GMS push connection on the VPN network fails.
  3. Not related to battery: Pangolin is in the user doze whitelist (unrestricted). Not related to the DNS upstream setting. The test networks have no global IPv6, so IPv6 isn't involved.

I did a small patch, by excluding Google Play Services from the tunnel inside NetworkSettingsPoller.applySettingsToBuilder.
Tested on a 0.8.2 debug build (arm64): the VPN stays bypassable=false, its UID ranges skip the GMS UID, FCM connects on the underlying network and reconnects after Wi-Fi off/on and Wi-Fi / mobile switches, and private resources keep working (But, on another note, a "per app" VPN would be even better.).

Environment
  • OS Type & Version: Debian 13 (trixie) x86_64,Android 17 (Pixel 9)
  • Pangolin Version: 1.25.3
  • Edition (Community or Enterprise): Community
  • Gerbil Version: 1.5.2
  • Traefik Version: v3.7
  • Newt Version: 1.16.0
  • Client Version: 0.8.2 (Play Store)
To Reproduce

Steps to reproduce
Connect the Pangolin VPN on Android.
Leave the phone idle until the existing FCM connection drops (or toggle Wi-Fi off/on).
Run adb shell dumpsys activity service com.google.android.gms/.gcm.GcmService: you'll see Not connected and repeated Failed connection err:3.
Disconnect the VPN: FCM connects immediately.

AI Disclosure

Ai assisted formatting.

Expected Behavior

With the VPN connected, Google push notifications (FCM) should keep arriving as they do without the VPN.

Google Play Services should be able to reconnect its push channel at any time: after the phone has been idle, after Wi-Fi goes off and on, and when switching between Wi-Fi and mobile data.

A split-tunnel VPN that only carries private resources shouldn't block notifications for every other app on the phone.

Lenguaje dominante
Kotlin
Estrellas
46
Forks
15
Merge medio
1 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fosrl/android

Todos los issues de fosrl/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.