Re: Bug#192747: ipv6 task
Hi Joey,
I would personally suggest to make iputils-* the defaults instead
since they also provide the normal ping, traceroute tools and add some
more like tracepath. Actually ifupdown suggests iproute. I would rather
put it as Recommends: or even Depends: since the ipv6 tunnel part of it
must have ip from iproute installed. (of course we have to take a look to
the priorites of the packages and things like that).
For the tasksel part I propose 2 kind of IPv6 tasks.
1) IPv6 gateway that should suggest a tunnel service, radvd and zebra
eventually (but that is already for advanced users). It is difficult to
decide which tunnel broker to suggest since it is pretty much related to
the ISP to which the user is connected. 6to4 is a solution that we have
been evaluating sometime ago. There were some threads about it and we have
a more or less tested script to make it working but i did not have the
time to package it properly. People are welcome to take over it.
2) IPv6 workstation that should suggest only a tunnel broker since it does
not need any other fancy software.
for both of them packages that are IPv6 enabled should be a must such as
openbsd-inetd, kernel 2.4.20 (2.4.19 has a broken ipv6), and whatever i am
missing more...
Thanks
Fabio
On Fri, 9 May 2003, Joey Hess wrote:
> I think it's time we added a task for ipv6, to pull in ping6,
> traceroute6, iproute, and anything else appopriate. Maybe an easy ipv6
> configurator like freenet6, or something using 6to4. Whatever else makes
> sense to put in. radvd?
>
> I only need some feedback from the ipv6 team on exactly what packages
> should be included, being a bit of an ipv6 novice myself.
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: