Anyone else notice this?
em1 is direct connection to modem.
cox assigned gateway 68.231.1.1
dpc3010 ip 192.168.100.1
arping -I em1 68.231.1.1
ARPING 68.231.1.1
60 bytes from 00:14:f1:e5:d1:31 (68.231.1.1): index=0 time=7.969 msec
60 bytes from 00:14:f1:e5:d1:31 (68.231.1.1): index=1 time=37.487 msec
60 bytes from 00:14:f1:e5:d1:31 (68.231.1.1): index=2 time=8.632 msec
arping -I em1 192.168.100.1
ARPING 192.168.100.1
60 bytes from 00:09:5b:ed:da:02 (192.168.100.1): index=0 time=411.078 usec
60 bytes from 00:14:f1:e5:d1:31 (192.168.100.1): index=1 time=9.679 msec
60 bytes from 00:09:5b:ed:da:02 (192.168.100.1): index=2 time=326.388 usec
60 bytes from 00:14:f1:e5:d1:31 (192.168.100.1): index=3 time=13.201 msec
60 bytes from 00:09:5b:ed:da:02 (192.168.100.1): index=4 time=295.788 usec
60 bytes from 00:14:f1:e5:d1:31 (192.168.100.1): index=5 time=9.479 msec
Hrm.. I try arping for other IANA 'non-routeable' space on that interface and get a reply from same mac.
arping -I em1 192.168.1.1
ARPING 192.168.1.1
60 bytes from 00:14:f1:e5:d1:31 (192.168.1.1): index=0 time=16.563 msec
60 bytes from 00:14:f1:e5:d1:31 (192.168.1.1): index=1 time=8.302 msec
# arping -I em1 192.168.3.1
ARPING 192.168.3.1
60 bytes from 00:14:f1:e5:d1:31 (192.168.3.1): index=0 time=9.479 msec
↧