[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-11-09 Thread themroc
I have exactly the same Problem like User Orange Shiang-Yuan Kao
(orange-kao) wrote on 2017-03-22 in Comment #10 in duplicate Bug 1671606
since upgrading to

Kubuntu 17.10

https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1671606/comments/10

-- 
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/1688018

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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


[Desktop-packages] [Bug 704123] Re: Network Manager asks for the PIN even if it is memorized

2015-01-20 Thread themroc
You can solve the problem if you uncheck the option All users can
connect with this network in connection settings.

-- 
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/704123

Title:
  Network Manager asks for the PIN even if it is memorized

Status in One Hundred Papercuts:
  Triaged
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager package in Debian:
  New

Bug description:
  
  HOW TO REPRODUCE
  

  1. Plug the USB modem into a port.

  2. When you are asked to enter the modem's PIN, do along with the
  automatically unlock this device option.

  3. Unplug the modem, and plug it again.

  **
  EXPECTED BEHAVIOUR
  **

  - The modem to be automatically unlocked.

  **
  REAL BEHAVIOUR
  **

  - You are asked to enter the PIN again.

  
  WORK-AROUNDS
  

  - Changing the SIM's PIN to empty.

  - Renaming the /usr/share/nm-applet/gsm-unlock.ui file.

  
  
  RELEVANT DETAILS
  

  - The same behaviour when configuring the PIN from the Network
  Connections menu.

  - Even if the PIN is stored in /etc/NetworkManager/system-
  connections/, Network Manager cannot retrieve it.

  - The bug makes the device to become locked as soon as network
  connectivity is lost for a while.

  - This bug forces administrators to tell the PIN to other users, while
  they will rather want to keep it in secret and just allow themselves
  to be able to configure the connectivity in specific devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/704123/+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


[Desktop-packages] [Bug 1404894] [NEW] newly added network printer does not work in 14.10

2014-12-22 Thread themroc
Public bug reported:

We have five Kubuntu-Notebooks/PCs and 2 network Printer (IP based, Port 9100)  
at home.
Before the Upgrade to 14.10 not at all notebooks were both printer installed.

After the upgrade to 14.10, I must realize, that only those printer
works, which was installed befor upgrading to 14.10.

Newly added network printer does not work in 14.10:
I cannot see the printer properties and it is not possible to print and after 
sending the print job, there is nothing in the print queue.
After a restart of Kubuntu  the print jobs become visible in the print queue, 
but the now  visible  print jobs will not be processed.
And the printer properties are still not visible.

Only printers that were installed before the upgrade to 14.10 work after
the upgrade.


cups: 1.7.5-3ubuntu2

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1404894

Title:
  newly added network printer does not work in 14.10

Status in cups package in Ubuntu:
  New

Bug description:
  We have five Kubuntu-Notebooks/PCs and 2 network Printer (IP based, Port 
9100)  at home.
  Before the Upgrade to 14.10 not at all notebooks were both printer installed.

  After the upgrade to 14.10, I must realize, that only those printer
  works, which was installed befor upgrading to 14.10.

  Newly added network printer does not work in 14.10:
  I cannot see the printer properties and it is not possible to print and after 
sending the print job, there is nothing in the print queue.
  After a restart of Kubuntu  the print jobs become visible in the print queue, 
but the now  visible  print jobs will not be processed.
  And the printer properties are still not visible.

  Only printers that were installed before the upgrade to 14.10 work
  after the upgrade.

  
  cups: 1.7.5-3ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1404894/+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