On Tue, 5 Sep 2000, Andries Brouwer wrote:
: I described the cause on Mon, 14 Aug 2000, and soon afterwards
: [EMAIL PROTECTED] sent a corrected (I hope - didnt check)
: patch to l-k. (Look for: Pekka Riikonen, Re: devfs / eth micro-problems)
:
: I see that this patch didnt make it into 2.4.0tes
Enclosed is a patch that exports some IPv6 specific symbols on 2.4 so that
finally IPv6 is accessible from modules. I bet there are bunch of other
functions that needs to be exported as well but this is a start. There
are also various IPv6 functions in 2.2 that should be exported for the
same r
: What needs access to these ipv6 symbols? Do tell...
:
For example, any module that performs packet manipulation for example in
netfilter hooks using IPv6. Currently such modules might be impossible to
do if they need to for example copy and resend packets (they also might
need to do route loo
: I mean show me real code, not hypothetical examples.
:
Like code that I'm doing currently though not ready and not to be
included into the main kernel. The point is that corresponding IPv4
symbols are exported as well why should we restrict IPv6? I bet after
IPv6 is used more commonly the ne
4 matches
Mail list logo