Ralph Passgang dixit:
>The implementation of ipv6 is not so hard to understand (at least for the
>parts that might be important here):
>
>if ipv6 is available (as module or compiled in the kernel) then each time a
>interface gets configured, so that it has the status "up", it automaticly
>gets an ipv6 link-local address. Additional the ipv6 stack will scan on the
>interface for routers that are announcing networks.
This is funny. BSD does rtsol only if enabled globally, and
the rtsol or rtsold programme is run on the interface.
>Later on eth0.0 is initialized. It binds THE SAME link local address, because
>eth0 and eth0.0 has the same mac adress (the same link local address for two
>devices can also be not correct in my opinion).
Is eth0 used anyway, or only eth0.0? Can one set eth0 to down
without downing eth0.0 as well?
Looks like the implementation of interface aliases collides.
>the interface is up and at this point the link local adress at least is also
>already active and would need to gets deactivated manually (by a script or
That shouldn't do harm though…
>I thought it would be the best to handle this via the /etc/network/interfaces
>file
Could you provide patches?
>opt/svn/freewrt/staging_dir_mipsel/bin/mipsel-linux-uclibc-gcc -lc -o
>libz.so.1.2.3 adler32.o compress.o crc32.o gzio.o uncompr.o deflate.o trees.o
>zutil.o inflate.o infback.o inftrees.o inffast.o
Obviously missing a -shared or -Bshared or whatever.
bye,
//mirabile
--
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- Henry Nelson, March 1999
_______________________________________________
freewrt-developers mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-developers
