Arch Linux

valmar

Member

Registered: 2007-03-14

Posts: 55

Recently emerged problem with vpnclient

Dear all,

          after a recent update, a problem started to emerge about vpnclient, the Proprietary Cisco client (I have to use it, as vpnc won't allow me to connect to my VPN server at work). However, adter one of the last updates, something happened.

When I start the connection, everything looks fine, with no errors. However, as soon as I connect, I lose all traffic. I cannot surf the internet, I cannot contact any machine on my network at work, nothing. The only thing I can do is ping the other end of the tunnel. This happens with all vpnclient connections. Some of these connections work well with vpnc but give me this error with vpnclient.

I tried several versions of vpnclient: 4.8.01.0640, 4.8.02.0030 even the "official" version of the University where I work. No change. So, I guess it must not be  client problem. I am guessing it could be the kernel, since it is the only other major update between the moment vpnclient worked and the moment it din not anymore.

Iam of course working on Arch64. anyone else has had nay problems with vpnclient?

  Thank you

         Valerio

Last edited by valmar (2009-02-25 16:19:26)

niljo

Member

Registered: 2008-08-28

Posts: 1

Re: Recently emerged problem with vpnclient

Hi

I have the exact same problem and I'm running on the i686 architecture (kernel26 2.6.28.7).
A friend of mine is running the client on gentoo with kernel26 2.6.28.5 without any problems :-/

valmar

Member

Registered: 2007-03-14

Posts: 55

Re: Recently emerged problem with vpnclient

Yes, this is annoying! I think at the same time the package "route" was also updated. Would it be possible for the kernel developers to take a look into this? It seems to me to be a routing problem

       Valerio

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Recently emerged problem with vpnclient

You haven't provided very much info to work with. Does the vpn client create any logs? If so, they might be useful. Try downgrading kernel26 and iproute2 to see if that helps. Do them separately first, then together.

I can't be sure, but it's possible that no Arch dev uses the Cisco client, so it may be hard to get an official answer on this.