On Sat, 21 May 2011 14:31:45 +0100, Ben Hutchings <b...@decadent.org.uk> wrote: >On Sat, 2011-05-21 at 15:01 +0200, Marc Haber wrote: >> with the increasing deployment of IPv6 I begin to see an issue >> icreasingly often: When an interface is configured for IPv6, it takes >> a few seconds before the IPv6 address actually becomes available. >> Services that are started in this time window won't listen on IPv6, >> which may be unintended behavior. Many people see this behavior as a >> bug in the distribution, which is why I am addressing this issue here >> on -devel. >> >> Unfortunately, it is non-trivial to find out whether my IPv6 >> configuration has completed or not. How many addresses will be >> assigned to us via stateless autoconfig? Are we running with privacy >> extensions? Do we have additional static configuration? >> >> The most "clean" solutions for this issue would be >> (a) Modify the services to notice when additional IP addresses come up >> and listen there if the service is configured for that IP address >> (b) Parse the configuration of each service in the init script and >> wait for the configured IP addresses to actually come up. >[...] > >(c) Set the IP_FREEBIND socket option before binding.
What does this do? And it needs changes to the software as well. Greetings Marc -- -------------------------------------- !! No courtesy copies, please !! ----- Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qnqvo-0002lu...@swivel.zugschlus.de
