[Touch-packages] [Bug 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

2017-04-12 Thread Giovanni Panozzo
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

Solved with dnsmasq-base 2.75-1ubuntu0.16.04.2, thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1680226

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1680226/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

2017-04-06 Thread Aron Xu
*** This bug is a duplicate of bug 1639776 ***
https://bugs.launchpad.net/bugs/1639776

** This bug has been marked a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1680226

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1680226/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1680226] Re: Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

2017-04-06 Thread Giovanni Panozzo
Ubuntu 17.04 seems to work very well with my split DNS setup. Also with
multiple VPN connections at the same time.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1680226

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1680226/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp