On 02/04/2017 10:46 PM, jungle boogie wrote:
Ping was failing with something very similar:
ping: sendmsg: Invalid argument
ping: wrote yahoo.com 64 chars, ret=-1
Follow up to my own mystery...
I have two network interfaces on this laptop: bge0 and wpi0, both of
which are on the same physical network.
What happened is the wpi0 interface died somehow and when I
rebooted/deleted pf rules, I thought I fixed it, when it reality the
network interface just came alive again.
The same network interface died earlier today and when I attempted to
ping, I got the same response as above. I restarted network with sh
/etc/netstart and pinging was fine.
Now the off-topic (from original post) question is why did the NIC die?
I see lots and lots of this in dmesg:
arpresolve: 192.168.0.1: route contains no arp information
arpresolve: 192.168.0.1: route contains no arp information
one of these:
arp: attempt to add entry for 192.168.0.21 on bge0 by 00:0c:42:c2:5f:9e
on wpi0
Here's the interface:
wpi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:19:d2:c8:ce:01
index 1 priority 4 llprio 3
groups: wlan
media: IEEE802.11 autoselect (DS1 mode 11g)
status: active
ieee80211: nwid the-rocks chan 6 bssid 64:70:02:32:c2:48 -42dBm
wpakey <not displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp
wpagroupcipher ccmp
inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255
Thanks for the pointers.
