From owner-freebsd-net@FreeBSD.ORG Mon May 19 01:36:11 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B82D98AD for ; Mon, 19 May 2014 01:36:11 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EEE32F2F for ; Mon, 19 May 2014 01:36:11 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s4J1a7xQ057096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 18 May 2014 18:36:09 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <53796003.9030306@freebsd.org> Date: Mon, 19 May 2014 09:36:03 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "Ronald F. Guilmette" , "freebsd-net@freebsd.org" Subject: Re: arp strangeness? References: <1737.1400452612@server1.tristatelogic.com> In-Reply-To: <1737.1400452612@server1.tristatelogic.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 01:36:11 -0000 On 5/19/14, 6:36 AM, Ronald F. Guilmette wrote: > In message <53783271.6090409@freebsd.org>, > Julian Elischer wrote: > >> On 5/18/14, 7:32 AM, Michael Sierchio wrote: >>> On Sat, May 17, 2014 at 4:30 PM, Ronald F. Guilmette >>> 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. it is possible that the router replies with "ONE" of its addreses.. not necessarily the one closest to you. I've seen that before. > (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.) > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >