INET Framework for OMNeT++/OMNEST
INET Framework contains IPv4, IPv6, TCP, SCTP, 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.
See the WHATSNEW file in the distribution for the list of recent changes.
A few useful starting points for browsing the documentation:
- hosts, routers, switches and other network level modules: StandardHost, Router, EtherSwitch, EtherHub, InternetCloud etc.
- network interfaces: EthernetInterface, PppInterface, Ieee80211Interface
- IEEE 802.11 models, both ad-hoc and infrastructure mode are supported
- IPv4 layer: Ipv4, Arp and Icmp; Ipv4RoutingTable
- IPv6 support: Ipv6, Ipv6NeighbourDiscovery, Icmpv6, Ipv6RoutingTable; see Ipv6 model overview
- transport layer: Tcp, Udp, SCTP
- InterfaceTable and Ipv4RoutingTable can be found in every host and router model
- queues in router network interfaces: DropTailQueue, DiffservQueue.
- Ipv4NetworkConfigurator automatically assigns IPv4 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: Ipv4Header, TcpHeader, UdpHeader, EthernetIIFrame, ArpPacket, PppFrame, GenericAppMsg, EtherAppReq, etc.
- control info classes (used in communication between protocol layers): TcpCommand, UdpControlInfo, Ieee802Ctrl, etc.
- application models: UdpVideoStreamServer, UdpVideoStreamClient, UdpBasicApp, UdpEchoApp, TcpSessionApp, TcpBasicClientApp, TcpGenericServerApp, TcpSinkApp, TcpServerHostApp, EtherAppClient, EtherAppServer, PingApp, SimpleVoipSender, SimpleVoipReceiver etc.
- wireless support: IRadioMedium, Ieee80211Interface
- Mobility models: TurtleMobility, BonnMotionMobility, AnsimMobility, RandomWaypointMobility, MassMobility
- Mpls models: the core modules are Mpls, LibTable, Ldp, RsvpTe, Ted, LinkStateRouting; MPLS-enabled routers are LdpMplsRouter, RsvpMplsRouter; see also the list of implemented standards
- dynamic routing is provided by the Daemon module (the Quagga routing daemon ported into the INET Framework, currently in a different project) used inside QuaggaRouter; alternatively one can run OspfRouter which relies on the Ospf module;
Generated by neddoc.