I have had mixed luck with vpnc on many linux distros. I have gotten
many people at my job to switch away from the standard cisco client
but we all noticed that running vpnc command line and not through
network-manager was the way to go. For some reason, when running it
through network manager the connection just drops sometimes, for
seeminglly no good reason considering the default config is used for
both of the GUI and command line.
On 1/12/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
On Jan 12 2007 21:45, Janne Karhunen wrote:
>
>> >In a way this is a regression - vpnc almost worked in 10.1 and
>> >SLED10. It used to connect, but connections weren't that stable.
>> >In 10.2 it doesn't even connect. Cisco client next to it works
>> >ok ( given that you first manually port it to recent kernels :/ ).
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\
>>
>> Not that I can see.
>
>I was talking about commercial cisco client, not vpnc. You
>have a version of it that supports 2.4.16+ kernel?
Yes. However, since it taints the kernel because of its proprietary
license and binary blob, I am happy to have vpnc doing exactly the same
using a tunnel device. On top of that, the crappy ciscoshit does not
support NATting clients connected to your local network [VMware machines
and laptops, not the default route] even though the config has an option
for it.
-`J'
--
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
