From nobody Tue Nov 26 18:37:11 2024 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 4XyWX45VjZz5dq0f for ; Tue, 26 Nov 2024 18:37:24 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XyWX42vrQz57Zv; Tue, 26 Nov 2024 18:37:24 +0000 (UTC) (envelope-from damjan.jov@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vk1-xa31.google.com with SMTP id 71dfb90a1353d-515191262c1so19093e0c.0; Tue, 26 Nov 2024 10:37:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732646243; x=1733251043; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XKPtVwJ1iFSpcR6Yppkxx1CCiLnNWoNqr1lBpgvMBv0=; b=SQXcqb3nrPaaDnQf9yWYbwVwLYjhJQ+sUcW5GyWBrGgVIpLvS0gfosF4b2qCV6Qcof owrimhsmkXrpTlqxdiXh/j4TgYJrWlfY8Ti20SIlc2wZO5SWc/QnnJggkv0u0xiPRIah izROhuSAVjNTL6pnPvfOY96BglSyBAO71YFcHfDJl81NJfMjJZgsv9WRSaDHDqbcn6sv e0jiEa3b08Je7FQC+FCP/Ovy/usalpqadnPwEPj2eOgkrtXszOW406cgqujCWndnjrkl D0K+VrU4OaBikD6YtfmpWstOaMrJadMQqkDnGXPEOgfNG9eKYHTfmSO1UZueYscwDcnD sHTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732646243; x=1733251043; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XKPtVwJ1iFSpcR6Yppkxx1CCiLnNWoNqr1lBpgvMBv0=; b=rPDEmEdXZpeWZGI2LmOCmKTSxLrkeyYLLo+ftUfw80ReTgMbzubFxO2esTpdTcHO01 Nm9jWITYSH31OgXw64Sjfv5fesJm+Be5fTjGS9bAVReHxtC6MuoWYIK3mNc+GeE3c1RO sYFWA/BxCN4zyjItexl4iPG00umSf1iCs6F/vz8VatKx1YelhJArAN4kQ33hzCBmaiHL 8YfuwgfCD4/itqycZ5Csiv8gXqJWGhpzK+Ho02HOYhEgTnXQ/9+bc+2i8bqQFrNbhhQ0 tG150tYQwUUMcHtgNnRV2Lceie2E9yv1vXtTYE5qeo9C1Pftb9FrTYHI1OIxyM6snFhh loGg== X-Gm-Message-State: AOJu0YwXMdBqa2cGpqbQUjjq7OjEV+qUEzr1ZZK1+czQMl5G9c06GEMB dCh7oo4PNwCxRnbuuQWq2uW5JwVDVy9innOgxIsfypyB0whkWukvVah8UHSCZ5hAQ5v1G+/2keG aag2YJlNTu4AkmoiwVmIxmhJKHOHcyw== X-Gm-Gg: ASbGncv6Wtt2WnU0IUT0Av4h7n5ILRlRU0iBTgdFsvfHm+bkG/fCUZk1XL1JrYb71B/ tKe73h4XhQhYsQWt++d4ul1CB3XcV/n9B X-Google-Smtp-Source: AGHT+IFrSWpnOyP/qGU9PpoKws2vGx/1JbC6bLK33Wtw7bxWAEIzKNIdfEDAuauXfWqsB3jS9sllONlB32QQ5eInaTE= X-Received: by 2002:a05:6122:801a:10b0:515:43ff:6ed8 with SMTP id 71dfb90a1353d-51544bf926dmr4005471e0c.5.1732646242896; Tue, 26 Nov 2024 10:37:22 -0800 (PST) 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 References: In-Reply-To: From: Damjan Jovanovic Date: Tue, 26 Nov 2024 18:37:11 +0000 Message-ID: Subject: Re: MSG_ERRQUEUE in socket recvmsg ? To: Kurt Jaeger Cc: freebsd-net@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d451fc0627d523bd" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XyWX42vrQz57Zv X-Spamd-Bar: ---- --000000000000d451fc0627d523bd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Nov 26, 2024 at 1:37=E2=80=AFPM Kurt Jaeger wrote: > Hello, > > there's a tool called tracepath (similar to traceroute) and some > implementation in python: > > https://github.com/keiichishima/pytracepath > > It depends on recv(2) having some MSG_ERRQUEUE flag. > > Does anyone know if that is being worked on or if there's > a reason that FreeBSD does not have that flag ? > > Thanks! > > -- > pi@FreeBSD.org +49 171 3101372 Now what ? > > It looks like pytracepath not only uses that non-standard flag to enable reporting of errors for some optional purpose, but relies on the specific format of those errors, such as the embedded IP addresses, to implement its core functionality. That tool is completely locked into Linux. FreeBSD's traceroute is implemented using raw sockets instead. Regards Damjan --000000000000d451fc0627d523bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Nov 26, 2024 at 1:37=E2=80=AF= PM Kurt Jaeger <pi@freebsd.org>= wrote:
Hello,
there's a tool called tracepath (similar to traceroute) and some
implementation in python:

https://github.com/keiichishima/pytracepath

It depends on recv(2) having some MSG_ERRQUEUE flag.

Does anyone know if that is being worked on or if there's
a reason that FreeBSD does not have that flag ?

Thanks!

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


It looks like pytracepath not only use= s that non-standard flag to enable reporting of errors for some optional pu= rpose, but relies on the specific format of those errors, such as the embed= ded IP addresses, to implement its core functionality.

=
That tool is completely locked into Linux.

FreeBSD's traceroute is implemented using raw sockets instead.
<= div>
Regards
Damjan

<= /div> --000000000000d451fc0627d523bd--