mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 14:47:04 -05:00
[GH-ISSUE #2512] Linux pangolin cli olm-dns.conf persist if not typing in "pangolin down" #6974
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#6974
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iclonethefirst on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2512
Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
It isn't really a bug I would say, it is intentional design, but it can lead to issues.
I was logged in with "pangolin up" and then shutdown my laptop. Upon rebooting I wasn't able to connect to the internet, but could still access network devices. My system uses NetworkManager.
After a lot of digging I finally found out that "pangolin up" creates the file "olm-dns.conf" and after removing it, I finally had internet again.
Is there maybe a way to avoid this issue somehow? Some less advanced users could struggle a lot and not be able to fix it.
The first debug step I tried was to start and stop the VPN, since I figured this was the cause, but since there was no internet available, it wasn't possible.
Environment
OS Type & Version: openSUSE tumbleweed (Kernel 6.19.2-1-default), GNOME
Pangolin CLI Version: 0.3.3
Olm Version: (don't know how to find it)
To Reproduce
=> no internet since it grabs wrong DNS
Expected Behavior
No manual intervention needed
@LaurenceJJones commented on GitHub (Feb 26, 2026):
I opened the same issue on the cli repo https://github.com/fosrl/cli/issues/38
@oschwartz10612 commented on GitHub (Feb 26, 2026):
Yeah lets track there thanks!