On 2016/09/20 23:31, Roy Marples wrote:
Thanks both for testing as I don't have any NFS mounts.
I've just comitted a very slightly modified version of the patch to
improve comments and add increament IPv6 dropped packet stats.
ip_output.c rev 1.263 works just fine for me.
Thank you very much fo
On 20/09/2016 12:58, Rin Okuyama wrote:
> On 2016/09/17 21:09, Roy Marples wrote:
>> When I first proposed it offlist, we thought the current
>> implementation was the correct thing.
>> Here is a patch to just do as you suggest.
>> http://www.netbsd.org/~roy/ip_output_tentative.patch
>>
>> Can the
Sorry for the late reply.
On 2016/09/17 21:09, Roy Marples wrote:
When I first proposed it offlist, we thought the current implementation was the
correct thing.
Here is a patch to just do as you suggest.
http://www.netbsd.org/~roy/ip_output_tentative.patch
Can the OP test it and see if NFS boo
On Fri, 16 Sep 2016 21:43:22 +0900, Rin Okuyama
wrote:
> NFS boot fails with ip_output.c rev 1.261 with my ERLITE (evbmips64-eb):
>
> root on cnmac0
> nfs_boot: trying BOOTP
> cnmac0: link state DOWN (was UNKNOWN)
> cnmac0: link state UP (was DOWN)
> nfs_bo
On Sat, Sep 17, 2016 at 07:45:43PM +0700, Robert Elz wrote:
> 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 DA
Date:Sat, 17 Sep 2016 13:09:45 +0100
From:Roy Marples
Message-ID:
| > 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
On 2016-09-17 03:31, Robert Elz wrote:
Date:Fri, 16 Sep 2016 23:37:40 +0100
From:Roy Marples
Message-ID: <03a78e8605c842d9d032ee3ed3a59...@mail.marples.name>
| > The IN_IFF_TENTATIVE handling just breaks lots of old code.
|
| You can disable it by setting the appr
Date:Fri, 16 Sep 2016 23:37:40 +0100
From:Roy Marples
Message-ID: <03a78e8605c842d9d032ee3ed3a59...@mail.marples.name>
| > The IN_IFF_TENTATIVE handling just breaks lots of old code.
|
| You can disable it by setting the appropriate sysctl to zero.
|
| $ s
r...@marples.name (Roy Marples) writes:
>On 2016-09-16 23:10, mlel...@serpens.de wrote:
>> r...@marples.name (Roy Marples) writes:
>>
>>> Sounds like NFS boot needs to wait for IN_IFF_TENTATIVE to clear from
>>> the address.
>>
>> The IN_IFF_TENTATIVE handling just breaks lots of old code.
>You
On 2016-09-16 23:10, mlel...@serpens.de wrote:
r...@marples.name (Roy Marples) writes:
Sounds like NFS boot needs to wait for IN_IFF_TENTATIVE to clear from
the address.
The IN_IFF_TENTATIVE handling just breaks lots of old code.
You can disable it by setting the appropriate sysctl to zero.
r...@marples.name (Roy Marples) writes:
>Sounds like NFS boot needs to wait for IN_IFF_TENTATIVE to clear from
>the address.
The IN_IFF_TENTATIVE handling just breaks lots of old code.
--
--
Michael van Elst
Internet: mlel...@serpens.de
rokuy...@rk.phys.keio.ac.jp (Rin Okuyama) writes:
> nfs_boot: sosend: 49
> nfs_boot: sosend: 49
> nfs_boot: sosend: 49
> nfs_boot: mountd error=49
The change in ip_output.c prevents the use of a recently configured
interface because now you have to wait for duplicate address detection
to
On 16/09/2016 13:43, Rin Okuyama wrote:
> NFS boot fails with ip_output.c rev 1.261 with my ERLITE (evbmips64-eb):
>
> root on cnmac0
> nfs_boot: trying BOOTP
> cnmac0: link state DOWN (was UNKNOWN)
> cnmac0: link state UP (was DOWN)
> nfs_boot: BOOTP next-s
NFS boot fails with ip_output.c rev 1.261 with my ERLITE (evbmips64-eb):
root on cnmac0
nfs_boot: trying BOOTP
cnmac0: link state DOWN (was UNKNOWN)
cnmac0: link state UP (was DOWN)
nfs_boot: BOOTP next-server: 192.168.10.128
nfs_boot: my_name=erlite
nfs_boot: my_addr
14 matches
Mail list logo