tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Applying the inet6 ND state engine to inet4



On 19/08/2020 19:05, Roy Marples wrote:
On 19/08/2020 15:04, Roy Marples wrote:
$ obj.amd64/arp -an
? (10.73.1.2) at 40:8d:5c:f4:71:34 on re0 1s D
? (10.73.1.1) at 04:18:d6:f0:02:cc on re0 2s R
? (10.73.1.230) at (incomplete) on re0 6s I
? (10.73.1.71) at f8:ad:cb:18:5a:88 on re0 23h56m28s S
? (10.73.1.30) at b4:2e:99:e0:33:f4 on re0 28s R
$

Patch here: https://www.netbsd.org/~roy/netbsd-nd.diff

If anyone's actually testing this, I updated the patch to fix some timing issues and a few other nits. Aside from deciding what to do about the timing knobs (and thus man page updates) it should be good to go now.

I've yet to update the patch to my latest, but I have sysctl knobs to mirror ndp settings, but globally rather than per iface.

That brings me to an intereting question.
Do we want to adjust ndp(8) to affect the timing for ARP as well so they are the same - which has the side effect of an IPv6 router adjusting bassereachable for ARP as well? There is no equivalent in ARP/DHCP, but having it network setable could be a win? It would also mean that the settings could be per iface as well quite easily.

It would also make the output more pretty as arp(8) output isn't that pretty, more so with the ND state and timings emitted as well.

Comments welcome.

Roy


Home | Main Index | Thread Index | Old Index