Daniel Drake wrote:
Peter wrote:
Well. I can't see the future :) But in the current situation,
I have to look for workarounds like, mentioned by you, installation from
package cd and then patching kernel. And I do not see any steps
forward. So I told never. Of course may be one day...

It just seems to me that the original post was a stab at gentoo kernel development rather than any hope of starting any constructive discussion...


But may be there is a possibility to create ebuild, which will download
the patch from http://www.polbox.com/h/hs001/ , and then patch the kernel?
I think this ebuild can be GPL'ed, but then user can decide does he want
this bad kernel headers and other code be changed or not.

Because the patch isn't GPL it means we can't include it in our tree without changing the licensing of our kernel (I don't think this would go down well). It's licensing is ok on its own, but what you suggest in an ebuild isn't practical, and would create lots of issues due to variation between kernel versions. If the author could recode it as a kernel module then that would be a start.
Also, this does not address points 2 and 3 in my last post, which still prevent us from including this.


Daniel

--
Granted.

But here's my question: is this issue not occurring solely because the user is trying to connect to said VPN through software?

My ISP uses VPN as well, and at the moment I connect via the LAN using software routing on a Windows machine (the presence of Windows bypasses the OP's issue). However, we are waiting for a router, which supports VPN in hardware and is compatible with both UNIX and Windows, and is configured via a web interface.

So if the OP had such a router (or, alternatively, if and when I get my bf to switch to Linux, making this a one-OS household), such a kernel patch would no longer be necessary, would it (because the router understands VPN perfectly well, so as long as I give it the correct configuration details, it would work fine)?

Or am I missing something (I'm no network guru ;-) )?

Holly

--
[email protected] mailing list



Reply via email to