From nobody Fri Sep 20 22:11:20 2024 X-Original-To: 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 4X9RS11mWsz5XQrg for ; Fri, 20 Sep 2024 22:11:29 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9RRz0w8Hz52Py for ; Fri, 20 Sep 2024 22:11:26 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=enki-multimedia.eu header.s=protonmail3 header.b=GgvgYOgV; dmarc=pass (policy=none) header.from=enki-multimedia.eu; spf=pass (mx1.freebsd.org: domain of benoitc@enki-multimedia.eu designates 185.70.43.23 as permitted sender) smtp.mailfrom=benoitc@enki-multimedia.eu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enki-multimedia.eu; s=protonmail3; t=1726870284; x=1727129484; bh=XekGdvnikQosAmGmSsRUpkKEloWGOmK54EcWtlmBPtg=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=GgvgYOgVm16zaXaoLnbbQhwXm8TZhzNQVsrBPQobiYXlZTbhzYxzArxfE3PKaKQ1I V/Mfu30shDEHzlNn/7bzRHftw4ks68w59Khoo0le6oojyqlOKwPoMA0RbtVvFKC/Qx yeBPzutKTSyqxPoXEp9VlirdEGbu6iEijMt6yDjO+hycDVPEkTBv5WYE+wqsHyF29w uG/0hbHwSnMu33E6dBNcU0aj3TaaFD1sgiNq6q8OzbTOrfiLiV6vO/Q/LgeVZkrWlc gZEsjum3poOITLmJq74CxrZ6TxoHBoStcCnsamLIV0BMHNUgMTezG3lROjGodN9PT1 T6Q/XKsRpAQsQ== Date: Fri, 20 Sep 2024 22:11:20 +0000 To: net@FreeBSD.org From: "benoitc@enki-multimedia.eu" Subject: Re: issue with ICMP with PF and nat and latest 14.1 Message-ID: <973C6711-9760-4978-AA2A-0219BA81C5B9@enki-multimedia.eu> In-Reply-To: <87v7ysiqge.wl-herbert@gojira.at> References: <764EE8F1-BE88-4714-AD3F-9D93028FFEC4@icloud.com> <87v7ysiqge.wl-herbert@gojira.at> Feedback-ID: 9066678:user:proton X-Pm-Message-ID: fbded9f8b493b99b45cdeb13768efed114ba3cf4 List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_DN_EQ_ADDR(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[enki-multimedia.eu,none]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; R_DKIM_ALLOW(-0.20)[enki-multimedia.eu:s=protonmail3]; RWL_MAILSPIKE_VERYGOOD(-0.20)[185.70.43.23:from]; MIME_GOOD(-0.10)[text/plain]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[net@FreeBSD.org]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; DKIM_TRACE(0.00)[enki-multimedia.eu:+] X-Rspamd-Queue-Id: 4X9RRz0w8Hz52Py X-Spamd-Bar: --- as a quick update, latest patched version of RELENG 14.1 is fixing the issu= e. Thanks for all the work :) Beno=C3=AEt > Le 19 sept. 2024 =C3=A0 00:01, benoitc@enki-multimedia.eu a =C3=A9crit : >=20 > I am running releng/14.1 . But this tickets looks very similar to the beh= aviour I'm seeing. Thanks for the link! >=20 >> Le 18 sept. 2024 =C3=A0 23:48, Herbert J. Skuhra a = =C3=A9crit : >>=20 >> On Wed, 18 Sep 2024 23:34:16 +0200, Benoit Chesneau wrote: >>>=20 >>> Hi, >>>=20 >>> It seems that since the latest update of PF in FreeBSD 14.1 mtr >>> doesn't provide a correct trace using the default. It works with the >>> ``--udp` and `-T` options so it doesn't seem to be an issue with the >>> next hop. Also mtr works perfectly on the firewall machine. Issue >>> only happen on the nated machines on the lan behind it. No issue >>> with ipv6. >>>=20 >>> I tried to change the config or pass everything but I still >>> reproduce the issue. Any idea to troubleshoot/fix it is welcome :) >>=20 >> Latest 14.1? Do you run stable/14 or releng/14.1? Maybe: >> >>=20 >> -- >> Herbert >>=20 >=20