🌬️ Zeph
Zeph is a reinforcement learning based algorithm for selecting prefixes to probe based on previous measurements in order to maximize the number of nodes and links discovered. Zeph can be used on top of the Iris platform.
🚀 Quickstart
Zeph has a command line interface to configure and run the algorithm.
First, install the Zeph package:
pip install dioptra-zeph
Zeph takes as input a list of /24 (IPv4) or /64 (IPv6) prefixes:
# prefixes.txt
8.8.8.0/24
2001:4860:4860::/64
To start a measurement from scratch:
zeph prefixes.txt
To start from a previous measurement:
zeph prefixes.txt UUID
Zeph relies on iris-client and pych-client for communicating with Iris and ClickHouse. See their respective documentation to know how to specify the credentials.
✨ Generate prefix lists from BGP RIBs
You can create an exhaustive list of /24 prefixes from a BGP RIB dump:
pyasn_util_download.py --latest
# Connecting to ftp://archive.routeviews.org
# Finding most recent archive in /bgpdata/2022.05/RIBS ...
# Downloading ftp://archive.routeviews.org//bgpdata/2022.05/RIBS/rib.20220524.1000.bz2
# 100%, 659KB/s
# Download complete.
zeph-bgp-convert --print-progress rib.20220524.1000.bz2 prefixes.txt
📚 Publications
@article{10.1145/3523230.3523232,
author = {Gouel, Matthieu and Vermeulen, Kevin and Mouchet, Maxime and Rohrer, Justin P. and Fourmaux, Olivier and Friedman, Timur},
title = {Zeph & Iris Map the Internet: A Resilient Reinforcement Learning Approach to Distributed IP Route Tracing},
year = {2022},
issue_date = {January 2022},
publisher = {Association for Computing Machinery},
address = {New York, NY, USA},
volume = {52},
number = {1},
issn = {0146-4833},
url = {https://doi.org/10.1145/3523230.3523232},
doi = {10.1145/3523230.3523232},
journal = {SIGCOMM Comput. Commun. Rev.},
month = {mar},
pages = {2–9},
numpages = {8},
keywords = {active internet measurements, internet topology}
}
🧑💻 Authors
Iris is developed and maintained by the Dioptra group at Sorbonne Université in Paris, France.
Metadata
Release files for dioptra-zeph 1.3.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dioptra_zeph-1.3.12.tar.gz | 11.0 kB | Without provenance | Details for dioptra_zeph-1.3.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dioptra_zeph-1.3.12-py3-none-any.whl | Python 3 | none | any | Details for dioptra_zeph-1.3.12-py3-none-any.whl |
Total release size: 26.4 kB
Release files / dioptra_zeph-1.3.12.tar.gz
| Download URL | dioptra_zeph-1.3.12.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cceb42362cb0cc6ddac462faa9600fbc9dbe7a13928c459244bc000a6535d7bf
|
|
BLAKE2b-256 checksum How to use checksums |
d943c268c1596949b658ec536a183ad93f0f4c07bc316720dd4a1c198454f6fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / dioptra_zeph-1.3.12-py3-none-any.whl
| Download URL | dioptra_zeph-1.3.12-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6be5ad48be1a2dc462f383fe64de8b2b7bde2b77945c981b4ce2af3bdfcd2f6d
|
|
BLAKE2b-256 checksum How to use checksums |
7e32a144c57225985c92dbc38fef0890776207192d3461dbd8ffb5e663de29b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for dioptra-zeph 1.3.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.