Parse ifconfig output collected from local or remote server and retrieve required interface information.
Usage
Install ifconfig-parser:
pip install -U ifparser
You can access inferface information as below :
>>> import commands
>>> from ifparser import Ifcfg
>>> ifdata = Ifcfg(commands.getoutput('ifconfig -a'))
>>> ifdata.interfaces
['lo', 'docker0', 'eth0']
>>> eth0 = ifdata.get_interface('eth0')
>>> eth0.BROADCAST
True
>>> eth0.hwaddr, eth0.mtu, eth0.ip, eth0.UP
('08:00:27:1f:d8:b0', '1500', '10.0.2.15', True)
You can query for intefaces on particular parameter :
>>> ifdata.get(itype='Ethernet')
[obj-docker0, obj-eth0]
>>> ifdata.get(UP=True)
[obj-lo, obj-docker0, obj-eth0]
Get all interface parameters with get_values. Following dictionary contains all possible values:
>>> eth0 = ifdata.get_interface('eth0')
>>> eth0.get_values()
{'BROADCAST': True,
'LOOPBACK': False,
'MULTICAST': True,
'RUNNING': True,
'UP': True,
'bcast': '10.10.2.255',
'hwaddr': 'FF:FF:27:1f:d8:b0',
'interface': 'eth0',
'ip': '10.10.2.15',
'itype': 'Ethernet',
'mask': '255.255.255.0',
'mtu': '1500',
'rxbytes': '547873',
'rxpkts': '628',
'txbytes': '50826',
'txpkts': '424'}
List of parameters for interface:
BROADCAST, LOOPBACK, MULTICAST, RUNNING, UP, DYNAMIC, NOARP, PROMISC, POINTOPOINT, SIMPLEX, SMART, MASTER, SLAVE
interface - Interface name, itype - Interface Type
ip - IP, bcast - Broadcast, mask - Mask
hwaddr - MAC address, mtu - MTU
rxbytes - Received Bytes, rxpkts - Received Packets
txbytes - Sent Bytes, txpkts - Sent Packets
Metadata
Release files for ifparser 0.8.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 |
|---|---|---|---|---|
| ifparser-0.8.2.tar.gz | 6.3 kB | Without provenance | Details for ifparser-0.8.2.tar.gz |
Release files / ifparser-0.8.2.tar.gz
| Download URL | ifparser-0.8.2.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69f79f046cda556f2b316783950db916417f8b91c074653f0ba58a549d35d23b
|
|
BLAKE2b-256 checksum How to use checksums |
d48f72756b026b47014c13d32b388eabb7c182aa9d97dd8e75b8ad1925f820da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/38.5.1 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/2.7.15rc1
|
Security for ifparser 0.8.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.