Am 21.05.2011 20:49, schrieb Marc Haber:
> On Sat, 21 May 2011 17:22:05 +0200, Michael Biebl
> wrote:
>> A similar issue (not directly IPv6 related) was discussed on fedora-devel not
>> very long ago. It was about the more "dynamic" nature of NetworkManager and
>> how
>> certain services currentl
On Sun, 22 May 2011 13:41:22 +0200, Bjørn Mork wrote:
>Marc Haber writes:
>> On Sat, 21 May 2011 15:42:51 -0700, Steve Langasek
>> wrote:
>>>With an event-based init system such as upstart, you could also set up the
>>>service not to start until the specified interface is fully configured.
>>
>>
On Sun, 22 May 2011 11:45:53 +0200, Goswin von Brederlow
wrote:
>Marc Haber writes:
>> On Sun, 22 May 2011 00:29:35 +0200, Goswin von Brederlow
>> wrote:
>>>(c) Modify ifupdown to notice when additional IP addresses come up (or
>>>go away) and run the ifup.d (ifdown.d) scripts for it.
>>
>> One
Marc Haber writes:
> On Sat, 21 May 2011 15:42:51 -0700, Steve Langasek
> wrote:
>>With an event-based init system such as upstart, you could also set up the
>>service not to start until the specified interface is fully configured.
>
> Issue (1): We don't have event-based init system yet
> Issue
Marc Haber writes:
> On Sun, 22 May 2011 00:29:35 +0200, Goswin von Brederlow
> wrote:
>>(c) Modify ifupdown to notice when additional IP addresses come up (or
>>go away) and run the ifup.d (ifdown.d) scripts for it.
>
> One would need an ifupdownd for this. I don't think that's realistic.
>
> G
On Sun, 22 May 2011 02:11:00 +0100, Ian Jackson
wrote:
>Marc Haber writes ("How to solve race condition between IPv6 ifup and start of
>services?"):
>> Is there a widely accepted method to do things any easier? It is
>> clearly not acceptable to have to manua
On Sat, 21 May 2011 15:42:51 -0700, Steve Langasek
wrote:
>With an event-based init system such as upstart, you could also set up the
>service not to start until the specified interface is fully configured.
Issue (1): We don't have event-based init system yet
Issue (2): When is an IPv6 interface
On Sun, 22 May 2011 00:29:35 +0200, Goswin von Brederlow
wrote:
>(c) Modify ifupdown to notice when additional IP addresses come up (or
>go away) and run the ifup.d (ifdown.d) scripts for it.
One would need an ifupdownd for this. I don't think that's realistic.
Greetings
Marc
--
---
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 IPv
Marc Haber writes ("How to solve race condition between IPv6 ifup and start of
services?"):
> 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 r
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 thi
Marc Haber writes:
> Hi,
>
> 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 I
On Sat, 2011-05-21 at 20:29 +0200, Marc Haber wrote:
> On Sat, 21 May 2011 14:31:45 +0100, Ben Hutchings
> 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
On Sat, 21 May 2011 17:22:05 +0200, Michael Biebl
wrote:
>A similar issue (not directly IPv6 related) was discussed on fedora-devel not
>very long ago. It was about the more "dynamic" nature of NetworkManager and how
>certain services currently don't cope with the network not being up and fully
>c
On Sat, 21 May 2011 14:31:45 +0100, Ben Hutchings
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 actuall
Am 21.05.2011 15:01, schrieb Marc Haber:
>
> 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
On Sat, 2011-05-21 at 15:01 +0200, Marc Haber wrote:
> Hi,
>
> 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 t
Hi,
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 beh
18 matches
Mail list logo
