Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

VPN does not handle switching networks very well.

Open
#17 6 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin

Research direction

Reproduce the issue in the Android app on Android 10 by connecting the VPN and switching between WiFi and LTE, including the Sonim XP8 environment described. Confirm that network transitions do not leave the VPN dropped or the app unresponsive, and that the connection can be reset without using system settings.

Written by the indexing model from the issue text.

Description

needs investigating
Describe the Bug

I've been using Pangolin for a while now, and really enjoy it, and decided to deploy it on a few edge clients. i.e. Android phones, tablets, etc.

I've noticed that when I leave the office (disconnect from WiFi) my VPN drops, and glitches out to the point where the app is unresponsive and I can't kill the VPN without doing it from system settings.

I cannot enable always-on VPN in settings as mentioned in #12 which may be part of the problem.

When I "hop" networks things tend to go awry, and to reset, I have to kill the VPN from settings and flick it back on.

Environment
  • OS Type & Version: Android 10.0.0 - Sonim XP8
  • Pangolin Version: 1.15.1
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6.7
  • Newt Version: 1.9.0
  • Client Version: 0.1.7

Use case: Punching SIP traffic over VPN. (Works great! Except for these small hiccups!)

To Reproduce

Connect to VPN via app, switch networks. (WiFi -> LTE, WiFi -> WiFi, LTE -> WiFi)

Expected Behavior

Connection should not drop / app should not hang.

Dominant language
Kotlin
Stars
45
Forks
12
Avg merge
1m
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fosrl/android

All issues in fosrl/android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.