Ubuntu
vpnc-scripts package

backport "vpnc-scripts: doesn't detect systemd-resolved, overwrites stub /etc/resolv.conf instead" (debian bug #1006738) to jammy lts

Bug #2018505 reported by Robert C Jennings
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
vpnc-scripts (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Confirmed
Undecided
Unassigned

Bug Description

Jammy is impacted by the deprecation of /usr/bin/systemd-resolve causing vpnc-script to fail to detect resolved and overwriting /etc/resolv.conf instead. For my usage this causes local (split, private) DNS resolution to fail when attached to my VPN.

Could we have https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006738 (import/0.1_git20210402-2) backported to Jammy LTS to address this bug? I haven't done a backport in 2 years and I'm afraid I'm too rusty.

See original description
Robert C Jennings (rcj)
Changed in vpnc-scripts (Ubuntu):
status: New → Fix Released
Robert C Jennings (rcj)
description: updated
Robert C Jennings (rcj)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in vpnc-scripts (Ubuntu Jammy):
status: New → Confirmed
Revision history for this message
Nicolas Göddel (ngoeddel) wrote :

I always wondered what completely destroyed my DNS, routes and everything around when I use `openconnect`. Its the `vpnc-script` that does not check for the symlink to `/run/systemd/resolve/stub-resolv.conf` and instead solely relies on the word `resolve` in the `hosts:` line in `/etc/nsswitch.conf`.

It is really annoying. When will there be a update to the package for Jammy?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.