Re: [PATCH] Don't allow Managed DHCPv6 to short-circuit SLAAC
- From: Tore Anderson <tore fud no>
- To: Dan Williams <dcbw redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: [PATCH] Don't allow Managed DHCPv6 to short-circuit SLAAC
- Date: Sat, 27 Aug 2011 13:13:13 +0200
* Dan Williams
> On Thu, 2011-08-11 at 00:10 +0200, Tore Anderson wrote:
>> NetworkManager currently operates on the assumption that Managed
>> (Stateful) DHCPv6 preempts SLAAC. This is not the case; Managed DHCPv6
>> and SLAAC are completely orthogonal. My consumer-grade xDSL CPE (a ZyXEL
>> P-2812HNU-F3) does both at the same time by default, which is a
>> necessity to trigger the following bug:
>
> Given the discussion from this week about SLAAC vs. the A=1 flag, is
> this patch independent of that or should we wait for additional changes
> in behavior?
Well, the bug I'm trying to fix; when both A=1 and M=1, you get a
seemingly successful activation followed by an instant failure, over and
over and over again; is very real and needs to be fixed. Stock NM takes
forever to connect to my home network because of it, see
<https://bugzilla.redhat.com/show_bug.cgi?id=720188> for a syslog.
The patch fixes the A=1, M=1 case. However it inadvertently breaks the
A=0, M=1 case, so it should *not* be applied. A new and better patch
should be developed, which may involve a more thorough revision of how
NM reacts to various types of RAs. I'll elaborate more on this in an
answer to your other message.
Best regards,
--
Tore Anderson
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]