[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-07 Thread Tim Shannon
The DNS servers have always been listed under the vpn0 link when I run systemd-resolve --status, even before your patch. I still get no internal network name resolution, even when hard coding the DNS servers in network manager. Maybe I've got a different issue than what others are seeing, but I

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-07 Thread Tim Shannon
Thanks for taking your time to work though this. My link name is vpn0 Link 3 (vpn0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: DNS Domain: ~. Link 2

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-06 Thread Tim Shannon
Maybe I'm doing something wrong, but I installed the deb, and even did a full reboot, and I'm still leaking my personal IP in the DNS leak test, and am still unable to ping servers on the inside of the VPN network when connected to the ANY connect VPN. -- You received this bug notification

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-06 Thread Tim Shannon
Not working for me, but I assume that's because I'm using network- manager-openconnect-gnome? -- 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/1624317 Title: systemd-resolved

[Desktop-packages] [Bug 1685646] Re: 'dpkg-reconfigure lirc' doesn't work as expected.

2017-04-28 Thread Tim Shannon
Is there any work around or eta? I just setup an HTPC and the remote doesn't work properly without being able to run the config wizard. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu.