Looking for contributors to TunnelScope: Python MTU diagnostics with good first issues
I'm building TunnelScope , an MIT-licensed Python CLI for evidence-based MTU and packet-size experiments on Linux. It runs bounded UDP probes with a cooperating receiver, keeps sender and receiver observations in JSON, and can generate a self-contained HTML report. v0.4.1 is available on PyPI . TunnelScope is still an alpha tool: a timeout is inconclusive, and the tool does not automatically…
I am developing TunnelScope, an open-source Python command-line interface designed for evidence-based Maximum Transmission Unit (MTU) and packet-size experiments on Linux. This tool establishes controlled UDP probes with a designated receiver, records the observations from both sender and receiver in JSON format, and is capable of producing a comprehensive HTML report.
As of version 0.4.1, TunnelScope is currently in its alpha phase. While it can generate inconclusive timeouts, it does not automatically determine the exact path MTU or definitively pinpoint the root cause. Additionally, the probe protocol is unauthenticated, necessitating the execution of experiments within a controlled laboratory setting rather than public networks.
For those interested in contributing, there are several beginner-friendly tasks. The first one involves integrating Python 3.10 into the Continuous Integration (CI) checks, which can be accomplished with a minor modification to the GitHub Actions configuration. Another task is to update the README quick start documentation to include receiver correlation information, thus enabling new users to understand which packets reached the receiver.
Additionally, a documentation task is available to guide users through a Windows PowerShell loopback quick start, which would facilitate basic local testing. IPv6 routed path, VPN, and Kubernetes validation are also deemed valuable, provided a suitable laboratory environment is available.
Sanitized results and documentation feedback are appreciated; however, it is important not to share any credentials or private packet captures. To get started, I recommend reviewing the README and contribution guide. Should any task pique your interest, please leave a comment on the corresponding issue prior to opening a pull request. I am more than willing to address any inquiries and review your contributions.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.