ZTE-Wrapper
An API wrapper for modern ZTE routers using a more advanced authentication method. This has only been tested on an MC888B. If you have any feedback, please share!
Features
"Support" in this case means that it can be controlled via the library.
| Feature | Support |
|---|---|
| Create portforward rules | ✅ |
| Delete portforward rules | ✅ |
| List portforward rules | ✅ |
| Send SMS | ✅ |
| Read SMS | ✅ |
| List wireless devices | ✅ |
| List wired devices | ✅ |
| Get signal strength | ✅ |
| Band information | ✅ |
| Usage statistics | ✅ |
| Firewall (e.g. domain/port filtering) | ✅ |
| DHCP Settings | ✅ |
| MAC-IP bindings | ✅ |
| DDNS settings | ✅ |
| Query WiFI settings | ✅ |
| Edit WiFI settings | ❌ |
| VPN settings | ❌ |
| Network tools (e.g. traceroute/ping) | ✅ |
| "Preferred position" tools | ❌* |
*: Not planning on implementing
Features as overlayed on web panel
(based on commit a7baa3b)
Roadmap
-
Implement DDNS-settings -
Publish onto PyPI -
More reliable error handling
-
Implement rest of the features
-
Implement better documentation
-
Write tests
Notes
- When referring to "megabytes" or "bytes", they are in base 2 format (e.g. 1Gib = 1024Mib)
- Authenticating (aka. running any of the API calls) logs off other clients from the admin web panel.
- Even thought the
apnwrapper should be able to change DNS settings, I've found that it doesn't work. This might have been patched in an update?
Why?
I wanted to harvest statistics from the router to my Prometheus instance. I might actually rewrite the entire admin webpage since it's kind of horrible
1 maintainer
Metadata
1 maintainer
Release files for zte-wrapper 1.0.2
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 |
|---|---|---|---|---|
| zte_wrapper-1.0.2.tar.gz | 15.0 kB | Without provenance | Details for zte_wrapper-1.0.2.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zte_wrapper-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for zte_wrapper-1.0.2-py3-none-any.whl |
| zte_wrapper-1.0.2-2-py3-none-any.whl | Python 3 | none | any | Details for zte_wrapper-1.0.2-2-py3-none-any.whl |
Total release size: 54.6 kB
Release files / zte_wrapper-1.0.2.tar.gz
| Download URL | zte_wrapper-1.0.2.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cc3e11a9e0dcd10714a3bbeb85232fdd67a2a1bd9014d4aa54a0f51dca22b88
|
|
BLAKE2b-256 checksum How to use checksums |
56d4e903fd143d707150b2d0438e37b447fc2ed2dae4c7ce47b8ce22ee7ed0a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.0
|
Release files / zte_wrapper-1.0.2-py3-none-any.whl
| Download URL | zte_wrapper-1.0.2-py3-none-any.whl |
|---|---|
| Size | 19.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6f072ec94fae35b5f3f4913b64dea61a5d39ca58082ada60e2117f01cb975f5
|
|
BLAKE2b-256 checksum How to use checksums |
e147ab8421e5faa680837354d43fef90d953469b03bc4795e43fcfc575554799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.0
|
Release files / zte_wrapper-1.0.2-2-py3-none-any.whl
| Download URL | zte_wrapper-1.0.2-2-py3-none-any.whl |
|---|---|
| Size | 19.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2eeccc4fd4d553ea1f94e74977c6a7b2c8d4996689931c9b4214944bcbff6e6f
|
|
BLAKE2b-256 checksum How to use checksums |
15f7b76896e2c5696f98dec0e2c24942c109952350d6605465f0d3031daf4f37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.0
|
Security for zte-wrapper 1.0.2
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.
