[Bug 1768203] Re: Connecting to a VPN clears DNS from parent connection
This works without problems, and without using `ipv4.dns-priority`, on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768203 Title: Connecting to a VPN clears DNS from parent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
The patch from #19 (which is now in Ubuntu) is not enough - there are still problems with network-manager-sstp, which calls pptp with "nm- sstp-service-*". If there's no better workaround, can the userpeerdns and 000resolveconf scripts at least bail on all "nm-*-service-*"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768203] Re: Connecting to a VPN clears DNS from parent connection
This helps, but there's still a problem - resolved tries to resolve the VPN-local addresses with both VPN and global DNS. Some of those addresses are available on both sites, and I prefer the internal one when the VPN is active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768203 Title: Connecting to a VPN clears DNS from parent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276941] Re: fstrim-all should not be run on mdadm devices
Still a problem on Bionic on Hyper-V: fstrim: /boot: FITRIM ioctl failed: Invalid argument -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276941 Title: fstrim-all should not be run on mdadm devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1276941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768203] [NEW] Connecting to a VPN clears DNS from parent connection
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy network-manager network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status After connecting to a VPN the parent connection's DNS servers are cleared, as seen in the output of `systemd-resolve --status`. Before connection to VPN: (...) Link 3 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 62.179.1.63 62.179.1.62 DNS Domain: chello.pl Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Connected to VPN, notice that only the ppp0 has DNS servers: (...) Link 20 (ppp0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.64.5 192.168.97.10 DNS Domain: ~dcs.pl Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no I want to use split-horizon DNS resolving, and this behaviour breaks resolving non-VPN names. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768203 Title: Connecting to a VPN clears DNS from parent connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes
~jonathanharker could you check if `nmcli connection show 'CONNECTION NAME' | grep DNS` shows the nameservers you expect? You can list connection names with `nmcli connection`. This way we'll make sure if the problem happens between NM and the VPN or NM and resolved (for me it was the latter, and the attached patch fixed it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691996 Title: DNS and search domain is not pushed to systemd-resolved sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes
There is a fix posted on the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=779087 - I've attached a ported patch. ** Bug watch added: GNOME Bug Tracker #779087 https://bugzilla.gnome.org/show_bug.cgi?id=779087 ** Patch added: "Port of patch from Patch from https://bugzilla.gnome.org/show_bug.cgi?id=779087 to network-manager 1.4.4-1ubuntu3.1" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+attachment/4935380/+files/dns-config-for-unmanaged-vpn-iface.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691996 Title: DNS and search domain is not pushed to systemd-resolved sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341496] [NEW] corosync hangs inside libqb
Public bug reported: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy libqb0 libqb0: Installed: 0.16.0.real-1ubuntu3 Candidate: 0.16.0.real-1ubuntu3 Version table: *** 0.16.0.real-1ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Corosync sometimes hangs inside libqb. I've looked at a hanged process with gdb, and I think I've found the problem. The problem is the loop here: https://github.com/ClusterLabs/libqb/blob/v0.16.0/lib/ringbuffer.c#L451 This was fixed in 0.17.0, see: https://github.com/ClusterLabs/libqb/blob/v0.17.0/lib/ringbuffer.c#L451 I think bumping to 0.17.0 should fix this (at least in backports? Please?) ** Affects: libqb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341496 Title: corosync hangs inside libqb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1341496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069640] [NEW] xrandr --prop sets backlight to 100%
Public bug reported: OS Version: Description:Ubuntu 12.10 Release:12.10 $ uname -a Linux beast 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Hardware: Samsung NP300V5-S06PL (but Samsung doesn't know they made it - don't bother asking them about it. It's like somebody took a non-polish i7 300V5 and slapped polish software on it) CPU: i7-2670QM GPU: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) - NVIDIA Corporation GF119 [GeForce GT 520MX] (by Optimus, this one is actually disabled with bumblebee) xrandr --prop is setting backlight to 100%. This has some interesting effects: - xbacklight -set X always fades from 100% to requested brightness - xbacklight -dec X always works relatively to 100% - after switching the screen off and on (for example by a lockscreen), the brightness is set to 100% - before upgrade (on 12.04), using fn buttons under Unity was putting it into an endless loop of jumping between max/just a step lower brightness (while eating as much CPU cycles as a single core could give it :-)) sysfs acts funny too: # cat /sys/class/backlight/acpi_video0/max_brightness 7 # echo 2 > /sys/class/backlight/acpi_video0/brightness# this actually sets the brightness # cat /sys/class/backlight/acpi_video0/actual_brightness # shouldn't this be 2? 7 # cat /sys/class/backlight/acpi_video0/brightness 2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: backlight brightness xrandr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069640 Title: xrandr --prop sets backlight to 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1069640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
