INET framework for the OMNeT++ discrete event simulator
C++ Python Yacc C Perl XSLT Other
Permalink
Failed to load latest commit information.
3rdparty 3rdparty/README: English fixes; mention LD_LIBRARY_PATH Feb 23, 2013
_scripts reformat scripts fixed Jul 20, 2016
doc doc: build only PDF output from the inet-manual Jun 9, 2016
etc mobility: removed sumo-launchd script as TraciMobility is no longer p… May 8, 2015
examples Examples: Changed all visualizer submodules to be optional. Jan 30, 2017
migrate CRLF to LF conversion Feb 5, 2010
misc/gdb/inet prettyprinter: changes for enable/disable pretty printers Jan 7, 2013
src omnetpp5.1 ccanvas compatibility changes: do not use deprecated funct… Feb 15, 2017
templates wizards: updated wizards so generated code is up to date now. Aug 7, 2012
tests tests: fixes Feb 15, 2017
tutorials Examples: Changed all visualizer submodules to be optional. Jan 30, 2017
.cproject build: turned on the exporting of the include folder for dependent pr… Dec 23, 2016
.gdbinit.py .gdbinit: Fixed python syntax. Jan 4, 2017
.gitattributes build: changed .gitattributes so project settings files will no longe… Aug 23, 2013
.gitignore build: create and include an opp_defines.h file that contains the WIT… Jul 8, 2016
.nedfolders build: using the new opp_featuretool Feb 26, 2016
.oppbuildspec build: turned on the exporting of the include folder for dependent pr… Dec 23, 2016
.oppfeatures .oppfeatures: Added separate features for the wireless and visualizat… Jan 30, 2017
.project build: fixed top level makefiles to be in sync with features enabled … Nov 18, 2011
CREDITS CR/LF conversion Dec 15, 2009
INSTALL doc: updated notes for using the got repo Aug 23, 2013
License CR/LF conversion Dec 15, 2009
Makefile build: create a precompiled header file when using gcc or clang Jun 27, 2016
Makefile.vc mobility: removed TraCI mobility as it is part of the Veins framework… Apr 22, 2015
README doc: readme/whatsnew updates Jun 24, 2015
WHATSNEW doc: whatsnew update Jan 4, 2017
__TODO backport: removed TODO - ChannelInstaller removed at 2011-03-10 Feb 3, 2014
__wizards.txt removed old note files Dec 7, 2011
doxy.cfg mobility: removed TraCI mobility as it is part of the Veins framework… Apr 22, 2015
inet_featuretool build: supporting the IDE generated features.h file, too Jul 8, 2016

README

INET Framework for OMNEST/OMNeT++
=================================

The INET framework (inet.omnetpp.org) is an open-source communication networks 
simulation package, written for the OMNEST/OMNeT++ simulation system. The INET 
framework contains models for several Internet protocols: beyond TCP and IP there 
is UDP, Ethernet, PPP and MPLS with LDP and RSVP-TE signalling. See the CREDITS 
file for the names of people who have contributed to the INET Framework.

IMPORTANT: The INET Framework is continuously being improved: new parts
are added, bugs are corrected, and so on. We cannot assert that any protocol
implemented here will work fully according to the specifications. YOU ARE
RESPONSIBLE YOURSELF TO MAKE SURE THAT THE MODELS YOU USE IN YOUR SIMULATIONS
WORK CORRECTLY, AND YOU'RE GETTING VALID RESULTS.

Contributions are highly welcome. You can make a difference!

See the WHATSNEW file for recent changes.


GETTING STARTED
---------------
You may start by downloading and installing the INET framework. Read the INSTALL
file for further information.

Then you can gather initial experience by starting some examples or following the 
INET wireless tutorial (tutorials/wireless). After that, you can learn the NED 
language from the OMNeT++ manual & sample simulations.

After that, you may write your own topologies using the NED language. You may
assign some of the submodule parameters in NED files. You may leave some of
them unassigned.

Then, you may assign unassigned module parameters in omnetpp.ini of your
simulation. (You can refer to sample simulations & manual for the content of
omnetpp.ini)

Finally, you will be ready to run your simulation. As you see, you may use
the INET framework without writing any C++ code, as long as you use the
available modules.

To implement new protocols or modify existing ones, you'll need to add your 
code somewhere under the src directory. If you add new files under the 'src' 
directory you will need to regenerate the makefiles (using the 'make makefiles' 
command).

If you want to use external interfaces in INET, please install libpcap-dev (on linux)
or winpcap (on windows from www.winpcap.org) and enable the "Emulation" feature
either in the IDE or using the inet_featuretool then regenerate the INET makefile
using 'make makefiles'.