INET Framework for OMNeT++/OMNEST
release 2006-10-20
INET Framework contains IPv4, IPv6, TCP, UDP protocol implementations,
and several application models. The framework also includes an MPLS model
with RSVP-TE and LDP signalling. Link-layer models are PPP, Ethernet and 802.11.
Static routing can be set up using network autoconfigurators, or one can use
routing protocol implementations.
The INET Framework supports wireless and mobile simulations as well. Support
for mobility and wireless communication has been derived from the
Mobility Framework.
This release features a new IEEE 802.11 model,
which supports both ad-hoc and infrastructure mode.
There are several other bugfixes and improvements as well; see the
WHATSNEW file in the distribution.
Recent additions: MPLS, RSVP-TE and LDP models revised/rewritten (Vojta Janota);
dynamic routing (OSPFv2 and RIP) provided by the Quagga Linux/*nix routing daemon
(ported into the INET Framework by Vojta Janota);
and a cleanroom OSPFv2 model (by Andras Babos).
History and contributors.
Introductory material:
A few useful starting points for browsing the documentation:
- the Usage Diagram
includes all modules and networks
- example networks: NClients, BulkTransfer, MulticastNetwork,
ARPTest, MixedLAN, etc.
- hosts, routers, switches: StandardHost, Router, EtherSwitch, EtherHub,
etc.
- network interfaces: EthernetInterface, PPPInterface, Ieee80211NicAdhoc,
Ieee80211NicSTA
- IEEE 802.11 models, both ad-hoc and infrastructure
mode are supported
- IP layer: IP, ARP and ICMP; RoutingTable
- IPv6 support: IPv6, IPv6NeighbourDiscovery, ICMPv6, RoutingTable6;
see IPv6 model overview
- transport layer: TCP, UDP
- InterfaceTable and NotificationBoard are there in every
host and router model
- queues in router network interfaces: DropTailQueue, REDQueue,
DropTailQoSQueue.
- FlatNetworkConfigurator automatically assigns IP addresses and
sets up static routes;
- ScenarioManager lets you change things in the model in the middle
of the simulation to study transient behaviour
- message classes: IPDatagram, TCPSegment, UDPPacket, EthernetIIFrame,
ARPPacket, PPPFrame, GenericAppMsg, EtherAppReq, etc.
- control info classes (used in communication between protocol layers):
IPControlInfo, TCPCommand, UDPControlInfo, Ieee802Ctrl, etc.
- application models: UDPVideoStreamSvr, UDPVideoStreamCli, UDPApp,
TCPSessionApp, TCPBasicClientApp, TCPGenericSrvApp, TCPSinkApp,
TCPSrvHostApp, EtherAppCli, EtherAppSrv, PingApp, etc.
- wireless support: ChannelControl, Nic80211
- mobility: MobileHost; mobility models such as TurtleMobility,
BonnMotionMobility, ANSimMobility, RandomWPMobility, MassMobility
- MPLS models: the core modules are MPLS, LIBTable, LDP, RSVP, TED,
LinkStateRouting; MPLS-enabled routers are LDP_LSR, RSVP_LSR;
see also the list of implemented standards
- dynamic routing is provided by the Daemon module (the Quagga routing
daemon ported into the INET Framework) used inside QuaggaRouter;
alternatively one can run OSPFRouter which relies on the OSPFRouting
module;
- support for recording nam traces is provided by NAMTrace and
NAMTraceWriter
Related documentation:
Generated by opp_neddoc.