traceroute - how to get it to work?

[le-mon]

Moin,
I am still baffled abput your work and enjoy docsight on my raspberry 3 as a systemd service in debian bookworm. /usr/bin/traceroute works as expected and all files are git-pulled and requiremented ;)

logs are saying:

Apr 09 12:22:35 raspi python3[22115]: 2026-04-09 10:22:35,220 [ERROR] docsis.traceroute: Traceroute helper not found at /usr/local/bin/docsight-traceroute-helper
Apr 09 12:22:42 raspi python3[22115]: 2026-04-09 10:22:42,251 [WARNING] waitress.queue: Task queue depth is 1

the only file i could find so far ist the .c file:

/home/user/docsight/tools/traceroute_helper.c

Am i doing something wrong / missing some steps or isn't this feature fully implemented yet?
The [WARNING] about waitress.queue isn't related, it just appears very often, maybe it's helpful to let you know.

[itsDNNS]

Hey! Thanks for the kind words.

The traceroute helper needs to be compiled from the C source and installed as a setuid binary -- the Docker image does this automatically but for bare-metal installs you have to do it manually:

sudo gcc -O2 -Wall -o /usr/local/bin/docsight-traceroute-helper tools/traceroute_helper.c
sudo chown root:root /usr/local/bin/docsight-traceroute-helper
sudo chmod 4755 /usr/local/bin/docsight-traceroute-helper

The setuid bit is needed because raw sockets require elevated privileges. Traceroute should work immediately after that, no restart needed.

I also just added a bare-metal section to INSTALL.md so this is documented going forward.

The waitress.queue: Task queue depth is 1 warning is harmless -- it just means a second request came in while the worker was busy. Nothing to worry about.

[le-mon]

Thanks, that's all i needed :)