From owner-freebsd-net@freebsd.org Sat Oct 12 19:28:28 2019 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4967B142958 for ; Sat, 12 Oct 2019 19:28:28 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46rFGz36Nqz4Sq2 for ; Sat, 12 Oct 2019 19:28:27 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x9CJSP69096573; Sat, 12 Oct 2019 12:28:25 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x9CJSPsq096572; Sat, 12 Oct 2019 12:28:25 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201910121928.x9CJSPsq096572@gndrsh.dnsmgr.net> Subject: Re: [SOLVED] Re: FRR on FreeBSD 12 - problems with OSPFv3 In-Reply-To: To: Rudy Date: Sat, 12 Oct 2019 12:28:25 -0700 (PDT) CC: freebsd-net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46rFGz36Nqz4Sq2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [-0.64 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.61)[-0.606,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.97)[-0.972,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.14), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.04), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2019 19:28:28 -0000 > > > > On 10/11/19 4:14 PM, BulkMailForRudy wrote: > > > > Thanks for the questions, good for me to think about it some more.? > > Short response: > > > > ?I don't think it is the FRR config, but the routes received that are > > crashing it or ospf6d has some other issue. > > > > > Got it running!? I tested the theory that 'bad routes' were crashing > ospf6d.? This did it.? I have some odd,legacy,test /124 blocks in the > network (will ferret them out), but filtering the routes fixes this. > > router ospf6 > ?auto-cost reference-bandwidth 10000 > ?area 0.0.0.0 filter-list prefix IN-OSPF6 in > ?interface cxl1 area 0.0.0.0 > ?interface cxl2 area 0.0.0.0 > ?interface cxl3 area 0.0.0.0 > ! > ipv6 prefix-list IN-OSPF6 seq 3 permit 2607:f598::/32 le 64 > ipv6 prefix-list IN-OSPF6 seq 99 deny ::/0 le 128 > > > Rudy Great, Would you still please open an issue as pointed out in another email at the FRR site, this helps them track and close the underlying problem. No route received from any peer should *crash* a daemon. Including this additional data may help them to identify the problem. Regards, -- Rod Grimes rgrimes@freebsd.org