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
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
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
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-
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.,
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
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: info Starting VPN service
'org.freedesktop.NetworkManager.vpnc'...
Apr 6 09:45:06 emissary NetworkManager: info VPN service
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
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.
--
10 matches
Mail list logo
