On 28/03/2020 15.30, Stuart Henderson wrote:
I've started seeing a lot of these:
/bsd: arpresolve: 10.15.5.1: route contains no arp information
last message repeated 436 times
Local subnet is working, traffic going via default route is not (ping
reports "sendmsg: Invalid argument".
Network config is dhcp running on iwm0/em0 as separate interfaces (no trunk,
just using default priorities to prefer wired) and the wlan is on the same
subnet as ethernet. This previously worked just fine. ifconfig/route
tables/dmesg
are below.
While I'm bisecting, does anyone have an idea what might have introduced it?
I've a very similar setup and the same messages.
I'm using a Lenovo T480 laptop connected with both em0 and iwn0 to the
same local network, served by a single dhcp server.
I've checked the logs and some similar messages dates back from 2019/10.
The last time it happened was yesterday 2020/04/05 with kernel:
OpenBSD 6.6-current (GENERIC.MP) #106: Sun Apr 5 00:44:26 MDT 2020
When I lost access to the Internet, unplugging the Ethernet cable
restore the access through the Wifi.
If you wish, I may do some more test the next time the problem occurs.
--
2020-04-05T11:42:56.857Z lad /bsd: arp: attempt to add entry for
192.168.1.254 on iwm0 by f4:ca:e5:55:0d:2d on em0
2020-04-05T11:42:56.957Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:43:29.108Z lad last message repeated 1260 times
2020-04-05T11:44:26.958Z lad last message repeated 513 times
2020-04-05T11:44:38.879Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:44:38.908Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:44:51.558Z lad last message repeated 4 times
2020-04-05T11:44:54.889Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:44:54.909Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:45:25.109Z lad last message repeated 239 times
2020-04-05T11:45:34.559Z lad last message repeated 7 times
2020-04-05T11:45:38.899Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:45:38.909Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:45:54.909Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:45:54.959Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:46:29.109Z lad last message repeated 12 times
2020-04-05T11:46:36.009Z lad last message repeated 9 times
2020-04-05T11:46:38.920Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:46:38.920Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:46:38.959Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:46:47.660Z lad last message repeated 3 times
2020-04-05T11:46:54.930Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:46:54.960Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:47:33.110Z lad last message repeated 236 times
2020-04-05T11:47:35.360Z lad last message repeated 7 times
2020-04-05T11:47:38.940Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:47:38.940Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:47:38.960Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:47:38.960Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:47:39.057Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:47:39.060Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:47:53.060Z lad ntpd[17974]: sendto: Invalid argument
2020-04-05T11:47:53.110Z lad /bsd: arpresolve: 192.168.1.254: route
contains no arp information
2020-04-05T11:47:55.070Z lad ntpd[17974]: sendto: Invalid argument
--
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
iwm0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu
1500
lladdr a8:6d:aa:7f:a2:8d
index 1 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect (HT-MCS8 mode 11n)
status: active
ieee80211: join jogbixop chan 6 bssid fc:f5:28:ca:9c:42 77%
wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
inet 192.168.1.18 netmask 0xffffff00 broadcast 192.168.1.255
em0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
lladdr e8:6a:64:de:d1:80
index 2 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
status: active
inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255
enc0: flags=0<>
index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
index 5 priority 0 llprio 3
groups: pflog
$ netstat -rnfinet
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Prio
Iface
default 192.168.1.254 UGS 22 2883 - 8
em0
default 192.168.1.254 UGS 0 0 - 12
iwm0
224/4 127.0.0.1 URS 0 2677 32768 8
lo0
127/8 127.0.0.1 UGRS 0 0 32768 8
lo0
127.0.0.1 127.0.0.1 UHhl 2 68220 32768 1
lo0
192.168.1/24 192.168.1.4 UCn 1 207 - 4
em0
192.168.1/24 192.168.1.18 UCn 1 0 - 8
iwm0
192.168.1.4 e8:6a:64:de:d1:80 UHLl 0 306872 - 1
em0
192.168.1.18 a8:6d:aa:7f:a2:8d UHLl 0 194 - 1
iwm0
192.168.1.254 f4:ca:e5:55:0d:2d UHLch 3 2678 - 3
em0
192.168.1.254 link#1 UHLch 1 0 - 7
iwm0
192.168.1.255 192.168.1.4 UHPb 0 746 - 1
em0
192.168.1.255 192.168.1.18 UHPb 0 0 - 1
iwm0
