On 2020/03/30 10:29, Martin Pieuchot wrote:
> On 29/03/20(Sun) 17:17, Stuart Henderson wrote:
> > [...]
> > I guess I'll just move it to a wifi network on a different vlan for now.
>
> Well I wouldn't be surprise if the issue is exposed by the use of two
> cloning routes. One way to move forward would be to add the name of the
> interface in the error message.
>
The arpresolve "route contains no arp information" is on em0.
The only entry relating to the gateway (10.15.5.1) showing in
arp -an after boot is
10.15.5.1 (incomplete) iwm0 Expired
(no entry for the gateway on em0).
Oddities:
- if I connect to a WPA-PSK network then iwm0 comes up quickly in
the "starting network" stage of /etc/rc and I have the problem. But
if I switch to a WPA-Enterprise network which doesn't connect until
wpa_supplicant starts ("starting package daemons" stage) then I don't
see the problem.
- but it's not just timing related though: I can add "!ping -c1 1.1.1.1"
or "!sleep 60" to hostname.em0 and still see the problem.
