inet: Don't mark cloned route as RTF_REJECT on RTM_MISS
authorRoy Marples <roy@marples.name>
Mon, 9 Sep 2019 16:20:29 +0000 (17:20 +0100)
committerRoy Marples <roy@marples.name>
Mon, 9 Sep 2019 16:20:29 +0000 (17:20 +0100)
commit25966042bdf034a8d395abae7b7d357f35c90cea
tree0b4f6249d5fa60e011b166d1a0780dee016c71dc
parent83751b8f5f204c52058a11caed4b2d0e7023b41f
inet: Don't mark cloned route as RTF_REJECT on RTM_MISS

With the current behaviour, the cloned route is marked as
RTF_REJECT which means subsequent use is delayed until either an
ARP reply comes in or the ARP entry times out and resolution
can then begin again.

Instead, no longer mark the route for RTF_REJECT and allow more
ARP requests to go out if something really wants to use it.
This mirror the current behaviour for inet6.
sys/netinet/if_ether.c