From nobody Fri Nov 12 13:09:26 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 DA833183E40E
	for <freebsd-net@mlmmj.nyi.freebsd.org>; Fri, 12 Nov 2021 13:14:38 +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 4HrJvy5wBtz4v2n
	for <freebsd-net@freebsd.org>; Fri, 12 Nov 2021 13:14:38 +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 1mlWO5-0004n2-Rw
	for freebsd-net@freebsd.org;
	Fri, 12 Nov 2021 14:14:37 +0100
Resent-From: Kurt Jaeger <pi@freebsd.org>
Resent-Date: Fri, 12 Nov 2021 14:14:37 +0100
Resent-Message-ID: <YY5ovYTlDC/IVLnI@fc.opsec.eu>
Resent-To: freebsd-net@freebsd.org
Date: Fri, 12 Nov 2021 14:09:26 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: freebsd-net@freebsd.org
Subject: dtrace to trace incoming connection not suceeding ?
Message-ID: <YY5nhomjYRnRojwa-v2@fc.opsec.eu>
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
X-Rspamd-Queue-Id: 4HrJvy5wBtz4v2n
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [0.00 / 15.00];
	 local_wl_from(0.00)[freebsd.org];
	 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-ThisMailContainsUnwantedMimeParts: N

Hello,

I'm trying to investigate tcp-179 connection issues with the
local frr setup. See below for more background.

The question is: What can I do to find the cause of the failing
connection ? Is there a way to trace the incoming packet to see
if it ever ends up at bgpd process ?

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.

The bgpd daemon of frr listens on port 179:

frr      bgpd       96061 20 tcp6   *:179                 *:*
frr      bgpd       96061 21 tcp4   *:179                 *:*

Incoming packets can be seen with tcpdump on the dest host:

# tcpdump -i vlan500 -n -s 1500 port 179 and host <source-host>
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan500, link-type EN10MB (Ethernet), capture size 1500 bytes
13:53:13.795162 IP <source>.12274 > <dest>.179: Flags [S], seq 62227917, win 65535, options [mss 1460,nop,wscale 9,sackOK,TS val 2870882787 ecr 0], length 0

But: No connection is established 8-(

The basic ipfw firewall is active, but

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