Implements the IPv4 protocol. The protocol header is represented by the Ipv4Header message class.

Interfacing with higher layer protocols

To send a packet over IPv4 from a higher layer protocol, the module should fill in an L3AddressReq object, attach it to the packet with the Packets's addTag() method, then send the packet to the Ipv4 module.

When Ipv4 sends up a packet to a higher layer protocol, it will also attach an L3AddressInd to the packet, with the source and destination IPv4 addresses of the IPv4 datagram in which the packet arrived.

Ipv4 can serve several higher-layer protocols. The higher layer protocols should call registerProtocol with their gate towards the Ipv4 module, for fill up the protocol-to-gateindex map. When delivering packets to them, the output gate is determined from the Protocol in the IPv4 header.

Routing and interfacing with lower layers

The routing table is stored in the module Ipv4RoutingTable. When a datagram needs to be routed, Ipv4 queries Ipv4RoutingTable for the output interface (or "port") and next hop address of the packet. This is done by directly calling C++ methods (such as findBestMatchingRoute(destAddress)) of Ipv4RoutingTable. No message exchange with Ipv4RoutingTable takes place.

A routed datagram will be sent to the queueOut, which is expected to be connected to INetworkInterface modules.

Routing protocol implementations (e.g. OSPF and ISIS) can also query and manipulate the route table by calling Ipv4RoutingTable's methods in C++.

Working with Arp

Ipv4 module subscribe to arpResolutionCompleted and arpResolutionFailed signals on Arp module. The Arp module accessed via arpOut gate, should not insert any module between Ipv4 and Arp. Before Ipv4 module send down a packet to lower layer, ask MacAddress of next hop from Arp via method call. If MacAddress unspecified, then start address resolution via Arp method call and insert packet to a queue specified by next hop addr. When received a arpResolutionCompleted, then send packets from queue of next hop addr. When received a arpResolutionFailed, then drop packets from queue of next hop addr. When Ipv4 module received an ARP packet from Lower Layer on some queueIn gate, then send out this packet on arpOut gate. When received a packet on arpIn gate, then send out this packet on the specified queueOut gate.

Performance model, QoS

In the current form, Ipv4 contains a FIFO which queues up Ipv4 datagrams; datagrams are processed in order. The processing time is determined by the procDelay module parameter.

The current performance model comes from the QueueBase C++ base class. If you need a more sophisticated performance model, you may change the module implementation (the Ipv4 class), and: (1) override the startService() method which determines processing time for a packet, or (2) use a different base class.

See also: Ipv4RoutingTable, Arp

Author: Andras Varga

Inheritance diagram

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

Parameters

Name	Type	Default value	Description
interfaceTableModule	string		The path to the InterfaceTable module
routingTableModule	string
arpModule	string
icmpModule	string
crcMode	string	"declared"
procDelay	double	0s
timeToLive	int	32
multicastTimeToLive	int	32
fragmentTimeout	double	60s
limitedBroadcast	bool	false	send out limited broadcast packets comming from higher layer
directBroadcastInterfaces	string	""	list of interfaces that direct broadcast is enabled (by default direct broadcast is disabled on all interfaces)

Properties

Name	Value	Description
display	i=block/routing

Gates

Name	Direction	Size	Description
transportIn	input
transportOut	output
queueIn	input
queueOut	output

Signals

Name	Type	Unit
ipv4DataOnNonrpf	inet::Ipv4Header
packetReceivedFromUpper	cPacket
packetReceivedFromLower	cPacket
packetDropped	cPacket
packetSentToLower	cPacket
ipv4DataOnRpf	inet::Ipv4Header
ipv4MdataRegister	inet::Packet
packetSentToUpper	cPacket
ipv4NewMulticast	inet::Ipv4Header

Statistics

