MaGoo, please open a separate bug for your issue, as it is related to
the openvpn plugin and not the VPNC plugin.
It appears to me like this bug has really been fixed since Intrepid or
Jaunty, following the initial description from the bug reporter: routes
now being imported by the plugin from vpn
The bug always exist:
I connect my computer with cable on eth0. The default route was the gateway on
eth0
I connect my openVPN tunnel for split tunneling. When it connected, the default
gateway was the IP of end tunneling. At this time, it is missing a route for
the tunnel connexion. I need to h
I can confirm that Doug's hint solved my problem
(https://bugs.launchpad.net/ubuntu/+source/network-manager-
vpnc/+bug/207506/comments/13). This checkbox should be disabled by
default.
I agree to this.
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/2
I'd have to respectfully disagree -- although I ran into the same
problem and also find it annoying to have to go so far to fix such a
simple issue -- AFAIK, checking this effectively enables what is called
"Split-tunnelling", and is considered a potential security issue in many
environments.
On t
Had this problem since upgrading to Jaunty. The checkbox did indeed fix
it and I agree that the default should be changed. I believe this is how
most people expect a VPN to work.
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
You received this
Never had this problem on Intrepid or Hardy when connecting the network
of my university via nm-vpnc. Problem occurred on jaunty for the first
time (fresh install).
I can confirm that Doug's hint solved my problem
(https://bugs.launchpad.net/ubuntu/+source/network-manager-
vpnc/+bug/207506/comment
This problem presented itself to me during the upgrade from Intrepid to
Jaunty, with no other changes to the network or VPN setup. On Intrepid,
everything worked fine. On Jaunty (beta as of 4/18/2009), all traffic
was going to the VPN which was not properly resolving Internet domains
(e.g., yahoo
Solution found in (pre-release) Jaunty!
>From the VPN tab of the Network Connections window, select a VPN
connection and click Edit. From the IPv4 Settings tab, click the
Routes... button near the bottom of the window. The "Use this
connection only for resources on its network" checkbox will pre
Here's my sample NM output from var/log/daemon.
Note that the first time it failed to connect and I do not know why.
Apr 6 09:45:06 emissary NetworkManager: Starting VPN service
'org.freedesktop.NetworkManager.vpnc'...
Apr 6 09:45:06 emissary NetworkManager: VPN service
'org.freedesktop.N
I can confirm this bug is present in Jaunty.
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I had the "default route only" issue when using Hardy. nm-vpnc has been
working perfectly for me since upgrading to Intrepid (months ago). It
now installs the correct routes and behaves pretty much exactly as vpnc
does. Currently using network-manager-vpnc
0.7~~svn20081015t024626-0ubuntu1.
--
This seems to exist still in the intrepid release version.
Nm-vpnc connects correctly, but the routing tables aren't changed so the
vpn-tunnel is used as default-route.
Via vpnc(-connect) this works fine. I experienced this on 2 new installations
of ubuntu 8.10 final.
With nm-vpnc 0.6.4svn2422-0u
This appears to be fixed in the current network-manager
(0.7~~svn20080928t225540-0ubuntu1) in intrepid. This issue seems to me
like it comes from network-manager-vpnc's lack of support for importing
the routes (which are handed to nm-vpnc from vpnc) into the network-
manager system. Not sure where
I am also encountering this issue. Unfortunately, this is also affected
several of my customers. I tried to follow the instructions listed at
the above link and the results are attached.
As with everyone above, launching vpnc-connect from the command line
works perfectly. Here is the routing table
This apparently happens because NM uses its own vpnc-script:
http://osdir.com/ml/network.networkmanager.devel/2006-03/msg00084.html
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
You received this bug notification because you are a member of Ub
Same here. Minimal VPNC config on my end.
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Don't think that is it. My vpnc etc is still default. I have never
created a vpnc config file but have only entered the parameters at the
cli:
With nm-vpnc connection--
[EMAIL PROTECTED]:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window i
Could this have something to do with the fact that nm-vpnc lacks support
for different settings that vpnc-connect uses (eg. through a config
file)? See for example Bug #165237 for one such problem.
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
Marking as confirmed
** Changed in: network-manager-vpnc (Ubuntu)
Status: New => Confirmed
--
nm-vpnc and vpnc-connect produce different routing tables
https://bugs.launchpad.net/bugs/207506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Having exact same issue-- vpnc-connect and network-manager-vpnc both
authenticate and bring up tun0, but vpnc-connect sets up routes properly
and network-manager-vpnc does not:
Default Boot
[EMAIL PROTECTED]:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Fl
20 matches
Mail list logo
