Date: Tue, 26 Nov 2024 22:07:25 +0100 From: Kurt Jaeger <pi@freebsd.org> To: Damjan Jovanovic <damjan.jov@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: MSG_ERRQUEUE in socket recvmsg ? Message-ID: <Z0Y4jWwr1ePhoC2B@fc.opsec.eu> In-Reply-To: <CAJm2B-=eOeOdEq6suiGVvKdOh9BEBa7%2BF5qJkwMq7XFmuv1zhQ@mail.gmail.com> References: <Z0XNvsrPP_boxDWz@fc.opsec.eu> <CAJm2B-=eOeOdEq6suiGVvKdOh9BEBa7%2BF5qJkwMq7XFmuv1zhQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > 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. > 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. Yes, I'm aware. But maybe someone is working on some MSG_ERRQUEUE ? > FreeBSD's traceroute is implemented using raw sockets instead. Yes, this forces it to have a root s-bit. I've found a python traceroute code: https://github.com/mihika09/Python-Traceroute and will have a look at that. -- pi@FreeBSD.org +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Z0Y4jWwr1ePhoC2B>