Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261
- To: Roy Marples <roy%marples.name@localhost>
- Subject: Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261 Re: NFS boot fails with ip_output.c rev 1.261
- From: Robert Elz <kre%munnari.OZ.AU@localhost>
- Date: Sat, 17 Sep 2016 19:45:43 +0700
Date: Sat, 17 Sep 2016 13:09:45 +0100
From: Roy Marples <roy%marples.name@localhost>
Message-ID: <bbe63ce45c28787de312f59859179239%mail.marples.name@localhost>
| > That isn't disabling the IFF_TENTATIVE handling, it is dosabling DAD,
| The end result should be the same.
For this purpose (if it were possible to achieve), yes, but disabling
DAD means no verification that the addr is not a duplicate, rather than
just assuming it probably isn't for the interim (and usually being right.)
Certainly if you believe that disabling DAD is acceptable (leading to
unverified addresses) sending from tentative addresses must also be
acceptable, since they're effectively the same thing.
The new patch looks like it will probably work (but I don't have
anything that can or would NFS boot, so I can't test that) but I think
it would be better to just treat tentative addresses like validated ones
(just as disabling DAD would do) - that is not test the IFF_TENTATIVE case
at all.
kre
Home |
Main Index |
Thread Index |
Old Index