Public bug reported:
When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search <domain>' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
first one, and so on. Depending on the network, this can cause DNS
leaks, name resolution failures, or other misbehavior.
To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 172.20.20.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/3
xfinitywifi 39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6
/org/freedesktop/NetworkManager/ActiveConnection/2
enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
-- -- --
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1
-- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.8.2 connected started full enabled enabled
enabled enabled enabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful regression-release
** Description changed:
When I connect to a wireless network that sets a DNS search domain name
- via DHCP, the line 'search domain' is added to /etc/resolv.conf as
+ via DHCP, the line 'search <domain>' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
first one, and so on. Depending on the network, this can cause name
resolution failures or other misbehavior.
To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
IpRoute:
- default via 172.20.20.1 dev wlp3s0 proto static metric 600
- 169.254.0.0/16 dev wlp3s0 scope link metric 1000
- 172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
+ default via 172.20.20.1 dev wlp3s0 proto static metric 600
+ 169.254.0.0/16 dev wlp3s0 scope link metric 1000
+ 172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=<set>
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=<set>
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
- DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
- wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/3
xfinitywifi 39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6
/org/freedesktop/NetworkManager/ActiveConnection/2
- enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
-- -- --
- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1
-- -- --
+ DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
+ wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/3
xfinitywifi 39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6
/org/freedesktop/NetworkManager/ActiveConnection/2
+ enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
-- -- --
+ lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1
-- -- --
nmcli-nm:
- RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
- running 1.8.2 connected started full enabled enabled
enabled enabled enabled
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.8.2 connected started full enabled enabled
enabled enabled enabled
** Description changed:
When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search <domain>' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
- first one, and so on. Depending on the network, this can cause name
- resolution failures or other misbehavior.
+ first one, and so on. Depending on the network, this can cause DNS
+ leaks, name resolution failures, or other misbehavior.
To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 172.20.20.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/3
xfinitywifi 39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6
/org/freedesktop/NetworkManager/ActiveConnection/2
enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
-- -- --
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1
-- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.8.2 connected started full enabled enabled
enabled enabled enabled
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1713457
Title:
DNS search domain not removed from resolv.conf on disconnect
Status in network-manager package in Ubuntu:
New
Bug description:
When I connect to a wireless network that sets a DNS search domain
name via DHCP, the line 'search <domain>' is added to /etc/resolv.conf
as expected. But if I then disconnect and connect to a different
network, it is not removed from resolv.conf. If the second network
also sets a search domain name, that one gets appended to resolv.conf
along with the first one, and so on. Depending on the network, this
can cause DNS leaks, name resolution failures, or other misbehavior.
To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 172.20.20.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
CONNECTION CON-UUID CON-PATH
wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/3
xfinitywifi 39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6
/org/freedesktop/NetworkManager/ActiveConnection/2
enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
-- -- --
lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1
-- -- --
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.8.2 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
