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.

Inheritance diagram

The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.

Implemented by

Name	Type	Description
DiffservTrafficConditioner	compound module	TODO documentation
LeakyBucket	compound module	Implements a parameterizable leaky bucket algorithm.
OmittedTrafficConditioner	compound module	Implements the given module interface and can be used as an omitted optional module that removes itself from the module hierarchy during initialization.
TC1	compound module	Traffic conditioner used in Experiments 1.1-1.6 and 5.1.
TC2	compound module	Traffic conditioner used in Experiment 3.1.
TC3	compound module	Traffic conditioner used in Experiment 3.2.
TokenBucket	compound module	Implements a parameterizable token bucket algorithm.
TrafficConditioner	compound module	TODO documentation

Used in compound modules

Name	Type	Description
EthernetInterface	compound module	Represents an Ethernet network interface.
EthernetPlcaInterface	compound module	Implements a network interface that is suitable for use in Ethernet 10BASE-T1S multidrop links. Such a multidrop link uses the Ethernet Phyisical Layer Collision Avoidance (PLCA) protocol. The protocol is defined in the IEEE 802.3cg-2019 standard. This network interface can be used in any network node module (e.g. ~StandardHost) that allows replacing its network interfaces. All network interfaces on the same multidrop link must use this module.
PppInterface	compound module	Implements a PPP network interface.
TrafficConditionerLayer	compound module	(no description)

Extends

Name	Type	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.
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.

Properties

Name	Value	Description
display	i=block/source
omittedTypename	OmittedTrafficConditioner

Source code

//
// 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.
//
moduleinterface ITrafficConditioner extends IPassivePacketSink, IActivePacketSource
{
    parameters:
        @omittedTypename(OmittedTrafficConditioner);
        @display("i=block/downarrow");
}

File: src/inet/queueing/contract/ITrafficConditioner.ned