[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Test of d-i in IPv6-only environment (was: Bug#686970: Inconsistent ipv6 handling of localhost in netbase and netcfg)



On Wed, Sep 19, 2012 at 09:00:07PM +0200, Karsten Merker wrote:
> I have run several tests of d-i (AMD64 netboot mini.iso dated
> 2012-09-19 00:12) in an IPv6-only environment, mainly using
> stateless autoconfiguration with RDNSS announcements.

Thank you very much for your testing. Much appreciated.

> - When the router announcements have "AdvOtherConfigFlag" set to
>   "On", i.e. they tell the client to do a DHCPv6 request for
>   additional (non-address) information, and the DHCPv6 server
>   does not respond, the client seems to infinitely try to get
>   a DHCPv6 reply.  After about 10 minutes I have killed the
>   dhcp6c process, but that results in the whole network
>   configuration process starting from the beginning.
>   I have attached the corresponding syslog part.
> 
>   Having router announcements with AdvOtherConfigFlag On and
>   a non-responding DHCPv6 server should of course not happen
>   in a correctly functioning network, but if possible it would
>   be nice if the client could timeout within a relatively 
>   short time when there is no reply, as it does for DHCPv4.
> 
>   All information which is strictly required for the installation
>   (prefix, gateway and DNS) has already been gathered from
>   the RA at this point and the installation could proceed
>   without the additional DHCPv6 info (domain name, NTP servers,
>   timezone info, etc.).

The latter is only true if RDNSS is available, which cannot be taken for
granted. (Cisco gear, for instance, does not support it.) So we might
miss DNS server information. That said we could query it afterwards.

Could you please file a bug against netcfg about that?

> - If the user does not know beforehand which of the suggested
>   mirrors are available via IPv6, finding that out inside the
>   installer is currently a matter of trial and error.  As mirror
>   connectivity can change over time, hardcoding this information
>   into the installer would be no safe solution.  Perhaps it would
>   be possible to add ftp.ipv6.debian.org to the mirror list,
>   currently it is not listed in the installer's mirror choices. 
>   Cdn.debian.net, which should automatically redirect you to a
>   proper mirror near you, is listed but it is not available via
>   IPv6.  Http.debian.net might also be a option which is
>   currently not in the mirrors list; according to the
>   documentation it supports IPv6 and has worked for me.
>   If I get this correctly, http.debian.net is not an "official"
>   debian service. Would it be ok to put a note into the
>   installation guide that users on ipv6-only networks should
>   try http.debian.net or ftp.ipv6.debian.org if they have
>   no other known-working mirror near them?

I guess the note should be easy. Could you file a bug against
installation-guide?

FWIW, ftp.debian.org is supposed to work, too. But it is a single host
in .nl.

Kind regards and thanks for your help
Philipp Kern

Attachment: signature.asc
Description: Digital signature


Reply to: