Public bug reported:

Binary package hint: vpnc

Upgrading from Feisty to Gutsy has broken my Cisco VPN, but I'm not sure
how to diagnose it.

Under Feisty, I could use either the command line "sudo vpnc" or use
NetworkManager to connect to my company's network, and it worked fine.
Apparently there's also an "official" Cisco client, but you need a
kernel compiled before the fall of the Berlin Wall to make it work (ie
RedHat).

When I say "the VPN worked fine", I mean:

-Requests to the corporate network were routed OK.  I could:
  VNC to a desktop at work
  SMB onto a drive at work etc
-Requests to my local network were unaffected, I could still:
  see my router's webface
  SMB to my housemate's Windows box
-Requests for internet traffic were unaffected, I could
  receive web-pages via my home internet connection
  use messenger programs etc

Under Gutsy, the VPN appears to connect fine (it does not disconnect
immediately, this is *not* a duplicate of 124238).  However, nothing at
all is accessible, neither the corporate network, nor the internet.

Without the VPN, NetworkManager (which I'm using for wireless roaming) creates 
a file that simply says:
search myHomeDomain
nameserver 192.168.2.1 (myHomeRouter)
That works fine, because the default route just goes straight to the router 
which gets name resolution etc from my ISP.

With the VPN connected however, I get a resolv.conf like this:
search myHomeDomain myCorporateDomain
nameserver corporateDNS1
nameserver corporateDNS2
This is useless, as I no longer can see the internet!  So, I manually add 
"nameserver 192.168.2.1", and that works as a quick fix, but I didn't need to 
do that under Feisty - regression.

More importantly, the VPN doesn't work - despite the routing table being
populated with a load of corporate internal IP addresses, I can't
actually see any of them.  They don't reply to pings, I can't SMB
anything, yet the connection is alive, I see tun0 under ifconfig.

What information do I need to diagnose the problem?
Why did this work before, and not now?

BTW, before you ask,

"Why did he upgrade to an unstable release on a box needed for work?"
Because Evolution in Feisty is fundamentally broken - useless for accessing 
Exchange server.  The latest Evolution is a *little* better (though still 
essentially useless for doing real work), but is not backported to Feisty.  
Doing a partial upgrade to Gutsy to get newer Evolution broke everything 
(Nautilus etc.) so I did a full dist-upgrade.  Also it seemed an easier way to 
move from Beryl to CompizFusion.

Help!!

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

-- 
VPNC broken after gutsy upgrade
https://bugs.launchpad.net/bugs/132044
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

Reply via email to