[Desktop-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=492208.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-03-25T21:44:28+00:00 Jeremy wrote:

Description of problem:
When connecting to VPN with NetworkManager-vpnc, it sets the default route to 
the VPN device.  When I connect with "vpnc" it leaves the default route alone.

There are also a couple of other routes missing when I use
NetworkManager to connect.

Version-Release number of selected component (if applicable):
NetworkManager-vpnc-0.7.0.99-1.fc10.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Connect to vpn
2.Check route with "route"
3.
  
Actual results:
0.0.0.0 0.0.0.0 0.0.0.0 U 0  00 tun0

Expected results:
0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 wlan0

Additional info:
The diff between the vpnc routing and the NetworkManager-vpnc routing is:
--- vpnc2009-03-25 14:38:59.629563747 -0700
+++ nwman   2009-03-25 14:39:25.283537596 -0700
@@ -1,7 +1,5 @@
 Kernel IP routing table
 Destination Gateway Genmask Flags Metric RefUse Iface
-10.yy.yy.yy 0.0.0.0 255.255.255.255 UH0  00 tun0
-10.zz.zz.zz 0.0.0.0 255.255.255.255 UH0  00 tun0
 xx.xx.xx.xx 192.168.1.1 255.255.255.255 UGH   0  00 wlan0
 192.168.1.0 0.0.0.0 255.255.255.0   U 2  00 wlan0
 10.69.148.0 0.0.0.0 255.255.255.0   U 0  00 tun0
@@ -32,4 +30,4 @@
 10.224.0.0  0.0.0.0 255.224.0.0 U 0  00 tun0
 10.0.0.00.0.0.0 255.192.0.0 U 0  00 tun0
 10.128.0.0  0.0.0.0 255.192.0.0 U 0  00 tun0
-0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 wlan0
+0.0.0.0 0.0.0.0 0.0.0.0 U 0  00 tun0

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/5


On 2009-04-03T23:16:23+00:00 vaxon wrote:

Same problem here.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/7


On 2009-04-04T00:22:18+00:00 vaxon wrote:

Actually, looking a bit more at the vpn configuration I can tell that
it's all configurable.

Click on the Network Manager icon and choose "VPN Connections" -> "Configure 
VPN...". Then choose the connection name and click "Edit". Go to "IPv4 
Settings" tab and click the "Routes" button at the lower-right corner.
Check off "Use this connection only for resources on its network".
This should make vpn use the old default route instead of redirecting all 
traffic to tun0.
Additional routes can be set up here as well.

But I really think that leaving the default route intact should be the
default vpnc behaviour.

Thanks,
Vax.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/8


On 2009-05-01T10:43:16+00:00 Stephen wrote:

I have a very similar problem here. But I cannot work around it using
the technique mentioned in #2 because that box is not checked.

When I connect using vpnc from the command line my name servers are
correctly tunnelled down tun0 as in the bug description. However when I
connect using NetworkManager-vpnc (default settings, and in fact every
combination of settings I have tried so far) my name servers are not
send down tun0 and consequently I cannot access any internal systems.

NetworkManager-vpnc should have the same behaviour as the vpnc command
line client.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/16


On 2009-05-01T17:54:02+00:00 Jeremy wrote:

(In reply to comment #2)
> But I really think that leaving the default route intact should be the default
> vpnc behaviour.

It must be a behaviour change, because it used to work OK.  Anyway,
checking that box does fix the problem for me.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/17


On 2009-11-05T14:33:37+00:00 Don wrote:

Confirmed that checking the box fixes the problem here as well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/330833/comments/25


[Desktop-packages] [Bug 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

2019-09-23 Thread Adam Felson
it's 2019 and the same bug still exists.

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

Title:
  NetworkManager always overwrites default route when connecting to
  OpenVPN network

Status in NetworkManager-OpenVPN:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  New
Status in network-manager package in Fedora:
  Invalid

Bug description:
  Binary package hint: network-manager

  My office VPN has IMAP, (forwarding) DNS services and not much else.
  It doesn't forward client traffic to the Internet. This means I can't
  use the VPN server as a default gateway.

  Every time I connect to the VPN using NetworkManager/OpenVPN, my
  routing table gets a default route to the VPN. I've tried everything
  to avoid this in both the Intrepid package and the version from the
  network manager PPA with no success. Even telling NetworkManager to
  ignore routes from the server doesn't work.

  As it is right now, I have to connect to the VPN, delete the default
  route, and re-add my wireless router as the default gateway before I
  can have both email and web access.

  See attached routing table details.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: network-manager 0.7-0ubuntu1~nm1~intrepid1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  Uname: Linux 2.6.27-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+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 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

2020-12-14 Thread Valerio Bozzolan
I also can reproduce this issue with NetworkManager of Ubuntu 20.04
Focal Fossa (network-manager 1.22.10-1ubuntu2.2).

If I create an OpenVPN server WITHOUT 'redirect-gateway' and if I use
the command line OpenVPN client directly as-is, it works. It does NOT
create a new default gateway (because I do not want it).

/usr/sbin/openvpn --config file.ovpn

Instead. If I import that configuration in Network Manager, the "use
this connection only for resources on this network" is unchecked and
probably that's the cause of the creation of a new additional default
route, wrong for these cases.

Any plan about how to fix this issue in NetworkManager?

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

Title:
  NetworkManager always overwrites default route when connecting to
  OpenVPN network

Status in NetworkManager-OpenVPN:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  New
Status in network-manager package in Fedora:
  Invalid

Bug description:
  Binary package hint: network-manager

  My office VPN has IMAP, (forwarding) DNS services and not much else.
  It doesn't forward client traffic to the Internet. This means I can't
  use the VPN server as a default gateway.

  Every time I connect to the VPN using NetworkManager/OpenVPN, my
  routing table gets a default route to the VPN. I've tried everything
  to avoid this in both the Intrepid package and the version from the
  network manager PPA with no success. Even telling NetworkManager to
  ignore routes from the server doesn't work.

  As it is right now, I have to connect to the VPN, delete the default
  route, and re-add my wireless router as the default gateway before I
  can have both email and web access.

  See attached routing table details.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: network-manager 0.7-0ubuntu1~nm1~intrepid1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  Uname: Linux 2.6.27-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+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 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network

2020-09-25 Thread Peter Würtz
Well, it's 2020 now. I'm stunned to see that Ubuntu chooses VPN as the
IPv6 default route, even when choosing IPv6 "Disable" in the VPN
settings :(  (completely ignored by the way).

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

Title:
  NetworkManager always overwrites default route when connecting to
  OpenVPN network

Status in NetworkManager-OpenVPN:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  New
Status in network-manager package in Fedora:
  Invalid

Bug description:
  Binary package hint: network-manager

  My office VPN has IMAP, (forwarding) DNS services and not much else.
  It doesn't forward client traffic to the Internet. This means I can't
  use the VPN server as a default gateway.

  Every time I connect to the VPN using NetworkManager/OpenVPN, my
  routing table gets a default route to the VPN. I've tried everything
  to avoid this in both the Intrepid package and the version from the
  network manager PPA with no success. Even telling NetworkManager to
  ignore routes from the server doesn't work.

  As it is right now, I have to connect to the VPN, delete the default
  route, and re-add my wireless router as the default gateway before I
  can have both email and web access.

  See attached routing table details.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: network-manager 0.7-0ubuntu1~nm1~intrepid1
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  Uname: Linux 2.6.27-11-generic i686

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