| 2015-08-08 16:24:41 |
d3bugg3r |
bug |
|
|
added bug |
| 2015-08-08 16:24:41 |
d3bugg3r |
attachment added |
|
network-manager dns problem https://bugs.launchpad.net/bugs/1482887/+attachment/4441437/+files/NM-DNS-problem.png |
|
| 2015-08-08 16:43:44 |
d3bugg3r |
description |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================-==============-==============-============================================
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and use
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/I382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and use
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/I382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
|
| 2015-08-08 17:08:03 |
d3bugg3r |
description |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and use
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/I382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and use
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
|
| 2015-08-08 17:10:27 |
d3bugg3r |
description |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and use
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
|
| 2015-08-08 17:12:28 |
d3bugg3r |
description |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head and
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
|
| 2015-08-08 19:32:11 |
d3bugg3r |
description |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head
Since this can lead to users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I check the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17
# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler
--------------------------------------------------
So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...
Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect
In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)
So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head
Since this can lead users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I checked the 'Security' box.
This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437 |
|
| 2015-08-11 17:52:53 |
d3bugg3r |
information type |
Private Security |
Public |
|
| 2015-08-11 18:20:38 |
d3bugg3r |
information type |
Public |
Public Security |
|
| 2015-08-15 18:25:35 |
d3bugg3r |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=753664 |
|
| 2015-08-15 18:25:35 |
d3bugg3r |
bug task added |
|
network-manager |
|
| 2015-08-15 22:25:58 |
Bug Watch Updater |
network-manager: status |
Unknown |
Confirmed |
|
| 2015-08-15 22:25:58 |
Bug Watch Updater |
network-manager: importance |
Unknown |
High |
|
| 2015-08-22 01:19:49 |
Bug Watch Updater |
network-manager: status |
Confirmed |
Incomplete |
|
| 2015-09-09 14:13:36 |
Marc Deslauriers |
network-manager (Ubuntu): status |
New |
Confirmed |
|
| 2015-10-06 21:54:24 |
pablomme |
bug |
|
|
added subscriber pablomme |
| 2017-07-19 16:26:30 |
Bug Watch Updater |
network-manager: status |
Incomplete |
Expired |
|