Name	Title	Source	Record	Unit	Interpolation Mode
packetDropForwardingDisabled	packet drop: forwarding disabled	packetDropReasonIsForwardingDisabled(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none
packetDropAddressResolutionFailed	packet drop: address resolution failed	packetDropReasonIsAddressResolutionFailed(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none
packetDropUndefined	packet drop: undefined	packetDropReasonIsUndefined(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none
packetDropHopLimitReached	packet drop: hop limit reached	packetDropReasonIsHopLimitReached(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none
packetDropNoInterfaceFound	packet drop: no interface found	packetDropReasonIsNoInterfaceFound(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none
packetDropNoRouteFound	packet drop: no route found	packetDropReasonIsNoRouteFound(packetDropped)	count, sum(packetBytes), vector(packetBytes)		none

Source code

//
// Implements the IPv4 protocol. The protocol header is represented
// by the ~Ipv4Header message class.
//
// <b>Interfacing with higher layer protocols</b>
//
// To send a packet over IPv4 from a higher layer protocol, the module should
// fill in an ~L3AddressReq object, attach it to the packet with the Packets's
// addTag() method, then send the packet to the ~Ipv4 module.
//
// When ~Ipv4 sends up a packet to a higher layer protocol, it will also attach
// an ~L3AddressInd to the packet, with the source and destination IPv4 addresses
// of the IPv4 datagram in which the packet arrived.
//
// ~Ipv4 can serve several higher-layer protocols. The higher layer protocols
// should call registerProtocol with their gate towards the ~Ipv4 module,
// for fill up the protocol-to-gateindex map. When delivering packets to them,
// the output gate is determined from the Protocol in the IPv4 header.
//
// <b>Routing and interfacing with lower layers</b>
//
// The routing table is stored in the module ~Ipv4RoutingTable. When a datagram
// needs to be routed, ~Ipv4 queries ~Ipv4RoutingTable for the output interface
// (or "port") and next hop address of the packet. This is done by directly
// calling C++ methods (such as findBestMatchingRoute(destAddress)) of ~Ipv4RoutingTable.
// No message exchange with ~Ipv4RoutingTable takes place.
//
// A routed datagram will be sent to the queueOut, which is expected to be
// connected to ~INetworkInterface modules.
//
// Routing protocol implementations (e.g. OSPF and ISIS) can also query
// and manipulate the route table by calling ~Ipv4RoutingTable's methods in C++.
//
// <b>Working with Arp</b>
//
// Ipv4 module subscribe to arpResolutionCompleted and arpResolutionFailed signals on Arp module.
// The ~Arp module accessed via arpOut gate, should not insert any module between ~Ipv4 and ~Arp.
// Before Ipv4 module send down a packet to lower layer, ask MacAddress of next hop from Arp via
// method call. If MacAddress unspecified, then start address resolution via Arp method call and
// insert packet to a queue specified by next hop addr.
// When received a arpResolutionCompleted, then send packets from queue of next hop addr.
// When received a arpResolutionFailed, then drop packets from queue of next hop addr.
// When Ipv4 module received an ARP packet from Lower Layer on some queueIn gate,
// then send out this packet on arpOut gate. When received a packet on arpIn gate,
// then send out this packet on the specified queueOut gate.
//
// <b>Performance model, QoS</b>
//
// In the current form, ~Ipv4 contains a FIFO which queues up Ipv4 datagrams;
// datagrams are processed in order. The processing time is determined by the
// procDelay module parameter.
//
// The current performance model comes from the QueueBase C++ base class.
// If you need a more sophisticated performance model, you may change the
// module implementation (the Ipv4 class), and: (1) override the startService()
// method which determines processing time for a packet, or (2) use a
// different base class.
//
// @see ~Ipv4RoutingTable, ~Arp
//
// @author Andras Varga
//
simple Ipv4 like IIpv4
{
    parameters:
        string interfaceTableModule;   // The path to the InterfaceTable module
        string routingTableModule;
        string arpModule;
        string icmpModule;
        string crcMode @enum("declared","computed") = default("declared");
        double procDelay @unit(s) = default(0s);
        int timeToLive = default(32);
        int multicastTimeToLive = default(32);
        double fragmentTimeout @unit(s) = default(60s);
        bool limitedBroadcast = default(false); // send out limited broadcast packets comming from higher layer
        string directBroadcastInterfaces = default("");   // list of interfaces that direct broadcast is enabled (by default direct broadcast is disabled on all interfaces)
        @display("i=block/routing");
        @signal[packetSentToUpper](type=cPacket);
        @signal[packetReceivedFromUpper](type=cPacket);
        @signal[packetSentToLower](type=cPacket);
        @signal[packetReceivedFromLower](type=cPacket);
        @signal[packetDropped](type=cPacket);
        @signal[ipv4NewMulticast](type=inet::Ipv4Header);
        @signal[ipv4DataOnNonrpf](type=inet::Ipv4Header);
        @signal[ipv4DataOnRpf](type=inet::Ipv4Header);
        @signal[ipv4MdataRegister](type=inet::Packet);
        @statistic[packetDropAddressResolutionFailed](title="packet drop: address resolution failed"; source=packetDropReasonIsAddressResolutionFailed(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
        @statistic[packetDropHopLimitReached](title="packet drop: hop limit reached"; source=packetDropReasonIsHopLimitReached(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
        @statistic[packetDropForwardingDisabled](title="packet drop: forwarding disabled"; source=packetDropReasonIsForwardingDisabled(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
        @statistic[packetDropNoInterfaceFound](title="packet drop: no interface found"; source=packetDropReasonIsNoInterfaceFound(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
        @statistic[packetDropNoRouteFound](title="packet drop: no route found"; source=packetDropReasonIsNoRouteFound(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
        @statistic[packetDropUndefined](title="packet drop: undefined"; source=packetDropReasonIsUndefined(packetDropped); record=count,sum(packetBytes),vector(packetBytes); interpolationmode=none);
    gates:
        input transportIn @labels(Ipv4ControlInfo/down,TcpHeader,UdpHeader,SctpHeader);
        output transportOut @labels(Ipv4ControlInfo/up,TcpHeader,UdpHeader,SctpHeader);
        input queueIn @labels(Ipv4Header,ArpPacket,Ieee802Ctrl);
        output queueOut @labels(Ipv4Header,ArpPacket,Ieee802Ctrl);
}

File: src/inet/networklayer/ipv4/Ipv4.ned

---

This documentation is released under the Creative Commons license