does busybox actually support IPv6?

[Jason Schoon]

On 5/18/06, Robert P. J. Day <rpjday at mindspring.com> wrote:
>
>
>   i ask given the following snippets from networking/interface.c:
>
> ===========================
>
> ...
>
> #ifdef CONFIG_FEATURE_IPV6
> # define HAVE_AFINET6 1           <--  OK ...
> #else
> # undef HAVE_AFINET6
> #endif
>
> ...
>
> #ifdef KEEP_UNUSED
>
> static int flag_unx;
> static int flag_inet;
>
> static struct aftrans_t {
>         char *alias;
>         char *name;
>         int *flag;
> } aftrans[] = {
>
>         {
>         "ip", "inet", &flag_inet},
> #ifdef HAVE_AFINET6                <-- ... and ...
>         {
>         "ip6", "inet6", &flag_inet6},    <-- hello?
> #endif
>         {
>         "inet", "inet", &flag_inet},
> #ifdef HAVE_AFINET6
>         {
>         "inet6", "inet6", &flag_inet6},
> #endif
>         {
>         "unix", "unix", &flag_unx}, {
>         "tcpip", "inet", &flag_inet},
>         {
>         0, 0, 0}
> };
>
> ...
> ===========================
>
>   notice what's missing?  a definition of "flag_inet6".  wouldn't this
> be a problem?  or is there something happening here just too tricky
> for me to appreciate?
>
> rday
>

Our products are now all mandated to support IPv6, and I use it very often.
I haven't seen any issues currently with Busybox and IPv6.  I have submitted
patches for a few things missing in the past, and have a few more pending.

Did you notice that all of that code is wrapped in a #ifdef KEEP_UNUSED, so
it is not currently active?  (I dislike that name greatly BTW, I think
wrapping it in an #if 0 or just deleting it would be much cleaner, but
Manuel may have had his reasons).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060518/3f88045e/attachment.htm