IGMP
This repository stores the implementation of IGMPv2 router-side state machines. This can be used to detect multicast interest of directly connected hosts.
The goal of this repository/module is to facilitate maintainability of this IGMP implementation since its code is used by other Python projects/modules:
This implementation was performed during my Master thesis and has since then been updated to fix issues, add new features and in the future to include the implementation of IGMPv3 as well.
Documents detailing the initial work of IGMPv2 implementation
- Python implementation of IGMPv2, PIM-DM and HPIM-DM
- Test to Python implementation of IGMPv2, PIM-DM, and HPIM-DM
Requirements
- Linux machine
- Python3 (we have written all code to be compatible with at least Python v3.2)
- pip (to install all dependencies)
Installation
pip3 install igmp
How to use it?
# import module
from igmp import InterfaceIGMP
intf = InterfaceIGMP(interface_name="eth0")
intf.enable() # start receiving igmp packets
# get information from a given multicast group
multicast_group_obj = intf.interface_state.get_group_state(group_ip="224.10.11.12")
interest = multicast_group_obj.has_members() # boolean that informs if there is
# multicast interest in this group
group_state = multicast_group_obj.state.print_state() # get string identifying
# the state in which this
# group is at
# get notified of interest changes on this group
class MulticastGroupNotifier:
def notify_membership(self, has_members):
print(has_members)
notifier = MulticastGroupNotifier()
multicast_group_obj.add_multicast_routing_entry(notifier)
# when there is a change of multicast interest (for example group 224.10.11.12
# gets interested receivers), the object associated to this object is notified
# through "notify_membership" method with has_members=True
# if you no longer want to monitor the interest of 224.10.11.12, remove the
# notifier from the group
multicast_group_obj.remove_multicast_routing_entry(notifier)
intf.remove() # stop receiving igmp packets
Metadata
Release files for igmp 1.0.4
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 | |
|---|---|---|---|---|
| igmp-1.0.4.tar.gz | 16.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| igmp-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.4 kB
Release files / igmp-1.0.4.tar.gz
| Download URL | igmp-1.0.4.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4497f4ee19c8e9d4ca46fb919e72e83ed4ddf193ff47ed8e842ca2afe1a537c
|
|
BLAKE2b-256 checksum How to use checksums |
16c547ace7e4cbd8736692a6a4bd79a3851ea3aac9ea55021e3e894ad19da023
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / igmp-1.0.4-py3-none-any.whl
| Download URL | igmp-1.0.4-py3-none-any.whl |
|---|---|
| Size | 25.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84a9d0cb7831a12ced6b6a82fccac248dfb7ab7c016ad3279165d144fabb4dfa
|
|
BLAKE2b-256 checksum How to use checksums |
f561e6f748d8b9eaf2c006078530b1c6e49cec2794bdc2e346f468f0c72586d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for igmp 1.0.4
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.