From owner-freebsd-net@freebsd.org Thu Dec 14 06:56:27 2017 Return-Path: Delivered-To: freebsd-net@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 775C9E98D7E for ; Thu, 14 Dec 2017 06:56:27 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EABA77381 for ; Thu, 14 Dec 2017 06:56:26 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id vBE6uHgN033424 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Dec 2017 07:56:18 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-rwg@pdx.rh.CN85.dnsmgr.net Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id vBE6uDH4074411; Thu, 14 Dec 2017 13:56:13 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Changes to route(8) or routing between r325235 and r326782? To: "Rodney W. Grimes" References: <201712122021.vBCKL219088220@pdx.rh.CN85.dnsmgr.net> Cc: sthaug@nethelp.no, freebsd-net@freebsd.org, crest@rlwinm.de From: Eugene Grosbein X-Enigmail-Draft-Status: N1110 Message-ID: <5A32208D.3070500@grosbein.net> Date: Thu, 14 Dec 2017 13:56:13 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <201712122021.vBCKL219088220@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Level: ** X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 06:56:27 -0000 On 13.12.2017 03:21, Rodney W. Grimes wrote: > Flap your intgerfaces and see what happens when quagga and the kernel fight > over who gets to install the local MTU route via lo of the ip address for > the interface you flapped. I do not see any problem here. After service quagga restart: # egrep 'zebra|ospfd' /var/log/messages Dec 14 13:48:43 ptic zebra[96288]: Zebra 1.2.1 starting: vty@2601 ... Dec 14 13:48:46 ptic ospfd[96297]: AdjChg: Nbr 192.168.7.1 on gif0:192.168.100.234: Loading -> Full (LoadingDone) Dec 14 13:48:46 ptic ospfd[96297]: AdjChg: Nbr 192.168.7.1 on gif1:192.168.100.134: Loading -> Full (LoadingDone) # ifconfig gif1 down # ifconfig gif1 up This adds to /var/log/messages: Dec 14 13:49:01 ptic ospfd[96297]: AdjChg: Nbr 192.168.7.1 on gif1:192.168.100.134: Full -> Deleted (KillNbr) Dec 14 13:49:01 ptic zebra[96288]: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument Dec 14 13:49:01 ptic zebra[96288]: kernel_rtm_ipv4: 192.168.100.132/30: rtm_write() unexpectedly returned -4 for command RTM_DELETE Dec 14 13:49:04 ptic zebra[96288]: if_ioctl(SIOCGIFMEDIA) failed: Invalid argument Dec 14 13:49:04 ptic ospfd[96297]: OSPF MPLS-TE: Abort update TE parameters: no Link Parameters for interface Dec 14 13:49:06 ptic ospfd[96297]: AdjChg: Nbr 192.168.7.1 on gif1:192.168.100.134: Exchange -> Full (ExchangeDone) There is no fight. Why don't you describe *your* setup in a PR so we could handle it right way? Perhaps, we could add another sysctl to disable route pinning if it really unavoidable for such setups.