Bug 1646760

Summary: OpenConnect/vpnc does not set nameservers
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
Component: NetworkManager-vpncAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: bgalvani, code, dcbw, huzaifas, jan.public, jphxxxx, lacho.kozhuharov, lkundrak, nmavrogi, thaller
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-24 14:48:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
nmcli output when connected to the VPN. none

Description Jan Vlug 2018-11-05 23:17:46 UTC 
When I set up a OpenConnect VPN in Fedora 28 the /etc/resolv.conf is automatically modified to contain the name servers of the VPN.

In Fedora 28, after establishing the VPN connection the /etc/resolv.conf looks like:

#@VPNC_GENERATED@ -- this file is generated by vpnc
# and will be overwritten by vpnc
# as long as the above mark is intact
# Generated by NetworkManager
nameserver 192.168.a.b
nameserver 192.168.a.c
search my.domain

However in Fedora 29, after establishing the VPN connection the /etc/resolv.cinf looks still like:

# Generated by NetworkManager
nameserver 192.168.d.e

I would expect that the name servers are automatically correctly configured when setting up a VPN.
Comment 1 Beniamino Galvani 2018-11-08 09:12:15 UTC 
Can you please show the 'nmcli' output when you are connected to the VPN?
Comment 2 Jan Vlug 2018-11-09 07:40:42 UTC 
Created attachment 1503567 [details]
nmcli output when connected to the VPN.

The requested nmcli output when connected to the VPN.
Comment 3 Nikos Mavrogiannopoulos 2018-11-24 14:48:34 UTC 

*** This bug has been marked as a duplicate of bug 1648108 ***