Hello, I don't have direct answer to your questions as I don't know much about the 2.4 kernel code.
However, I just want to give these four comments about IPV6 in 2.4 Linux kernel: 1) Also in the latest 2.6 kernels you cannot "rmmod ipv6" when it is configured as a module, although work is done to enable this in the future. So you can ignore or not treat too seriously this "unloading bug when IPv6 is configured as a module" note about the 2.4 kernel you mentioned 2) As far as I know, most test suites for IPV6 are not compatible with the 2.4 kernels (for example, TAHI Conformance Test: http://www.tahi.org/conformance/). I did not check this point though. 3) The 2.4 kernel does not have any IPSec support (not for IPV6 ; I think that also not for IPV4). IPSec is mandatory according to the latest IPV6 spec and is optional in IPV4 spec (although most operating systems, including Linux and OpenSolaris had implemented it also as part of IPV4). See, for example, in RFC 2401, (Security Architecture for the Internet Protocol), although it is **not** mentioned in your list. from rfc 2401: ... ... 10. Conformance Requirements "All IPv4 systems that claim to implement IPsec MUST comply with all requirements of the Security Architecture document. All IPv6 systems MUST comply with all requirements of the Security Architecture document.". .. .. 4) The only tunnel you have in 2.4 IPV6 is sit (IPv6 in IPv4 tunnel). At least in the link for 2.4 code you mention in your mail. (maybe it does exist in newer versions of 2.4) You don't have the ip6_tunnel ("ip6tnl") which is IPV4 or IPV6 in IPV6. (Though this is relatively easy to implement, based on the 2.6 implementation) Regards, Rami Rosen On Sun, Mar 16, 2008 at 4:38 PM, Oleg Goldshmidt <[EMAIL PROTECTED]> wrote: > Hi folks, > > I suppose there are some people here who for one reason or another still run > kernel 2.4 on servers or embedded systems and are willing to admit to it. > > Can anyone tell me how well kernels circa 2.4.19 (or later) support the > *current* IPv6 specification? I see IPv6 support in the code > (http://lxr.linux.no/linux-old+v2.4.19/net/ipv6/) which is marked as > EXPERIMENTAL and carries warnings in the configuration, but it looks like > this is associated with some unloading bug when IPv6 is configured as a > module (http://lxr.linux.no/linux-old+v2.4.19/net/Config.in). The same > warning appears in 2.4.31 which is the last 2.4 in LXR at least. > > Suppose I will be happy to compile IPv6 into the kernel (not as a module) - > I am still interested in how well 2.4 supports today's IPv6. More > specifically, after some research I have come to a conclusion that I am > interested in assessment of 2.4 support for (at least) the following: > > * IPv6 (RFC2460) > * ICMPv6 (RFC 4443) > * Neighbor discovery for IPv6 (RFC2461) > * Path MTU discovery for IP6 (RFC1981) > * Address configuration - either SLAAC (RFC2462) or DHCPv6 (RFC3315) > * IPv6 addressing architecture (RFC4291) > * Scoped address architecture (RFC4007) > * Unique local IPv6 unicast addresses (RFC4193) > * Multicast listener discovery (MLD) for IPv6 (RFC2710) > > Can anyone shed light on the above (any V's or X's will help, as will "don't > even think of it")? Is anyone running 2.4 in IPv6 environments? How > mature/up-to-date is the support? > > If IPv6 is a requirement, does it absolutely mandate moving to > 2.6.{latest,recent-enough} or will 2.4 be possible? Is there any version of > 2.4 from which IPv6 support is markedly better than in earlier ones? > > I have seen http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/ and > http://www.deepspace6.net/docs/best_ipv6_support.html, among others. It is > not clear to me how updated the info related to old kernels is. If anyone > knows that I can trust these documents that will be great. > > Let's not go into the question why 2.4 is important, OK? > > Thanks a lot in advance, > > -- > Oleg Goldshmidt | [EMAIL PROTECTED] > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
