Bug 1401319 - Using dnsmasq for DNS in NetworkManager fails after VPN reconnect
Summary: Using dnsmasq for DNS in NetworkManager fails after VPN reconnect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnsmasq
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL: http://lists.thekelleys.org.uk/piperm...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-04 18:17 UTC by Rolf Fokkens
Modified: 2017-08-18 08:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-18 08:48:08 UTC
Type: Bug


Attachments (Terms of Use)
Temporary workaround pending the upstream solution (640 bytes, text/plain)
2016-12-04 18:55 UTC, Rolf Fokkens
no flags Details

Description Rolf Fokkens 2016-12-04 18:17:04 UTC
Description of problem:
When setting dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf DNS resolving via the VPN works after the inital connection, but fails after reconnecting.

Version-Release number of selected component (if applicable):
dnsmasq-2.76-1.tgho2.fc25

How reproducible:
100%

Steps to Reproduce:
1. set dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf
2. make a VPN connection
3. disconnect the VPN
4. make a connection using the same VPN
5. note DNS resolving results in REFUSED when querying VPN hosts

Actual results:
REFUSED

Expected results:
DNS lookup

Additional info:

Comment 1 Rolf Fokkens 2016-12-04 18:50:26 UTC
It is a known issue upstream:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q4/010949.html

However:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q3/010831.html

It may take a while until it propagates to Fedora.

Comment 2 Rolf Fokkens 2016-12-04 18:55:17 UTC
Created attachment 1227942 [details]
Temporary workaround pending the upstream solution

Comment 3 Tomáš Hozza 2016-12-05 13:29:28 UTC
(In reply to Rolf Fokkens from comment #0)
> Description of problem:
> When setting dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf DNS
> resolving via the VPN works after the inital connection, but fails after
> reconnecting.
> 
> Version-Release number of selected component (if applicable):
> dnsmasq-2.76-1.tgho2.fc25

This build is not an official Fedora build. Please reproduce the issue with the latest official Fedora build and let us know.

Comment 4 Rolf Fokkens 2016-12-05 15:05:02 UTC
Sorry, I copy/pasted my (temporary) fixed release. The actual issue is in dnsmasq-2.76-1.fc25.

Comment 5 Tomáš Hozza 2016-12-05 15:33:38 UTC
(In reply to Rolf Fokkens from comment #4)
> Sorry, I copy/pasted my (temporary) fixed release. The actual issue is in
> dnsmasq-2.76-1.fc25.

Can you please retest with http://koji.fedoraproject.org/koji/buildinfo?buildID=821058 ?

Comment 6 Rolf Fokkens 2016-12-05 21:37:46 UTC
Yep, this one solves the issue!

Comment 7 Rolf Fokkens 2016-12-05 21:48:43 UTC
I see, the patch is the forementioned commit:

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2675f2061525bc954be14988d64384b74aa7bf8b

Including a fix for the SIGSEGV I presume.

Comment 8 Fedora Admin XMLRPC Client 2017-02-16 21:25:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.


Note You need to log in before you can comment on or make changes to this bug.