Re: [2.6.21-git2] sk_buff changes break Cisco VPN client

["Alessandro Suardi" <alessandro.suardi@gmail.com>]

On 4/28/07, Roland Dreier <rdreier@cisco.com> wrote:
> This is really a problem for Cisco support, not the kernel people.
> (And despite my email address I really have no idea who looks after
> the VPN client).

It's ok, I know it's "not a kernel issue". I just asked over here
because I saw network code already converted to the new
sk_buff code, and hoped someone could hint to a solution;
I don't think it'd be extremely fruitful to ask Cisco since I'm
already running a patched version of their latest official
Linux release, which hasn't been updated for quite a while.

> However I can suggest vpnc (http://www.unix-ag.uni-kl.de/~massar/vpnc/)
> as an alternative.  I'm not forced to use Cisco VPN access any more,
> but when I tried it, vpnc was tons better than the Cisco product.

vpnc only started supporting hybrid-auth as of very, very
recently; I used it before my company network turned to
hybrid-auth-only several months ago. It's in my sights to go
back to test vpnc-0.4.0 with the hybrid-auth support patch
in the near future. But in the meantime I'll be stuck with
the Cisco VPN client.

After clarifying all this, I'll respectfully ask again whether
anyone has an idea about how to go fixing the five or so
lines of the skb stuff impacted by the kernel changes -
and will of course take no offense if nobody can help, while
happily ignoring those who can only contribute what I do
already know, that is - this isn't a kernel issue.

Thanks again in advance, ciao,

--alessandro

"Did you get married but forgot to get divorced ?"

    (Danny and Dusty, 'The Good Old Days')
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/