From owner-freebsd-current@freebsd.org Fri Oct 30 16:03:51 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 327F7A20E44 for ; Fri, 30 Oct 2015 16:03:51 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 176621C18 for ; Fri, 30 Oct 2015 16:03:51 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 1501EA20E42; Fri, 30 Oct 2015 16:03:51 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEF3EA20E41 for ; Fri, 30 Oct 2015 16:03:50 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward11h.cmail.yandex.net (forward11h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::9c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75AEC1C16; Fri, 30 Oct 2015 16:03:50 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web12h.yandex.ru (web12h.yandex.ru [IPv6:2a02:6b8:0:f05::22]) by forward11h.cmail.yandex.net (Yandex) with ESMTP id 578AA2148A; Fri, 30 Oct 2015 19:03:37 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web12h.yandex.ru (Yandex) with ESMTP id A146AC2039A; Fri, 30 Oct 2015 19:03:36 +0300 (MSK) Received: by web12h.yandex.ru with HTTP; Fri, 30 Oct 2015 19:03:36 +0300 From: Alexander V. Chernikov Envelope-From: melifaro@ipfw.ru To: Bryan Drewery , "current@FreeBSD.org" In-Reply-To: <5632961B.2040604@FreeBSD.org> References: <5632485F.5080203@FreeBSD.org> <56324C80.8000408@vangyzen.net> <56324D69.4080507@FreeBSD.org> <5632961B.2040604@FreeBSD.org> Subject: Re: r288951: ifconfig -alias, arp not removed MIME-Version: 1.0 Message-Id: <1500541446221016@web12h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 30 Oct 2015 19:03:36 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2015 16:03:51 -0000 30.10.2015, 00:57, "Bryan Drewery" : > On 10/29/2015 9:46 AM, Bryan Drewery wrote: >> šOn 10/29/15 9:42 AM, Eric van Gyzen wrote: >>> šOn 10/29/2015 11:25, Bryan Drewery wrote: >>>> š# ifconfig >>>> šigb0: flags=8843 metric 0 mtu 1500 >>>> >>>> šoptions=403bb >>>> šššššššššether c8:0a:a9:04:39:78 >>>> šššššššššinet 10.10.0.7 netmask 0xffff0000 broadcast 10.10.255.255 >>>> šššššššššinet 10.10.7.2 netmask 0xffff0000 broadcast 10.10.255.255 >>>> šššššššššinet 10.10.0.9 netmask 0xffff0000 broadcast 10.10.255.255 >>>> šššššššššnd6 options=23 >>>> šššššššššmedia: Ethernet autoselect (1000baseT ) >>>> šššššššššstatus: active >>>> >>>> š# ifconfig igb0 inet 10.10.0.9 -alias >>>> š# arp -an|grep 10.10.0.9 >>>> š? (10.10.0.9) at c8:0a:a9:04:39:78 on igb0 permanent [ethernet] >>>> š# arp -d 10.10.0.9 >>>> šarp: writing to routing socket: Operation not permitted >>>> >>>> šI swear this is not normal. I'm on an older build as well, r288951. Well, there were changes on arpscrub procedures in r287789. (There was one bug fixed in r289501, but I think it is not relevant). Could you consider trying more recent HEAD and check if this is still reproducible? I was not able to reproduce that behavior. >>> >>> šThat definitely looks abnormal. See what "route get" says. I think >>> šthat's the error you get when there is a route for that address. >> >> š# netstat -rn|grep 10.10.0.9 >> š# route get 10.10.0.9 >> ššššroute to: lapbox >> šdestination: 10.10.0.0 >> ššššššššmask: 255.255.0.0 >> šššššššššfib: 0 >> šššinterface: igb0 >> šššššššflags: >> ššrecvpipe sendpipe ssthresh rtt,msec mtu weight expire >> šššššššš0 0 0 0 1500 1 0 >> š# route get 5.5.5.5 >> ššššroute to: 5.5.5.5 >> šdestination: default >> ššššššššmask: default >> šššššgateway: router.asus.com >> šššššššššfib: 0 >> šššinterface: igb0 >> šššššššflags: >> ššrecvpipe sendpipe ssthresh rtt,msec mtu weight expire >> šššššššš0 0 0 0 1500 1 0 >> >> šFor more context, this current system had 10.10.0.9 added to it. I >> šstarted up a VM which also started using 10.10.0.9 and managed to "win" >> šon the local network for owning it. (I don't know arp and this stuff >> šwell). I then came to this system to remove the alias and the arp entry >> što allow me to connect from it and have gotten into this situation. > > Just saw this in dmesg, which is what I described: > > arp: 08:00:27:12:c1:a5 is using my IP address 10.10.0.9 on igb0! > arp: 08:00:27:12:c1:a5 is using my IP address 10.10.0.9 on igb0! > arp: 08:00:27:12:c1:a5 attempts to modify permanent entry for 10.10.0.9 > on igb0 > arp: 08:00:27:12:c1:a5 attempts to modify permanent entry for 10.10.0.9 > on igb0 > arp: 08:00:27:12:c1:a5 attempts to modify permanent entry for 10.10.0.9 > on igb0 > arp: 08:00:27:12:c1:a5 attempts to modify permanent entry for 10.10.0.9 > on igb0 > > -- > Regards, > Bryan Drewery