Christoph, Unfortunately, this is a company-provided vesion of the Cisco VPN, so I'm loathe to change anything. Also odd is the fact that my version is labeled as 4.6, while the http://www.unix-ag.uni-kl.de/~massar/vpnc/ version is labeled 3.x....
Just struck me as odd that there is so much code devoted to whether the tun device is there or not that if it could be genericized it would be better. -Jared On 3/28/06, Christoph Thielecke <[EMAIL PROTECTED]> wrote: > Helllo Jared, > > > I'm trying to get a variant of the Cisco VPN client working with > > kvpnc. The particular client uses a program called vpnclient, which > > is most likely a varient of the vpnc program. The major difference is > > that kvpnc seems to always be looking for a tun device to be > > configured. I assume that this is the device that vpnc sets up to > > create the vpn tunnel. In my case the tunnel device is called cipsec0 > > (rather than tun0). I tried changing the device name in the general > > setup to cipsec0, but that doesn't seem to have any affect. The > > underlying code is still looking for the tun kernel module and tun > > device file. > You are trying to get the original Cisco client running which is not supported > by KVpnc. I recommenend to use vpnc which is a replacement for the original > cisco client. > > The device name is not enough. The whoole support for the original cisco > client is missing. > > > Any ideas on how to change this? > For now I dont see the requirement to support of the original cisco client > because vpnc has nearly all features, is free and some limitations are not > there. > > So my recommendation is to install vpnc. > > > Best regards > > Christoph > -- > Linux User Group Wernigerode > http://www.lug-wr.de/ > > > _______________________________________________ > Kvpnc-user mailing list > [email protected] > https://mail.gna.org/listinfo/kvpnc-user > > > > _______________________________________________ Kvpnc-user mailing list [email protected] https://mail.gna.org/listinfo/kvpnc-user
