Describe the Bug
I have a a google pixel 8 pro with grapheneos installed and can successfully connect to my pangolin.
Applying settings like upstream dns or download logs do not apply on reconnect.
Force killing pangolin app and restarting it needed.
Note: my pangolin app showed it was connected to a newt site even when disconnected. That seems awkward and might have to do with this bug
Environment
- OS Type & Version: GrapheneOS (Android 16)
- Pangolin Version: 1.18.3
- Gerbil Version:
- Traefik Version:3.6.16
- Newt Version: 1.12.5
- Client Version: 0.1.11
To Reproduce
Install Pangolin on a grapheneos/android smartphone (some recent pixel). Connect to pangolin with a private resource defined. Disconnect
Set dns configs for upstream server configured as a private resource on pangolin.
Enable logs.
Connect. Check on dns server if queries reach it. With Termux install dig and test directly querying it. It should work. Check downloading logs
However upstream DNS is not used on OS level and pangolin logs show that they are disabled
Expected Behavior
Settings should be applied without having to resort to force killing the app.
Describe the Bug
I have a a google pixel 8 pro with grapheneos installed and can successfully connect to my pangolin.
Applying settings like upstream dns or download logs do not apply on reconnect.
Force killing pangolin app and restarting it needed.
Note: my pangolin app showed it was connected to a newt site even when disconnected. That seems awkward and might have to do with this bug
Environment
To Reproduce
Install Pangolin on a grapheneos/android smartphone (some recent pixel). Connect to pangolin with a private resource defined. Disconnect
Set dns configs for upstream server configured as a private resource on pangolin.
Enable logs.
Connect. Check on dns server if queries reach it. With Termux install dig and test directly querying it. It should work. Check downloading logs
However upstream DNS is not used on OS level and pangolin logs show that they are disabled
Expected Behavior
Settings should be applied without having to resort to force killing the app.