arp strangeness?

[Ronald F. Guilmette]

In message <53783271.6090409 at freebsd.org>, 
Julian Elischer <julian at freebsd.org> wrote:

>On 5/18/14, 7:32 AM, Michael Sierchio wrote:
>> On Sat, May 17, 2014 at 4:30 PM, Ronald F. Guilmette <rfg at tristatelogic.com>
>> wrote:
>>
>>> May 16 23:05:33 segfault kernel: arp: 69.62.255.254 moved from
>> 00:1e:13:22:eb:51 to 00:00:0e:07:ac:00 on rl0
>>> May 16 23:05:33 segfault kernel: arp: 69.62.255.254 moved from
>> 00:00:0e:07:ac:00 to 00:1e:13:22:eb:51 on rl0
>>> May 16 23:25:29 segfault kernel: arp: 69.62.255.254 moved from
>> 00:1e:13:22:eb:51 to 00:00:0e:07:ac:00 on rl0
>>> May 16 23:25:29 segfault kernel: arp: 69.62.255.254 moved from
>> 00:00:0e:07:ac:00 to 00:1e:13:22:eb:51 on rl0
>>
>> Yeah, the router address may be a synthetic address shared by multiple
>> physical interfaces, or
>> it may be fictional and handled via multiple interfaces/routers/etc. in
>> your ISPs fabric running some HA
>> routing (via OSPF for example).
>
>but check with your ISP that your information is current.
>It may be that you should be using another address and this one is 
>just working by accident.

Mostly because I am having ongoing connectivity issues, I did in fact
have a phone conversion, at last, with some actually knowledgable
person(s) at my ISP (Surewest aka Consolidated Communications), and
among the many questions I asked, I did also ask if the old (ancient?)
gateway address I had been using was still the current and proper one,
and sure enough, no, the current proper one is now the .1 address within
the /24 I happen to be located in.  So I've changed that now.  (I do
thank you for the suggestion, but I had already planned to ask them
if I was using the correct gateway address.)

Oddly, even though I now have the defaultrouter address in my /etc/rc.conf
file set to the .1 address, _now_ my traceroutes are showing the .2 address
in this same /24 as the first hop.  Oh well, I'm not going to worry about it.
I have bigger fish to fry.

(Specifically, my ISP now informs me that there are definite problems
with either my ADSL2+ router, or my line, or both, and I will be working
with them to correct those issues.)