Thanks Hadley, Indeed you need a license to work with it, the admin from the remote network provided it for me part of my contract with them.
Yes, it does need a compilation against kernel sources but during the un-install / install process required by every kernel upgrade I had no compilation error. The service component starts ok but the client part doesn't want to connect to the remote router. The answer is: Initializing the VPN connection. Secure VPN Connection terminated locally by the Client Reason: Failed to establish a VPN connection. There are no new notification messages at this time. And no more log entries. On Thu, 2006-04-06 at 21:54 +1200, Hadley Rich wrote: > On Thursday 06 April 2006 21:41, Adrian Mageanu wrote: > > I use cisco vpn from here > > http://www.cisco.com/univercd/cc/td/doc/product/vpn/client/4_6/uglinsol/ind > >ex.htm to connect to a remote network. > > > > It used to work ok until I upgraded the kernel to > > 2.6.16-1.2069_FC4smp.i686 > > > > Although the documentation says that the cisco client does not work with > > SMP kernels, I had no problem runing it on all previous kernel versions > > from 2.6.11-1.1369 through 2.6.15-1.1833, all SMP versions. > > > > The workaround is I boot the box in the previous kernel and works. > > > > What is different in the latest kernel release from the previous? Is > > there a way to fix this? Other than the above mentioned. > > I see that that client involves a loadable module. I can't find the license > so > don't know whether it is proprietary or not. If it is the following might > relate. > > On Arch Linux (which is quite bleeding edge) recently the Intel modem drivers > (intel536ep and intel537) stopped working due to a change in the kernel > regarding loading non-GPL modules. > > I can't find a lot about it on the web but this was the reason quoted on the > list "The drivers no longer compile against 2.6.16, as the serial interface > in 2.6.16, only links with drivers distributed under the GPL." > > Since then the kernel change has been reversed and the modules work again. > > Maybe this relates to your problem? > > hads
