[Bug 364844] Re: network-manager-vpnc produces incorrect routing table

[Lonnie]

Public bug reported:

Although, by manually using vpnc via a command prompt, I don't get this
problem, when I use the GUI provided in Ubuntu 9.04 GNOME netowork-
manager-vpnc (to do a Cisco VPN connection), it doesn't honor split-
tunneling.

While connected to the virtual private network, the GUI enabled VPN
connection sends all traffic accross the tunnel. Therefore:

-I'm unable to reach any destination that is not in the virtual private network. Therefore,
-I'm unable to reach my local dns server, and
-I'm unable to surf the web locally while being connected to the VPN.

However, when I use vpnc mannually from a command prompt, instead
traffic is routed correctly; only traffic destined for the virtual
private network gets sent through the tunnel, and other traffic
appropriately gets routed through my local network (such as DNS
request).

Using the GUI VPN, if my machine makes a request for my local dns server
at 192.168.54.1, instead of sending that to the local machine, it gets
sent accross the tunnel, and since that's not where the DNS server is,
it doesn't resolve.

So, GUI VPN connections don't honor split-tunneling configurations on
Cisco VPNs, but manual command line vpnc does.

Please forgive my redundancy, but I wanted to make it very clear what
the problem is, and the manifestations of this problem.

I look forward to this bug being fixed, because it will allow me to do
vpn connections quickly through the GUI, instead of having to type at
several prompts.

Respectfully,

Lonnie Lee Best
Wilson Wade Vick CPNA

** Changed in: network-manager-vpnc (Ubuntu)
       Status: New => Confirmed

-- 
network-manager-vpnc produces incorrect routing table
https://bugs.launchpad.net/bugs/364844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs