From nobody Fri Nov 12 17:49:24 2021
X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 48FE1185FFA6
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Fri, 12 Nov 2021 17:49:26 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4HrR121fsKz4bg9;
	Fri, 12 Nov 2021 17:49:26 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.95 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1mlag0-00054r-Q6;
	Fri, 12 Nov 2021 18:49:24 +0100
Date: Fri, 12 Nov 2021 18:49:24 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: tuexen@freebsd.org
Cc: freebsd-net@freebsd.org
Subject: Re: dtrace to trace incoming connection not suceeding ?
Message-ID: <YY6pJADF9wwM2FVf@fc.opsec.eu>
References: <YY5nhomjYRnRojwa-v2@fc.opsec.eu>
 <866D4765-25EF-4C5F-AA2E-D6BE8D5EBEEB@freebsd.org>
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-net
List-Help: <mailto:freebsd-net+help@freebsd.org>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Subscribe: <mailto:freebsd-net+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-net+unsubscribe@freebsd.org>
Sender: owner-freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <866D4765-25EF-4C5F-AA2E-D6BE8D5EBEEB@freebsd.org>
X-Rspamd-Queue-Id: 4HrR121fsKz4bg9
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-Spam: Yes
X-ThisMailContainsUnwantedMimeParts: N

Hello,

> > Background: a fbsd 13.0p4 amd64 box, with a frr-7.4_4 (or 7.5.1_3)
> > fails to act on incoming ipv4 tcp 179 connections.

That box above (c5) fails to speak to a 12.2-RELEASE-p7 box (c1).

I have a second case, between a 12.2-RELEASE-p1 and this 12.2-RELEASE-p7
box (c9), same failure.

And I have a third case between a spare box (c2), running 13.0p4, which
fails to speak to both the 12.2-RELEASE-p7 and the 12.2-RELEASE-p1 box 8-(

And the funny thing is: The 13.0p4 box talks sucessfully
with a 12.1p8 box.

Below is a list of the hardware in each case:

c1	12.2p7			can't talk to c9, c5
	ix0@pci0:2:0:0: class=0x020000 card=0x061115d9 chip=0x10fb8086 rev=0x01 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82599ES 10-Gigabit SFI/SFP+ Network Connection'

c2	13.0p4, spare box	can't talk to c1, c5
	ix0@pci0:1:0:0: class=0x020000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x10fb subvendor=0x8086 subdevice=0x7a12
    vendor     = 'Intel Corporation'
    device     = '82599 10 Gigabit Dual Port Network Connection'

c5	13.0p4, where it all started (it had 12.1p8 before)
	ix0@pci0:2:0:0: class=0x020000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x10fb subvendor=0x8086 subdevice=0x000c
    vendor     = 'Intel Corporation'
    device     = '82599ES 10-Gigabit SFI/SFP+ Network Connection'

c6	12.1p8		c5 can talk to that
	ix0@pci0:1:0:0: class=0x020000 card=0x7a128086 chip=0x10fb8086 rev=0x01 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82599ES 10-Gigabit SFI/SFP+ Network Connection'

c9	12.2p1
	ix0@pci0:2:0:0: class=0x020000 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82599ES 10-Gigabit SFI/SFP+ Network Connection'

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?