Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66261 - [networkmanager-openconnect] resolv.conf not updated when server provides IPv6 nameservers

Attached to Project: Arch Linux
Opened by Omar Sandoval (osandov) - Tuesday, 14 April 2020, 22:48 GMT
Last edited by Jan de Groot (JGC) - Friday, 20 November 2020, 11:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When connecting to an OpenConnect VPN with IPv6 nameservers using networkmanager-openconnect 1.2.6-1, /etc/resolv.conf is not updated with any nameservers. This is fixed by the following upstream commit: https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/commit/de44e42509d85c0ce94492441b5aa70a90d186fb. See https://www.spinics.net/lists/fedora-package-announce/msg272340.html and https://bugzilla.redhat.com/show_bug.cgi?id=1753422. I tested applying that patch and it fixed the issue for me. It should suffice to apply that patch until another upstream release is cut.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 20 November 2020, 11:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1.2.7dev+49+gc512d5a-1
Comment by Omar Sandoval (osandov) - Thursday, 10 September 2020, 18:25 GMT
This bug is still valid. It should be an easy fix of applying https://gitlab.gnome.org/GNOME/NetworkManager-openconnect/-/commit/de44e42509d85c0ce94492441b5aa70a90d186fb. How can I help move this along?
Comment by Kevin Murphy (kemurphy) - Sunday, 18 October 2020, 04:08 GMT
Any updates here?
Comment by Omar Sandoval (osandov) - Monday, 19 October 2020, 07:53 GMT
Looks like the recent update fixed this, thanks!

Loading...