Use case
You have a server in LAN. You want some client to connect to it but the client does not know the address. So you run beacon on the server side and the client will find it.
Prerequisites
python 2.6+
netifaces (optional)
Download
packages at http://pypi.python.org/pypi/netbeacon
repository at https://github.com/dsiroky/netbeacon
Metadata
Release files for netbeacon 1.1
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 |
|---|---|---|---|---|
| netbeacon-1.1.tar.gz | 2.9 kB | Without provenance | Details for netbeacon-1.1.tar.gz |
Release files / netbeacon-1.1.tar.gz
| Download URL | netbeacon-1.1.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1381dd63800ef950f6c267f8500ddb00e4d033a62226fb43830e5a715d18bcc8
|
|
BLAKE2b-256 checksum How to use checksums |
d45d6194eab2879ca8907d6c6bbda776678d50723118981db41020b8efbe68e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for netbeacon 1.1
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.