Module Interfaces¶

Name	Type	Description
IActivePacketSink	module interface	Interface for active packet sink modules. An active packet sink, also called a collector, has one input that must be connected to a passive packet source module. The active packet sink is expected to pull packets from the connected passive packet source over time.
IActivePacketSource	module interface	Interface for active packet source modules. An active packet source, also called a producer, has one output that must be connected to a passive packet sink module. The active packet source is expected to push packets into the connected passive packet sink over time.
IAggregatorPolicy	module interface	Interface for aggregator policy modules that determine when packets can be aggregated. Implementations of this interface decide whether a new packet can be combined with the current set of aggregated packets based on various criteria such as size limits, timing constraints, or protocol-specific requirements. The policy module is consulted by the aggregator to make aggregation decisions.
IAnalogDigitalConverter	module interface	Converts analog signal representations to digital sample representations in wireless communication systems. This module transforms continuous analog models into discrete sample models with a configurable sample rate, handling both header and data portions of the signal separately. It serves as a bridge between the analog domain and the digital processing domain, enabling detailed bit-level simulation of receiver signal processing chains.
IAntenna	module interface	The antenna model describes the physical device (a part of the radio) which converts electric signals into radio waves, and vice versa.
IApp	module interface	Generic application interface.
IArp	module interface	Interface for Address Resolution Protocol (ARP) implementations. Provides address resolution services for mapping network layer addresses (e.g., IPv4) to link layer addresses (e.g., MAC). Modules implementing this interface maintain a cache of address mappings and handle resolution requests from the network layer.
IBackgroundNoise	module interface	The background noise model describes the thermal noise, the cosmic background noise, and other random fluctuations of the electromagnetic field that affect the quality of the communication channel.
IBgp	module interface	Interface for BGP routing module.
ICcEnergyConsumer	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current-based interfaces.
ICcEnergyGenerator	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current-based interfaces.
ICcEnergyManagement	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current based interfaces.
ICcEnergySink	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current-based interfaces.
ICcEnergySource	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current-based interfaces.
ICcEnergyStorage	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with current [A], and storage capacity with charge [C] and output voltage [V]. The Cc is an abbreviation that is used for charge and current based interfaces.
IChannelVisualizer	module interface	(no description)
IClock	module interface	Interface for clock models.
IClockServo	module interface	Interface for clock servo models.
ICloudDelayer	module interface	Delay module interface for `InternetCloud`.
ICollisionController	module interface	Interface for collision controllers. A collision controller is used with EDCA, and it detects and reports internal collisions among Edcaf instances.
ICommunicationCache	module interface	Module interface for communication caches that store and manage radio and transmission data in wireless networks. Provides efficient caching of intermediate computation results related to signal propagation, reception, and interference to improve simulation performance by avoiding redundant calculations.
IContention	module interface	Interface for modules that implement contention-based channel access. For each frame, Contention listens on the channel for a DIFS (AIFS) period then for a random backoff period before transmitting the frame, and defers when a busy channel is sensed. After receiving a corrupted frame, EIFS is used instead of the original DIFS (AIFS).
ICtsPolicy	module interface	Interface for CTS policies.
IDataLinkVisualizer	module interface	Interface allows configuring different IDataLinkVisualizer submodules from INI files. Such a visualizer displays the active data link layer links in a network.
IDcf	module interface	Interface for modules that implement the DCF (Distributed Coordination Function) for IEEE 802.11.
IDecoder	module interface	Interface for decoders in wireless communications. Decoders convert bit-level signal representations back into packet-level representations, performing the reverse of the encoding process. This typically involves operations such as descrambling, forward error correction (FEC) decoding, and deinterleaving. Implementations of this interface handle different wireless standards and encoding schemes, providing the final step in recovering transmitted data from received bits.
IDemodulator	module interface	Module interface for demodulators in wireless communication systems. Demodulators convert symbols back to bits in the receiver’s signal processing chain. They take a reception symbol model as input and produce a reception bit model as output by applying the inverse of the modulation scheme (such as BPSK, QPSK, QAM16, etc.) to each symbol to recover the original bit sequence.
IDigitalAnalogConverter	module interface	Interface for digital-to-analog converter modules that transform discrete-time signal samples into continuous-time analog signals. This module represents the final stage in the digital signal processing chain before transmission over the wireless medium. It takes a sample model containing discrete signal samples as input and produces an analog model representing the continuous waveform as output. The conversion process typically involves interpolation between sample points to create a smooth analog signal.
IDs	module interface	Interface for modules that implement the frame Distribution Service for IEEE 802.11. The job of the Distribution Service is deciding what to do with correctly received frames. They may be discarded (e.g. on address mismatch), sent up to higher layers, and/or transmitted back on the wireless LAN after switching addresses.
IEigrp	module interface	Interface for routing protocol modules connected to IP Layer.
IEncoder	module interface	Module interface for bit-level encoders used in wireless communication systems. Encoders transform packet models into bit models by applying techniques such as scrambling, forward error correction (FEC), and interleaving. These processes add redundancy and structure to the data stream to improve transmission reliability over noisy channels.
IEnergyConsumer	module interface	The energy consumer models describe the energy consumption process of devices over time. For example, a radio consumes energy when it transmits or receives signals, or a CPU consumes energy when the network layer processes packets, or a display consumes energy when it’s turned on, etc.
IEnergyGenerator	module interface	The energy generator models describe the energy generation process of devices over time. A solar panel, for example, produces energy based on time, the panel’s position on the globe, its orientation towards the sun, and the actual weather conditions.
IEnergyManagement	module interface	The energy management models monitor an energy storage, estimate its state, and control the consumers and generators to protect the energy storage from operating outside its safe operating area.
IEnergySink	module interface	The energy sink models absorbs energy from multiple energy generators.
IEnergySource	module interface	The energy source models provide energy for multiple energy consumers.
IEnergyStorage	module interface	The energy storage models describe devices that absorb energy produced by generators, and provide energy for consumers. For example, an electrochemical battery in a mobile phone provides energy for its display, its CPU, and its wireless communication device. It can also absorb energy produced by a solar panel installed on its display, or by a portable charger plugged into a wall socket.
IEnergyStorageVisualizer	module interface	Interface allows configuring different IEnergyStorageVisualizer submodules from INI files. Such a visualizer displays energy storages.
IEpEnergyConsumer	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The Ep is an abbreviation that is used for energy and power based interfaces.
IEpEnergyGenerator	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The Ep is an abbreviation that is used for energy and power-based interfaces.
IEpEnergyManagement	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The Ep is an abbreviation that is used for energy and power based interfaces.
IEpEnergySink	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The abbreviation Ep is used for energy and power based interfaces.
IEpEnergySource	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The Ep is an abbreviation that is used for energy and power-based interfaces.
IEpEnergyStorage	module interface	This interface extends the corresponding energy model interface. It requires implementations to describe energy consumption and energy generation with power [W] and storage capacity with energy [J]. The Ep is an abbreviation that is used for energy and power-based interfaces.
IErrorModel	module interface	The error model describes how the signal to noise ratio affects the amount of errors at the receiver.
IEtherMac	module interface	Interface for Ethernet MAC implementations. All Ethernet MAC implementations should implement this (i.e. declared as: `EthernetCsmaMacPhy` like `IEtherMac`). The existing implementations are these: EthernetCsmaMacPhy and EthernetMacPhy.
IEthernetInterface	module interface	Interface for Ethernet network interfaces.
IEthernetLayer	module interface	Module interface for Ethernet protocol layer implementations. Implementations typically handle the encapsulation of higher layer packets into Ethernet frames for transmission and the decapsulation of received Ethernet frames for delivery to higher layers.
IEthernetMacLayer	module interface	Module interface for Ethernet MAC (Media Access Control) layer implementations. Defines an interface for various MAC layer variants in the modular Ethernet architecture. Provides connection points to upper layers (e.g., LLC) and lower layers (e.g., PHY) through standardized gates.
IEthernetNetworkNode	module interface	Interface for all network nodes that have Ethernet connectivity. Extends the base INetworkNode interface by adding Ethernet-specific gates and parameters.
IEthernetPhyLayer	module interface	(no description)
IExternalInterface	module interface	Interface for external network interfaces.
IFailureProtectionConfigurationVisualizer	module interface	Interface allows configuring different IFailureProtectionConfigurationVisualizer submodules from INI files. Such a visualizer displays the TSN configuration in a network.
IFecCoder	module interface	Interface for Forward Error Correction (FEC) coders. Defines a common interface for modules that implement channel coding techniques to detect and correct transmission errors. FEC coders are used in bit-level physical layer simulations in wireless simulations to accurately model error correction capabilities of wireless protocols.
IFragmentationPolicy	module interface	Interface for fragmentation policies.
IFragmenterPolicy	module interface	Module interface for fragmentation policies that determine how packets are split into fragments. Implementations calculate the appropriate fragment sizes based on various constraints such as maximum transmission unit.
IGateScheduleConfigurator	module interface	Interface for gate scheduling configurator modules. A gate scheduling configurator is responsible for configuring all PeriodicGate modules of all traffic categories in all network interfaces in the network.
IGateScheduleVisualizer	module interface	Interface allows configuring different IGateScheduleVisualizer submodules from INI files. Such a visualizer displays gates.
IGeographicCoordinateSystem	module interface	Interface for geographic coordinate systems. A geographic coordinate system maps scene coordinates to geographic coordinates, and vice versa.
IGeoHorizonVisualizer	module interface	Interface allows configuring different IGeoHorizonVisualizer submodules from INI files. Such a visualizer draws the satellite visibility footprint (the area on the Earth from which a node is seen above an elevation mask) on a 2D map.
IGeoMapVisualizer	module interface	Interface allows configuring different IGeoMapVisualizer submodules from INI files. Such a visualizer projects geographically located network nodes onto a 2D world map.
IGeoSkyViewVisualizer	module interface	Interface allows configuring different IGeoSkyViewVisualizer submodules from INI files. Such a visualizer draws an azimuth/elevation sky view polar plot next to each observer node, showing where the target nodes (e.g. satellites) are in the observer’s sky.
IGptp	module interface	Interface for gPTP module.
IGround	module interface	Module interface for ground models that define the terrain in physical environment simulations. Provides methods to compute ground projections and normals for any position, which is necessary for accurate modeling of signal propagation and mobility over terrain. Implementations range from simple flat surfaces to terrain models based on real-world elevation data.
IHcf	module interface	Interface for modules that implement the HCF (Hybrid Coordination Function) for IEEE 802.11.
IHook	module interface	Generic module that can be inserted at some points in the model
IIeee80211Agent	module interface	Module interface for IEEE 802.11 agent modules that provide the decision logic for selecting access points and managing wireless connections in wireless stations. Agents initiate channel scanning, association, authentication, and handovers by sending commands to the management module.
IIeee80211Llc	module interface	Module interface for IEEE 802.11 Logical Link Control (LLC) implementations. LLC defines the interface between the MAC layer and network layer in IEEE 802.11 networks. Implementations handle encapsulation and decapsulation of packets, using either EtherType Protocol Discrimination (EPD) or Link Protocol Discrimination (LPD) methods.
IIeee80211Mac	module interface	Module interface for the IEEE 802.11 MAC module type.
IIeee80211Mgmt	module interface	Module interface for all IEEE 802.11 management module types. It exists to specify what gates a management module should have in order to be usable within Ieee80211Interface.
IIeee80211Visualizer	module interface	Interface allows configuring different IIeee80211Visualizer submodules from INI files. Such a visualizer displays IEEE 802.11 network interface associations.
IIeee8021aeTagEpdHeaderChecker	module interface	(no description)
IIeee8021aeTagEpdHeaderInserter	module interface	Module interface for IEEE 802.1AE (MACsec) tag header inserters. Implementations process outgoing frames to add IEEE 802.1AE security tags with EtherType Protocol Discrimination (EPD), encapsulate packet data in encrypted chunks, and add security parameters including Secure Channel Identifier (SCI) and packet number (PN) as defined in the IEEE 802.1AE standard for MAC security.
IIeee8021dQosClassifier	module interface	Interface for 802.1d QoS classifiers. For each packet, the classifier computes an 802.1d User Priority (UP) value and sets it in the Iee802Ctrl control info before sending out the packet on the “out” gate.
IIeee8021qLayer	module interface	(no description)
IIeee8021qTagEpdHeaderChecker	module interface	(no description)
IIeee8021qTagEpdHeaderInserter	module interface	(no description)
IIeee8021qTagTpidHeaderChecker	module interface	(no description)
IIeee8021qTagTpidHeaderInserter	module interface	(no description)
IIeee8021rLayer	module interface	(no description)
IIeee8021rTagEpdHeaderChecker	module interface	(no description)
IIeee8021rTagEpdHeaderInserter	module interface	(no description)
IIeee8022Llc	module interface	(no description)
IIeee8022LlcChecker	module interface	(no description)
IIeee8022LlcInserter	module interface	(no description)
IIeee8022LlcLayer	module interface	(no description)
IIeee8022SnapChecker	module interface	(no description)
IIeee8022SnapInserter	module interface	(no description)
IIgmp	module interface	Module interface for IGMP modules.
IInfoVisualizer	module interface	Interface allows configuring different IInfoVisualizer submodules from INI files. Such a visualizer displays various information from submodules of network nodes.
IIngressClassifier	module interface	Module interface for ingress packet classifiers for MPLS.
IIntegratedVisualizer	module interface	Interface allows configuring different IIntegratedVisualizer submodules from INI files. Integrated visualizers are compound modules, they do not display anything on their own. Instead, they combine multiple visualizers, most often simple modules, to provide a convenient way to add complex visualizations to a simulation.
IInterfaceTableVisualizer	module interface	Interface allows configuring different IInterfaceTableVisualizer submodules from INI files. Such a visualizer displays various information for network interfaces present in the interface tables of a network.
IInterleaver	module interface	Module interface for bit-level interleavers used in wireless communication systems. Interleavers rearrange the order of bits in a data stream to spread the effects of burst errors, improving the performance of forward error correcting codes. Implementations provide methods for interleaving and deinterleaving bit sequences according to specific patterns.
IIpv4	module interface	Module interface for IPv4 protocol implementations. Defines gates and parameters for modules that provide IPv4 protocol functionality. The IPv4 protocol provides datagram routing, fragmentation, and addressing between network interfaces and transport layer protocols.
IIpv4NodeConfigurator	module interface	(no description)
IIpv6NodeConfigurator	module interface	(no description)
IIpvxTrafficGenerator	module interface	Module interface for modules that generate traffic directly over IP. Compatible with both Ipv4 and Ipv6.
IL2NodeConfigurator	module interface	Interface for all layer 2 node configurators.
IL3NetworkConfigurator	module interface	Interface for all layer 3 network configurators.
ILayeredErrorModel	module interface	(no description)
ILinkBreakVisualizer	module interface	Interface allows configuring different ILinkBreakVisualizer submodules from INI files. Such a visualizer displays the data link breaks in a network.
ILinkLayer	module interface	Interface for both upper and lower interfaces of different link layers.
ILinkLayerLower	module interface	Interface for the lower interface of different link layers.
ILinkLayerUpper	module interface	Interface for the upper interface of different link layers.
ILoopbackInterface	module interface	Interface for loopback network interfaces.
IMacForwardingTable	module interface	Interface for MAC address tables, used by MAC relay units in Ethenet switches.
IMacProtocol	module interface	This interface provides an abstraction for different MAC protocols.
IMacRelayUnit	module interface	Module interface for modules providing Ethernet switch functionality. These modules handle the mapping between ports and MAC addresses, and forward frames to appropriate ports.
IManetRouting	module interface	Defines a module interface for Mobile Ad-hoc Network (MANET) routing protocols. MANET routing protocols are designed for wireless networks where nodes can move and the topology changes dynamically. Implementations include GPSR, DSDV, and DYMO protocols.
IMeasurementLayer	module interface	Module interface for measurement layers that collect performance metrics on packet flows. Implementations monitor and record various statistics about packets passing through the network stack.
IMeasurer	module interface	Interface for all standalone measurement modules. These measurement modules can be used in various places such as network interfaces, network nodes, subnetworks or even the whole network. They most often collect statistical results by subscribing to signals of other modules and by doing their calculation internally.
IMediumAnalogModel	module interface	The analog model describes how the analog representation of the transmissions is turned into the analog representation of the receptions.
IMediumLimitCache	module interface	Module interface for caching various limits and constraints of the radio medium to optimize performance. Maintains information about maximum transmission power, minimum interference and reception power, maximum antenna gain, communication and interference ranges, and other parameters.
IMediumVisualizer	module interface	Interface allows configuring different IMediumVisualizer submodules from INI files. Such a visualizer displays transmitting nodes, receiving nodes, and propagating radio signals on a medium.
IMld	module interface	Module interface for MLD modules.
IMobility	module interface	The module interface for mobility models.
IMobilityVisualizer	module interface	Interface allows configuring different IMobilityVisualizer submodules from INI files. Such a visualizer updates the position (among others) of visual representations according to the corresponding mobility model.
IModulator	module interface	Interface for digital modulator modules that convert sequences of bits into sequences of symbols. Modulators implement various modulation schemes (such as BPSK, QPSK, QAM, etc.) that determine how digital information is encoded into changes in the carrier signal’s amplitude, frequency, or phase. The modulator takes a bit model as input and produces a symbol model as output, forming an essential component in the physical layer signal processing chain for wireless communication systems.
IMpduAggregationPolicy	module interface	Interface for MPDU aggregation policies.
IMrp	module interface	Interface for modules that implement the Media Redundancy Protocol (MRP), specified in IEC 62439-2.
IMsduAggregationPolicy	module interface	Interface for MSDU aggregation policies.
INeighborCache	module interface	The neighbor cache model computes the affected set of receivers on the medium for a given transmission.
INetworkConfigurator	module interface	Interface for all network-wide configurator modules.
INetworkConnectionVisualizer	module interface	Interface allows configuring different INetworkConnectionVisualizer submodules from INI files. Such a visualizer creates the visual representations of network connections.
INetworkInterface	module interface	Interface for network interfaces.
INetworkLayer	module interface	(no description)
INetworkLayerLower	module interface	(no description)
INetworkLayerUpper	module interface	Interface for different network layers.
INetworkNode	module interface	INetworkNode defines the common interface for all network node types in INET. It serves as the base interface that all node modules must implement to be recognized and treated as network nodes within the simulation.
INetworkNodeVisualizer	module interface	Interface allows configuring different INetworkNodeVisualizer submodules from INI files. Such a visualizer creates the visual representations of network nodes.
INetworkProtocol	module interface	This interface provides an abstraction for different network protocols.
INetworkRouteVisualizer	module interface	Interface allows configuring different INetworkRouteVisualizer submodules from INI files. Such a visualizer displays active network routes in a network.
IObjectCache	module interface	An object cache is a data structure that is used by the physical environment to store physical objects.
IObstacleLoss	module interface	The obstacle loss model describes the reduction of power as the signal passes through physical objects.
IOriginatorAckPolicy	module interface	Interface for originator ACK policies. This policy tells whether an ACK is expected for a transmitted frame, and also determines the ACK timeout.
IOriginatorBlockAckAgreementPolicy	module interface	Interface for originator Block ACK agreement policies.
IOriginatorQosAckPolicy	module interface	Interface for the originator QoS ACK policies.
IOscillator	module interface	Interface for oscillator models.
IOspf	module interface	Interface for routing protocol modules connected to IP Layer.
IPacketAggregator	module interface	Interface for packet aggregator modules that combine multiple packets into a single aggregated packet. Aggregation is a technique to improve network efficiency by reducing the overhead associated with transmitting many small packets. Implementations of this interface collect packets and combine them according to specific aggregation policies and protocols.
IPacketBuffer	module interface	Interface for packet buffer modules. A packet buffer is often used by packet queues to store packets in a limited shared resource. Packets can be added to and removed from a packet buffer. When the buffer becomes overloaded, one or more packets are dropped according to the configured dropping strategy. For each dropped packet, the packet owner is notified in order to update its internal state.
IPacketClassifier	module interface	Interface for packet classifier modules. A packet classifier is a passive module which has one passive input and multiple active outputs. Packets pushed into the passive input are passed through to one of the active outputs without any delay or reordering.
IPacketDeaggregator	module interface	Interface for packet deaggregator modules that split an aggregated packet back into its original component packets. Deaggregation is the reverse process of aggregation, extracting the individual packets that were previously combined to reduce header overhead. Implementations of this interface receive an aggregated packet and forward each extracted subpacket separately.
IPacketDefragmenter	module interface	Module interface for packet defragmenters that reassemble original packets from fragments. Implementations collect fragments and reconstruct the complete packet once all fragments have been received.
IPacketDelayer	module interface	Interface for packet delayers.
IPacketDropVisualizer	module interface	Interface allows configuring different IPacketDropVisualizer submodules from INI files. Such a visualizer displays the packet drops in a network.
IPacketFilter	module interface	Interface for packet filter modules. A packet filter connects one input to one output. It can operate in both active and passive mode. Packets can be pushed into its input or packets can be pulled from its output. Processed packets are either dropped, if they don’t match the filter criteria, or they are passed through without any delay or reordering. Packets are not modified in any way.
IPacketFlow	module interface	Interface for packet flows. A packet flow connects one input to one output. It can operate in both active and passive mode. Packets can be pushed into its input or packets can be pulled from its output. Packets are never dropped but the contents and/or attached meta information may be altered.
IPacketFlowVisualizer	module interface	(no description)
IPacketFragmenter	module interface	Module interface for packet fragmenters that split packets into smaller fragments. Implementations divide packets that exceed maximum transmission size into multiple fragments that can be reassembled at the destination.
IPacketGate	module interface	Interface for a packet gate. A packet gate connects one input to one output. It can operate in both active and passive mode. Packets can be pushed into its input or packets can be pulled from its output.
IPacketLifeTimer	module interface	(no description)
IPacketMarker	module interface	Interface for packet marker modules. A packet marker connects one input to one output. It can operate in both active and passive mode. Packets can be pushed into its input or packets can be pulled from its output. When processing a packet, a marker attaches some information (such as a label) to the packet based on the data and metadata it contains. The packets are processed individually.
IPacketMeter	module interface	Interface for packet meter modules. A packet meter connects one input to one output. It can operate in both active and passive mode. Packets can be pushed into its input or packets can be pulled from its output. When processing packets, a meter attaches some information (such as the packet rate) to the packets based on the data and metadata they contain. The packets are processed as part of a stream.
IPacketPolicing	module interface	Interface for packet policing modules. A packet policing connects one input to one output. It operates in passive mode on its input and in active mode on its output. These modules usually meter various traffic properties and drop packets, but they never modify, delay or reorder packets.
IPacketPuller	module interface	Interface for packet pullers. A packet puller connects one input to one output. Packets can be pulled from its output and it pulls packets from its input.
IPacketPusher	module interface	Interface for packet pushers. A packet pusher connects one input to one output. Packets can be pushed into its input and it pushes packets into its output.
IPacketQueue	module interface	Interface for packet queue modules. A packet queue is a passive module which has one passive input and one passive output. Packets pushed into the passive input are either stored or dropped. Packets pulled from the passive output are provided from the stored packets.
IPacketReceiver	module interface	(no description)
IPacketScheduler	module interface	Interface for packet scheduler modules. A packet scheduler is a passive module which has multiple active inputs and one passive output. Packets pulled from the passive output are provided by one of the inputs without any delay and reordering.
IPacketServer	module interface	Interface for packet server modules. A packet server is an active module which has one active input and one active output. Packets are pulled from the connected input module and pushed into the connected output module with an optional delay but without reordering.
IPacketShaper	module interface	Interface for packet shaper modules. A packet shaper connects one input to one output. It operates in passive mode both on its input and its output. These modules may delay and reorder packets but they never modify or drop packets.
IPacketSink	module interface	Interface for packet sink modules which are both passive and active simultaneously.
IPacketSource	module interface	Interface for packet source modules which are both active and passive simultaneously.
IPacketTransmitter	module interface	(no description)
IPassivePacketSink	module interface	Interface for passive packet sink modules. A passive packet sink, also called a consumer, has one input that must be connected to an active packet source module. The connected active packet source is expected to push packets into the passive packet sink over time.
IPassivePacketSource	module interface	Interface for passive packet source modules. A passive packet source, also called a provider, has one output that must be connected to an active packet sink module. The connected active packet sink is expected to pull packets from the passive packet source over time.
IPathLoss	module interface	The path loss model describes the reduction of power as the signal propagates through space.
IPhysicalEnvironment	module interface	Module interface for physical environment models that contain physical objects affecting signal propagation. Implementations define a space with objects of various shapes, positions, orientations, and materials. These objects impact wireless signal propagation through absorption, reflection, refraction, and diffraction.
IPhysicalEnvironmentVisualizer	module interface	Interface allows configuring different IPhysicalEnvironmentVisualizer submodules from INI files. Such a visualizer displays the physical objects present in the physical environment.
IPhysicalLayer	module interface	Interface for the interface of different physical layers.
IPhysicalLinkVisualizer	module interface	Interface allows configuring different IPhysicalLinkVisualizer submodules from INI files. Such a visualizer displays the active physical layer links in a network.
IPim	module interface	Defines a module interface for Protocol Independent Multicast (PIM) routing protocol implementations. PIM is used for multicast routing across IP networks, building distribution trees for multicast data.
IPppInterface	module interface	Interface for PPP network interfaces.
IProcessingDelayLayer	module interface	Module interface for processing delay layers that model packet processing time in network devices. Implementations simulate the delay introduced by packet processing operations in both ingress and egress directions.
IPropagation	module interface	The propagation model describes how a radio signal propagates through space over time.
IProtocolHeaderChecker	module interface	Module interface for protocol header checker components. Modules that implement this interface verify protocol-specific headers in packets and typically remove them after successful validation. These components act as packet filters that can drop invalid packets based on header information, ensuring protocol compliance and integrity. They are commonly used in protocol stacks to process incoming packets before passing them to higher layers.
IProtocolHeaderInserter	module interface	Module interface for protocol header inserter components. Modules that implement this interface add protocol-specific headers to packets before they are transmitted. These components process packets by prepending or appending headers that contain protocol information such as addressing, control data, or authentication codes.
IProtocolLayer	module interface	Interface for all protocol layer modules that connect to a higher and to a lower protocol layer, both of which are optional.
IPulseFilter	module interface	Module interface for pulse filters in wireless communication systems. Pulse filters convert between the sample domain and the symbol domain in the receiver’s signal processing chain. They take a reception sample model as input and produce a reception symbol model as output by extracting symbols from the received signal samples based on the configured samples per symbol ratio.
IPulseShaper	module interface	Interface for pulse shaping components in wireless communications. Transforms symbol-domain signals into sample-domain signals by applying pulse shaping to digital symbols, creating a continuous-time waveform. Used in detailed physical layer simulations.
IQueueVisualizer	module interface	Interface allows configuring different IQueueVisualizer submodules from INI files. Such a visualizer displays queues.
IQuic	module interface	QUIC protocol interface.
IRadio	module interface	Module interface for radio modules. Radio modules deal with the transmission of frames over a wireless medium (the radio medium).
IRadioMedium	module interface	The medium model describes the shared physical medium where communication takes place. It keeps track of radios, noise sources, ongoing transmissions, background noise, and other ongoing noises. The medium computes when, where, and how transmissions and noises arrive at receivers.
IRadioVisualizer	module interface	Interface allows configuring different IRadioVisualizer submodules from INI files. Such a visualizer displays radios.
IRateControl	module interface	Interface for auto rate control modules.
IRateSelection	module interface	Interface for frame rate selection modules. Rate selection decides what bit rate (or MCS) should be used for frames of various types, such as control frames, management frames, and data frames.
IReceiver	module interface	The receiver model describes the physical process that converts electric signals into packets.
IReceiverAnalogModel	module interface	The receiver analog model describes the connecting piece between the technology-dependent part of the receivers and the different analog medium models.
IRecipientAckPolicy	module interface	Interface for recipient ACK policies. This policy chooses between no ACK, normal ACK, and Block ACK for received frames.
IRecipientBlockAckAgreementPolicy	module interface	Interface for recipient Block ACK agreement policies.
IRecipientQosAckPolicy	module interface	Interface for recipient QoS ACK policies.
IRoutingTable	module interface	Interface for different routing tables.
IRoutingTableVisualizer	module interface	Interface allows configuring different IRoutingTableVisualizer submodules from INI files. Such a visualizer displays routes present in the routing tables of a network.
IRTPPayloadReceiver	module interface	Interface for RTP Payload Receivers.
IRtpPayloadSender	module interface	Interface for RTP Payload Senders.
IRtsPolicy	module interface	Interface for RTS policies.
IRx	module interface	Interface for Rx processes. The Rx process checks received frames for errors, manages the NAV, and notifies other processes about the channel state (free or busy). The channel is free only if it is free according to both the physical (CCA) and the virtual (NAV-based) carrier sense algorithms. Correctly received frames are sent up to upper layers, corrupted frames are discarded.
ISceneVisualizer	module interface	Interface allows configuring different ISceneVisualizer submodules from INI files. Such a visualizer displays the scene, the coordinate axes, sets up the initial viewpoint, etc.
IScrambler	module interface	Module interface for scramblers that convert input bit sequences into seemingly random output sequences of the same length. Scramblers are used in wireless communication systems to randomize data, avoid long sequences of identical bits, improve clock recovery, and reduce transmission errors. Implementations typically use generator polynomials and seed values to define the scrambling algorithm. This interface supports both scrambling and descrambling operations needed in encoders and decoders of various wireless protocols.
ISctp	module interface	Interface for SCTP protocol.
ISocketLayer	module interface	(no description)
ISpanningTree	module interface	Module interface for Spanning Tree protocols
IStatisticVisualizer	module interface	Interface allows configuring different IStatisticVisualizer submodules from INI files. Such a visualizer displays a statistic for multiple network nodes.
IStreamRedundancyConfigurationVisualizer	module interface	Interface allows configuring different IStreamRedundancyConfigurationVisualizer submodules from INI files. Such a visualizer displays the `StreamRedundancy` configuration in a network.
ITcp	module interface	Interface for TCP protocol implementations. All TCP implementations should implement this (i.e. declared as: TCP like ITcp) The existing implementations are these: Tcp, TcpLwip, (and ~TcpNsc in the inet-gpl project).
ITokenGenerator	module interface	Interface for token generators.
ITracingObstacleLossVisualizer	module interface	Interface allows configuring different ITracingObstacleLossVisualizer submodules from INI files. Such a visualizer displays obstacle loss during wireless signal propagation.
ITrafficConditioner	module interface	Interface for traffic conditioner modules. A traffic conditioner connects one input to one output. It operates in passive mode on its input and in active mode on its output. Packets can be pushed into its input and packets can be pulled from its output. A traffic conditioner can drop, delay, and reorder packets, but it doesn’t modify packets in any way.
ITrafficConditionerLayer	module interface	Defines a module interface for traffic conditioner layer implementations. Traffic conditioner layers provide mechanisms for controlling packet flow through the network stack. They can shape, police, and condition traffic by applying various policies for dropping, delaying, or reordering packets in both ingress and egress directions.
ITrafficgen	module interface	(no description)
ITrafficgenHandler	module interface	(no description)
ITransmitter	module interface	The transmitter model models the physical process which converts packets into electrical signals.
ITransmitterAnalogModel	module interface	The transmitter analog model describes the process which produces the signal analog domain representation.
ITransportConnectionVisualizer	module interface	Interface allows configuring different ITransportConnectionVisualizer submodules from INI files. Such a visualizer displays the active transport connections in a network.
ITransportRouteVisualizer	module interface	Interface allows configuring different ITransportRouteVisualizer submodules from INI files. Such a visualizer displays active transport routes in a network.
ITunnelInterface	module interface	Interface for tunnel network interfaces.
ITx	module interface	Interface for processes that unconditionally transmit a frame after waiting for a specified inter-frame space (usually SIFS). Such processes can be used to transmit frames where no contention is needed, e.g. ACK, CTS, or the second and further frames of a TXOP.
IUdp	module interface	UDP protocol interface.
IVirtualInterface	module interface	Interface for virtual network interfaces.
IVisualizer	module interface	Base interface for all visualizer module interfaces in the INET Framework. Defines common parameters for specifying visualization target and subject modules. Visualizers provide graphical representation of various aspects of network simulation, such as links, traffic flows, routing paths, and network state information.
IWiredInterface	module interface	Interface for wired network interfaces.
IWirelessInterface	module interface	Interface for wireless network interfaces.