A workaround may be to edit /etc/NetworkManager/NetworkManager.conf and
comment out the line "dns=dnsmasq".
** Description changed:
- Using a laptop with a hardware switch for enable/disable WLAN.
- Connected to two different LANs using DHCP on ETH/WLAN.
+ I have a laptop with a hardware switch to enable or disable the WLAN
+ interface.
- When both interfaces are active (in different networks), the system uses the
LAN interface as the default route as expected.
- But it does not use the the nameserver on that interface consistently.
- It often tries to use the WLAN nameserver which leads to trouble as the WLAN
nameserver does not know about the hosts on the LAN.
+ I am connected to two different LANs using DHCP via eth and wlan,
+ respectively.
+
+ When both interfaces are active (in different networks), the system uses
+ the LAN interface as the default route as expected.
+
+ However, it does not use the the nameserver on that interface
+ consistently. It often tries to use the WLAN nameserver which leads to
+ trouble as the WLAN nameserver does not know about the hosts on the LAN.
The nameserver should be taken from the same interface as the default
route to avoid messups.
Ubuntu 12.04 did not have that behavior.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
Uname: Linux 3.15.0-031500rc2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 15 14:28:46 2014
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
InstallationDate: Installed on 2014-04-24 (20 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IpRoute:
- default via 10.1.1.254 dev eth0 proto static
- 8.0.0.0/24 dev vboxnet0 proto kernel scope link src 8.0.0.1
- 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.42 metric 1
+ default via 10.1.1.254 dev eth0 proto static
+ 8.0.0.0/24 dev vboxnet0 proto kernel scope link src 8.0.0.1
+ 10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.42 metric 1
NetworkManager.state:
- [main]
- NetworkingEnabled=true
- WirelessEnabled=true
- WWANEnabled=true
- WimaxEnabled=true
+ [main]
+ NetworkingEnabled=true
+ WirelessEnabled=true
+ WWANEnabled=true
+ WimaxEnabled=true
RfKill:
- 0: phy0: Wireless LAN
- Soft blocked: yes
- Hard blocked: yes
+ 0: phy0: Wireless LAN
+ Soft blocked: yes
+ Hard blocked: yes
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2014-04-30T15:18:11.879306
nmcli-con:
- NAME UUID TYPE
TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
- Wired connection 1 58608da7-d199-4c51-a8f4-a7913363637f
802-3-ethernet 1400156985 Do 15 Mai 2014 14:29:45 CEST yes
no /org/freedesktop/NetworkManager/Settings/2
- afxhome 213a5a1b-daf7-4b28-b682-6c8934b20e4d
802-11-wireless 1400132352 Do 15 Mai 2014 07:39:12 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
- AtSec guest 6d860806-d458-4de0-bfcb-8e40c2185437
802-11-wireless 1400141574 Do 15 Mai 2014 10:12:54 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
+ NAME UUID TYPE
TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
+ Wired connection 1 58608da7-d199-4c51-a8f4-a7913363637f
802-3-ethernet 1400156985 Do 15 Mai 2014 14:29:45 CEST yes
no /org/freedesktop/NetworkManager/Settings/2
+ afxhome 213a5a1b-daf7-4b28-b682-6c8934b20e4d
802-11-wireless 1400132352 Do 15 Mai 2014 07:39:12 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
+ AtSec guest 6d860806-d458-4de0-bfcb-8e40c2185437
802-11-wireless 1400141574 Do 15 Mai 2014 10:12:54 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
- DEVICE TYPE STATE DBUS-PATH
- wlan0 802-11-wireless unavailable
/org/freedesktop/NetworkManager/Devices/1
- eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/0
+ DEVICE TYPE STATE DBUS-PATH
+ wlan0 802-11-wireless unavailable
/org/freedesktop/NetworkManager/Devices/1
+ eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
- RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
- running 0.9.8.8 connected enabled disabled
disabled enabled enabled
+ RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
+ running 0.9.8.8 connected enabled disabled
disabled 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/1319805
Title:
DNS confused with multiple interfaces (eth/wlan)
Status in network-manager package in Ubuntu:
New
Bug description:
I have a laptop with a hardware switch to enable or disable the WLAN
interface.
I am connected to two different LANs using DHCP via eth and wlan,
respectively.
When both interfaces are active (in different networks), the system
uses the LAN interface as the default route as expected.
However, it does not use the the nameserver on that interface
consistently. It often tries to use the WLAN nameserver which leads to
trouble as the WLAN nameserver does not know about the hosts on the
LAN.
The nameserver should be taken from the same interface as the default
route to avoid messups.
Ubuntu 12.04 did not have that behavior.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
Uname: Linux 3.15.0-031500rc2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 15 14:28:46 2014
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2014-04-24 (20 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
IpRoute:
default via 10.1.1.254 dev eth0 proto static
8.0.0.0/24 dev vboxnet0 proto kernel scope link src 8.0.0.1
10.1.1.0/24 dev eth0 proto kernel scope link src 10.1.1.42 metric 1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2014-04-30T15:18:11.879306
nmcli-con:
NAME UUID TYPE
TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY
DBUS-PATH
Wired connection 1 58608da7-d199-4c51-a8f4-a7913363637f
802-3-ethernet 1400156985 Do 15 Mai 2014 14:29:45 CEST yes
no /org/freedesktop/NetworkManager/Settings/2
afxhome 213a5a1b-daf7-4b28-b682-6c8934b20e4d
802-11-wireless 1400132352 Do 15 Mai 2014 07:39:12 CEST yes
no /org/freedesktop/NetworkManager/Settings/1
AtSec guest 6d860806-d458-4de0-bfcb-8e40c2185437
802-11-wireless 1400141574 Do 15 Mai 2014 10:12:54 CEST yes
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless unavailable
/org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8 connected enabled disabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1319805/+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
