On Sat, May 21, 2011 at 03:42:51PM -0700, Steve Langasek wrote: > On Sat, May 21, 2011 at 03:01:39PM +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.
> Apache, for one, seems to fail at this currently; I have an apache instance
> running on my laptop which I want to bind to ipv6, but of course since it's
> a roaming laptop, there isn't always an ipv6 address available at startup;
> apache thinks this means it should open ipv4-only sockets, requiring a
> restart once I'm on an ipv6 network. :/
Can't you listen on :: ? It is always available if IPv6 is loaded.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
signature.asc
Description: Digital signature
