docs: updates to cleanup formatting on tables and denote that the python gui is the default in index.md
This commit is contained in:
Blake Harnden
parent
a7588a2188
commit
482ad037f4
9 changed files with 310 additions and 310 deletions
|
|
@ -27,27 +27,27 @@ will allow quickly dragging and dropping that node type during creation.
|
|||
|
||||
## Available Services
|
||||
|
||||
| Service Group | Services |
|
||||
|---|---|
|
||||
|[BIRD](services/bird.md)|BGP, OSPF, RADV, RIP, Static|
|
||||
|[EMANE](services/emane.md)|Transport Service|
|
||||
|[FRR](services/frr.md)|BABEL, BGP, OSPFv2, OSPFv3, PIMD, RIP, RIPNG, Zebra|
|
||||
|[NRL](services/nrl.md)|arouted, MGEN Sink, MGEN Actor, NHDP, OLSR, OLSRORG, OLSRv2, SMF|
|
||||
|[Quagga](services/quagga.md)|BABEL, BGP, OSPFv2, OSPFv3, OSPFv3 MDR, RIP, RIPNG, XPIMD, Zebra|
|
||||
|[SDN](services/sdn.md)|OVS, RYU|
|
||||
|[Security](services/security.md)|Firewall, IPsec, NAT, VPN Client, VPN Server|
|
||||
|[Utility](services/utility.md)|ATD, Routing Utils, DHCP, FTP, IP Forward, PCAP, RADVD, SSF, UCARP|
|
||||
|[XORP](services/xorp.md)|BGP, OLSR, OSPFv2, OSPFv3, PIMSM4, PIMSM6, RIP, RIPNG, Router Manager|
|
||||
| Service Group | Services |
|
||||
|----------------------------------|-----------------------------------------------------------------------|
|
||||
| [BIRD](services/bird.md) | BGP, OSPF, RADV, RIP, Static |
|
||||
| [EMANE](services/emane.md) | Transport Service |
|
||||
| [FRR](services/frr.md) | BABEL, BGP, OSPFv2, OSPFv3, PIMD, RIP, RIPNG, Zebra |
|
||||
| [NRL](services/nrl.md) | arouted, MGEN Sink, MGEN Actor, NHDP, OLSR, OLSRORG, OLSRv2, SMF |
|
||||
| [Quagga](services/quagga.md) | BABEL, BGP, OSPFv2, OSPFv3, OSPFv3 MDR, RIP, RIPNG, XPIMD, Zebra |
|
||||
| [SDN](services/sdn.md) | OVS, RYU |
|
||||
| [Security](services/security.md) | Firewall, IPsec, NAT, VPN Client, VPN Server |
|
||||
| [Utility](services/utility.md) | ATD, Routing Utils, DHCP, FTP, IP Forward, PCAP, RADVD, SSF, UCARP |
|
||||
| [XORP](services/xorp.md) | BGP, OLSR, OSPFv2, OSPFv3, PIMSM4, PIMSM6, RIP, RIPNG, Router Manager |
|
||||
|
||||
## Node Types and Default Services
|
||||
|
||||
Here are the default node types and their services:
|
||||
|
||||
| Node Type | Services |
|
||||
|---|---|
|
||||
| *router* | zebra, OSFPv2, OSPFv3, and IPForward services for IGP link-state routing. |
|
||||
| *PC* | DefaultRoute service for having a default route when connected directly to a router. |
|
||||
| *mdr* | zebra, OSPFv3MDR, and IPForward services for wireless-optimized MANET Designated Router routing. |
|
||||
| Node Type | Services |
|
||||
|-----------|--------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| *router* | zebra, OSFPv2, OSPFv3, and IPForward services for IGP link-state routing. |
|
||||
| *PC* | DefaultRoute service for having a default route when connected directly to a router. |
|
||||
| *mdr* | zebra, OSPFv3MDR, and IPForward services for wireless-optimized MANET Designated Router routing. |
|
||||
| *prouter* | a physical router, having the same default services as the *router* node type; for incorporating Linux testbed machines into an emulation. |
|
||||
|
||||
Configuration files can be automatically generated by each service. For
|
||||
|
|
|
|||
|
|
@ -9,13 +9,13 @@ The CORE source consists of several different programming languages for
|
|||
historical reasons. Current development focuses on the Python modules and
|
||||
daemon. Here is a brief description of the source directories.
|
||||
|
||||
| Directory | Description |
|
||||
|---|---|
|
||||
|daemon|Python CORE daemon code that handles receiving API calls and creating containers|
|
||||
|docs|Markdown Documentation currently hosted on GitHub|
|
||||
|gui|Tcl/Tk GUI|
|
||||
|man|Template files for creating man pages for various CORE command line utilities|
|
||||
|netns|C program for creating CORE containers|
|
||||
| Directory | Description |
|
||||
|-----------|--------------------------------------------------------------------------------------|
|
||||
| daemon | Python CORE daemon/gui code that handles receiving API calls and creating containers |
|
||||
| docs | Markdown Documentation currently hosted on GitHub |
|
||||
| gui | Tcl/Tk GUI |
|
||||
| man | Template files for creating man pages for various CORE command line utilities |
|
||||
| netns | C program for creating CORE containers |
|
||||
|
||||
## Getting started
|
||||
|
||||
|
|
|
|||
|
|
@ -62,13 +62,13 @@ Every topic below assumes CORE, EMANE, and OSPF MDR have been installed.
|
|||
|
||||
> **WARNING:** demo files will be found within the new `core-pygui`
|
||||
|
||||
|Topic|Model|Description|
|
||||
|---|---|---|
|
||||
|[XML Files](emane/files.md)|RF Pipe|Overview of generated XML files used to drive EMANE|
|
||||
|[GPSD](emane/gpsd.md)|RF Pipe|Overview of running and integrating gpsd with EMANE|
|
||||
|[Precomputed](emane/precomputed.md)|RF Pipe|Overview of using the precomputed propagation model|
|
||||
|[EEL](emane/eel.md)|RF Pipe|Overview of using the Emulation Event Log (EEL) Generator|
|
||||
|[Antenna Profiles](emane/antenna.md)|RF Pipe|Overview of using antenna profiles in EMANE|
|
||||
| Topic | Model | Description |
|
||||
|--------------------------------------|---------|-----------------------------------------------------------|
|
||||
| [XML Files](emane/files.md) | RF Pipe | Overview of generated XML files used to drive EMANE |
|
||||
| [GPSD](emane/gpsd.md) | RF Pipe | Overview of running and integrating gpsd with EMANE |
|
||||
| [Precomputed](emane/precomputed.md) | RF Pipe | Overview of using the precomputed propagation model |
|
||||
| [EEL](emane/eel.md) | RF Pipe | Overview of using the Emulation Event Log (EEL) Generator |
|
||||
| [Antenna Profiles](emane/antenna.md) | RF Pipe | Overview of using antenna profiles in EMANE |
|
||||
|
||||
## EMANE Configuration
|
||||
|
||||
|
|
|
|||
262
docs/gui.md
262
docs/gui.md
|
|
@ -93,46 +93,46 @@ the left side of the CORE window. Below are brief descriptions for each toolbar
|
|||
item, starting from the top. Most of the tools are grouped into related
|
||||
sub-menus, which appear when you click on their group icon.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Selection Tool | Tool for selecting, moving, configuring nodes. |
|
||||
|  | Start Button | Starts Execute mode, instantiates the emulation. |
|
||||
|  | Link | Allows network links to be drawn between two nodes by clicking and dragging the mouse. |
|
||||
| Icon | Name | Description |
|
||||
|----------------------------|----------------|----------------------------------------------------------------------------------------|
|
||||
|  | Selection Tool | Tool for selecting, moving, configuring nodes. |
|
||||
|  | Start Button | Starts Execute mode, instantiates the emulation. |
|
||||
|  | Link | Allows network links to be drawn between two nodes by clicking and dragging the mouse. |
|
||||
|
||||
### CORE Nodes
|
||||
|
||||
These nodes will create a new node container and run associated services.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Router | Runs Quagga OSPFv2 and OSPFv3 routing to forward packets. |
|
||||
|  | Host | Emulated server machine having a default route, runs SSH server. |
|
||||
|  | PC | Basic emulated machine having a default route, runs no processes by default. |
|
||||
|  | MDR | Runs Quagga OSPFv3 MDR routing for MANET-optimized routing. |
|
||||
|  | PRouter | Physical router represents a real testbed machine. |
|
||||
|  | Edit | Bring up the custom node dialog. |
|
||||
| Icon | Name | Description |
|
||||
|-----------------------------------------|---------|------------------------------------------------------------------------------|
|
||||
|  | Router | Runs Quagga OSPFv2 and OSPFv3 routing to forward packets. |
|
||||
|  | Host | Emulated server machine having a default route, runs SSH server. |
|
||||
|  | PC | Basic emulated machine having a default route, runs no processes by default. |
|
||||
|  | MDR | Runs Quagga OSPFv3 MDR routing for MANET-optimized routing. |
|
||||
|  | PRouter | Physical router represents a real testbed machine. |
|
||||
|  | Edit | Bring up the custom node dialog. |
|
||||
|
||||
### Network Nodes
|
||||
|
||||
These nodes are mostly used to create a Linux bridge that serves the
|
||||
purpose described below.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Hub | Ethernet hub forwards incoming packets to every connected node. |
|
||||
|  | Switch | Ethernet switch intelligently forwards incoming packets to attached hosts using an Ethernet address hash table. |
|
||||
|  | Wireless LAN | When routers are connected to this WLAN node, they join a wireless network and an antenna is drawn instead of a connecting line; the WLAN node typically controls connectivity between attached wireless nodes based on the distance between them. |
|
||||
|  | RJ45 | RJ45 Physical Interface Tool, emulated nodes can be linked to real physical interfaces; using this tool, real networks and devices can be physically connected to the live-running emulation. |
|
||||
|  | Tunnel | Tool allows connecting together more than one CORE emulation using GRE tunnels. |
|
||||
| Icon | Name | Description |
|
||||
|-------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
|  | Hub | Ethernet hub forwards incoming packets to every connected node. |
|
||||
|  | Switch | Ethernet switch intelligently forwards incoming packets to attached hosts using an Ethernet address hash table. |
|
||||
|  | Wireless LAN | When routers are connected to this WLAN node, they join a wireless network and an antenna is drawn instead of a connecting line; the WLAN node typically controls connectivity between attached wireless nodes based on the distance between them. |
|
||||
|  | RJ45 | RJ45 Physical Interface Tool, emulated nodes can be linked to real physical interfaces; using this tool, real networks and devices can be physically connected to the live-running emulation. |
|
||||
|  | Tunnel | Tool allows connecting together more than one CORE emulation using GRE tunnels. |
|
||||
|
||||
### Annotation Tools
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Marker | For drawing marks on the canvas. |
|
||||
|  | Oval | For drawing circles on the canvas that appear in the background. |
|
||||
| Icon | Name | Description |
|
||||
|-------------------------------|-----------|---------------------------------------------------------------------|
|
||||
|  | Marker | For drawing marks on the canvas. |
|
||||
|  | Oval | For drawing circles on the canvas that appear in the background. |
|
||||
|  | Rectangle | For drawing rectangles on the canvas that appear in the background. |
|
||||
|  | Text | For placing text captions on the canvas. |
|
||||
|  | Text | For placing text captions on the canvas. |
|
||||
|
||||
### Execution Toolbar
|
||||
|
||||
|
|
@ -140,14 +140,14 @@ When the Start button is pressed, CORE switches to Execute mode, and the Edit
|
|||
toolbar on the left of the CORE window is replaced with the Execution toolbar
|
||||
Below are the items on this toolbar, starting from the top.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Selection Tool | In Execute mode, the Selection Tool can be used for moving nodes around the canvas, and double-clicking on a node will open a shell window for that node; right-clicking on a node invokes a pop-up menu of run-time options for that node. |
|
||||
|  | Stop Button | Stops Execute mode, terminates the emulation, returns CORE to edit mode. |
|
||||
|  | Observer Widgets Tool | Clicking on this magnifying glass icon invokes a menu for easily selecting an Observer Widget. The icon has a darker gray background when an Observer Widget is active, during which time moving the mouse over a node will pop up an information display for that node. |
|
||||
|  | Marker | For drawing freehand lines on the canvas, useful during demonstrations; markings are not saved. |
|
||||
|  | Two-node Tool | Click to choose a starting and ending node, and run a one-time *traceroute* between those nodes or a continuous *ping -R* between nodes. The output is displayed in real time in a results box, while the IP addresses are parsed and the complete network path is highlighted on the CORE display. |
|
||||
|  | Run Tool | This tool allows easily running a command on all or a subset of all nodes. A list box allows selecting any of the nodes. A text entry box allows entering any command. The command should return immediately, otherwise the display will block awaiting response. The *ping* command, for example, with no parameters, is not a good idea. The result of each command is displayed in a results box. The first occurrence of the special text "NODE" will be replaced with the node name. The command will not be attempted to run on nodes that are not routers, PCs, or hosts, even if they are selected. |
|
||||
| Icon | Name | Description |
|
||||
|-----------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
|  | Selection Tool | In Execute mode, the Selection Tool can be used for moving nodes around the canvas, and double-clicking on a node will open a shell window for that node; right-clicking on a node invokes a pop-up menu of run-time options for that node. |
|
||||
|  | Stop Button | Stops Execute mode, terminates the emulation, returns CORE to edit mode. |
|
||||
|  | Observer Widgets Tool | Clicking on this magnifying glass icon invokes a menu for easily selecting an Observer Widget. The icon has a darker gray background when an Observer Widget is active, during which time moving the mouse over a node will pop up an information display for that node. |
|
||||
|  | Marker | For drawing freehand lines on the canvas, useful during demonstrations; markings are not saved. |
|
||||
|  | Two-node Tool | Click to choose a starting and ending node, and run a one-time *traceroute* between those nodes or a continuous *ping -R* between nodes. The output is displayed in real time in a results box, while the IP addresses are parsed and the complete network path is highlighted on the CORE display. |
|
||||
|  | Run Tool | This tool allows easily running a command on all or a subset of all nodes. A list box allows selecting any of the nodes. A text entry box allows entering any command. The command should return immediately, otherwise the display will block awaiting response. The *ping* command, for example, with no parameters, is not a good idea. The result of each command is displayed in a results box. The first occurrence of the special text "NODE" will be replaced with the node name. The command will not be attempted to run on nodes that are not routers, PCs, or hosts, even if they are selected. |
|
||||
|
||||
## Menu
|
||||
|
||||
|
|
@ -160,95 +160,95 @@ menu, by clicking the dashed line at the top.
|
|||
The File menu contains options for manipulating the **.imn** Configuration
|
||||
Files. Generally, these menu items should not be used in Execute mode.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| New | This starts a new file with an empty canvas. |
|
||||
| Open | Invokes the File Open dialog box for selecting a new **.imn** or XML file to open. You can change the default path used for this dialog in the Preferences Dialog. |
|
||||
| Save | Saves the current topology. If you have not yet specified a file name, the Save As dialog box is invoked. |
|
||||
| Save As XML | Invokes the Save As dialog box for selecting a new **.xml** file for saving the current configuration in the XML file. |
|
||||
| Save As imn | Invokes the Save As dialog box for selecting a new **.imn** topology file for saving the current configuration. Files are saved in the *IMUNES network configuration* file. |
|
||||
| Export Python script | Prints Python snippets to the console, for inclusion in a CORE Python script. |
|
||||
| Execute XML or Python script | Invokes a File Open dialog box for selecting an XML file to run or a Python script to run and automatically connect to. If a Python script, the script must create a new CORE Session and add this session to the daemon's list of sessions in order for this to work. |
|
||||
| Option | Description |
|
||||
|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| New | This starts a new file with an empty canvas. |
|
||||
| Open | Invokes the File Open dialog box for selecting a new **.imn** or XML file to open. You can change the default path used for this dialog in the Preferences Dialog. |
|
||||
| Save | Saves the current topology. If you have not yet specified a file name, the Save As dialog box is invoked. |
|
||||
| Save As XML | Invokes the Save As dialog box for selecting a new **.xml** file for saving the current configuration in the XML file. |
|
||||
| Save As imn | Invokes the Save As dialog box for selecting a new **.imn** topology file for saving the current configuration. Files are saved in the *IMUNES network configuration* file. |
|
||||
| Export Python script | Prints Python snippets to the console, for inclusion in a CORE Python script. |
|
||||
| Execute XML or Python script | Invokes a File Open dialog box for selecting an XML file to run or a Python script to run and automatically connect to. If a Python script, the script must create a new CORE Session and add this session to the daemon's list of sessions in order for this to work. |
|
||||
| Execute Python script with options | Invokes a File Open dialog box for selecting a Python script to run and automatically connect to. After a selection is made, a Python Script Options dialog box is invoked to allow for command-line options to be added. The Python script must create a new CORE Session and add this session to the daemon's list of sessions in order for this to work. |
|
||||
| Open current file in editor | This opens the current topology file in the **vim** text editor. First you need to save the file. Once the file has been edited with a text editor, you will need to reload the file to see your changes. The text editor can be changed from the Preferences Dialog. |
|
||||
| Print | This uses the Tcl/Tk postscript command to print the current canvas to a printer. A dialog is invoked where you can specify a printing command, the default being **lpr**. The postscript output is piped to the print command. |
|
||||
| Save screenshot | Saves the current canvas as a postscript graphic file. |
|
||||
| Recently used files | Above the Quit menu command is a list of recently use files, if any have been opened. You can clear this list in the Preferences dialog box. You can specify the number of files to keep in this list from the Preferences dialog. Click on one of the file names listed to open that configuration file. |
|
||||
| Quit | The Quit command should be used to exit the CORE GUI. CORE may prompt for termination if you are currently in Execute mode. Preferences and the recently-used files list are saved. |
|
||||
| Open current file in editor | This opens the current topology file in the **vim** text editor. First you need to save the file. Once the file has been edited with a text editor, you will need to reload the file to see your changes. The text editor can be changed from the Preferences Dialog. |
|
||||
| Print | This uses the Tcl/Tk postscript command to print the current canvas to a printer. A dialog is invoked where you can specify a printing command, the default being **lpr**. The postscript output is piped to the print command. |
|
||||
| Save screenshot | Saves the current canvas as a postscript graphic file. |
|
||||
| Recently used files | Above the Quit menu command is a list of recently use files, if any have been opened. You can clear this list in the Preferences dialog box. You can specify the number of files to keep in this list from the Preferences dialog. Click on one of the file names listed to open that configuration file. |
|
||||
| Quit | The Quit command should be used to exit the CORE GUI. CORE may prompt for termination if you are currently in Execute mode. Preferences and the recently-used files list are saved. |
|
||||
|
||||
### Edit Menu
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Undo | Attempts to undo the last edit in edit mode. |
|
||||
| Redo | Attempts to redo an edit that has been undone. |
|
||||
| Cut, Copy, Paste | Used to cut, copy, and paste a selection. When nodes are pasted, their node numbers are automatically incremented, and existing links are preserved with new IP addresses assigned. Services and their customizations are copied to the new node, but care should be taken as node IP addresses have changed with possibly old addresses remaining in any custom service configurations. Annotations may also be copied and pasted.
|
||||
| Select All | Selects all items on the canvas. Selected items can be moved as a group. |
|
||||
| Select Adjacent | Select all nodes that are linked to the already selected node(s). For wireless nodes this simply selects the WLAN node(s) that the wireless node belongs to. You can use this by clicking on a node and pressing CTRL+N to select the adjacent nodes. |
|
||||
| Find... | Invokes the *Find* dialog box. The Find dialog can be used to search for nodes by name or number. Results are listed in a table that includes the node or link location and details such as IP addresses or link parameters. Clicking on a result will focus the canvas on that node or link, switching canvases if necessary. |
|
||||
| Clear marker | Clears any annotations drawn with the marker tool. Also clears any markings used to indicate a node's status. |
|
||||
| Preferences... | Invokes the Preferences dialog box. |
|
||||
| Option | Description |
|
||||
|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Undo | Attempts to undo the last edit in edit mode. |
|
||||
| Redo | Attempts to redo an edit that has been undone. |
|
||||
| Cut, Copy, Paste | Used to cut, copy, and paste a selection. When nodes are pasted, their node numbers are automatically incremented, and existing links are preserved with new IP addresses assigned. Services and their customizations are copied to the new node, but care should be taken as node IP addresses have changed with possibly old addresses remaining in any custom service configurations. Annotations may also be copied and pasted. |
|
||||
| Select All | Selects all items on the canvas. Selected items can be moved as a group. |
|
||||
| Select Adjacent | Select all nodes that are linked to the already selected node(s). For wireless nodes this simply selects the WLAN node(s) that the wireless node belongs to. You can use this by clicking on a node and pressing CTRL+N to select the adjacent nodes. |
|
||||
| Find... | Invokes the *Find* dialog box. The Find dialog can be used to search for nodes by name or number. Results are listed in a table that includes the node or link location and details such as IP addresses or link parameters. Clicking on a result will focus the canvas on that node or link, switching canvases if necessary. |
|
||||
| Clear marker | Clears any annotations drawn with the marker tool. Also clears any markings used to indicate a node's status. |
|
||||
| Preferences... | Invokes the Preferences dialog box. |
|
||||
|
||||
### Canvas Menu
|
||||
|
||||
The canvas menu provides commands for adding, removing, changing, and switching
|
||||
to different editing canvases.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| New | Creates a new empty canvas at the right of all existing canvases. |
|
||||
| Manage... | Invokes the *Manage Canvases* dialog box, where canvases may be renamed and reordered, and you can easily switch to one of the canvases by selecting it. |
|
||||
| Delete | Deletes the current canvas and all items that it contains. |
|
||||
| Size/scale... | Invokes a Canvas Size and Scale dialog that allows configuring the canvas size, scale, and geographic reference point. The size controls allow changing the width and height of the current canvas, in pixels or meters. The scale allows specifying how many meters are equivalent to 100 pixels. The reference point controls specify the latitude, longitude, and altitude reference point used to convert between geographic and Cartesian coordinate systems. By clicking the *Save as default* option, all new canvases will be created with these properties. The default canvas size can also be changed in the Preferences dialog box.
|
||||
| Wallpaper... | Used for setting the canvas background image. |
|
||||
| Previous, Next, First, Last | Used for switching the active canvas to the first, last, or adjacent canvas. |
|
||||
| Option | Description |
|
||||
|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| New | Creates a new empty canvas at the right of all existing canvases. |
|
||||
| Manage... | Invokes the *Manage Canvases* dialog box, where canvases may be renamed and reordered, and you can easily switch to one of the canvases by selecting it. |
|
||||
| Delete | Deletes the current canvas and all items that it contains. |
|
||||
| Size/scale... | Invokes a Canvas Size and Scale dialog that allows configuring the canvas size, scale, and geographic reference point. The size controls allow changing the width and height of the current canvas, in pixels or meters. The scale allows specifying how many meters are equivalent to 100 pixels. The reference point controls specify the latitude, longitude, and altitude reference point used to convert between geographic and Cartesian coordinate systems. By clicking the *Save as default* option, all new canvases will be created with these properties. The default canvas size can also be changed in the Preferences dialog box. |
|
||||
| Wallpaper... | Used for setting the canvas background image. |
|
||||
| Previous, Next, First, Last | Used for switching the active canvas to the first, last, or adjacent canvas. |
|
||||
|
||||
### View Menu
|
||||
|
||||
The View menu features items for controlling what is displayed on the drawing
|
||||
canvas.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Show | Opens a submenu of items that can be displayed or hidden, such as interface names, addresses, and labels. Use these options to help declutter the display. These options are generally saved in the topology files, so scenarios have a more consistent look when copied from one computer to another. |
|
||||
| Show hidden nodes | Reveal nodes that have been hidden. Nodes are hidden by selecting one or more nodes, right-clicking one and choosing *hide*. |
|
||||
| Locked | Toggles locked view; when the view is locked, nodes cannot be moved around on the canvas with the mouse. This could be useful when sharing the topology with someone and you do not expect them to change things. |
|
||||
| 3D GUI... | Launches a 3D GUI by running the command defined under Preferences, *3D GUI command*. This is typically a script that runs the SDT3D display. SDT is the Scripted Display Tool from NRL that is based on NASA's Java-based WorldWind virtual globe software. |
|
||||
| Zoom In | Magnifies the display. You can also zoom in by clicking *zoom 100%* label in the status bar, or by pressing the **+** (plus) key. |
|
||||
| Zoom Out | Reduces the size of the display. You can also zoom out by right-clicking *zoom 100%* label in the status bar or by pressing the **-** (minus) key. |
|
||||
| Option | Description |
|
||||
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Show | Opens a submenu of items that can be displayed or hidden, such as interface names, addresses, and labels. Use these options to help declutter the display. These options are generally saved in the topology files, so scenarios have a more consistent look when copied from one computer to another. |
|
||||
| Show hidden nodes | Reveal nodes that have been hidden. Nodes are hidden by selecting one or more nodes, right-clicking one and choosing *hide*. |
|
||||
| Locked | Toggles locked view; when the view is locked, nodes cannot be moved around on the canvas with the mouse. This could be useful when sharing the topology with someone and you do not expect them to change things. |
|
||||
| 3D GUI... | Launches a 3D GUI by running the command defined under Preferences, *3D GUI command*. This is typically a script that runs the SDT3D display. SDT is the Scripted Display Tool from NRL that is based on NASA's Java-based WorldWind virtual globe software. |
|
||||
| Zoom In | Magnifies the display. You can also zoom in by clicking *zoom 100%* label in the status bar, or by pressing the **+** (plus) key. |
|
||||
| Zoom Out | Reduces the size of the display. You can also zoom out by right-clicking *zoom 100%* label in the status bar or by pressing the **-** (minus) key. |
|
||||
|
||||
### Tools Menu
|
||||
|
||||
The tools menu lists different utility functions.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Autorearrange all | Automatically arranges all nodes on the canvas. Nodes having a greater number of links are moved to the center. This mode can continue to run while placing nodes. To turn off this autorearrange mode, click on a blank area of the canvas with the select tool, or choose this menu option again. |
|
||||
| Autorearrange selected | Automatically arranges the selected nodes on the canvas. |
|
||||
| Align to grid | Moves nodes into a grid formation, starting with the smallest-numbered node in the upper-left corner of the canvas, arranging nodes in vertical columns. |
|
||||
| Traffic... | Invokes the CORE Traffic Flows dialog box, which allows configuring, starting, and stopping MGEN traffic flows for the emulation. |
|
||||
| IP addresses... | Invokes the IP Addresses dialog box for configuring which IPv4/IPv6 prefixes are used when automatically addressing new interfaces. |
|
||||
| MAC addresses... | Invokes the MAC Addresses dialog box for configuring the starting number used as the lowest byte when generating each interface MAC address. This value should be changed when tunneling between CORE emulations to prevent MAC address conflicts. |
|
||||
| Build hosts file... | Invokes the Build hosts File dialog box for generating **/etc/hosts** file entries based on IP addresses used in the emulation. |
|
||||
| Renumber nodes... | Invokes the Renumber Nodes dialog box, which allows swapping one node number with another in a few clicks. |
|
||||
| Experimental... | Menu of experimental options, such as a tool to convert ns-2 scripts to IMUNES imn topologies, supporting only basic ns-2 functionality, and a tool for automatically dividing up a topology into partitions. |
|
||||
| Topology generator | Opens a submenu of topologies to generate. You can first select the type of node that the topology should consist of, or routers will be chosen by default. Nodes may be randomly placed, aligned in grids, or various other topology patterns. All of the supported patterns are listed in the table below. |
|
||||
| Debugger... | Opens the CORE Debugger window for executing arbitrary Tcl/Tk commands. |
|
||||
| Option | Description |
|
||||
|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Autorearrange all | Automatically arranges all nodes on the canvas. Nodes having a greater number of links are moved to the center. This mode can continue to run while placing nodes. To turn off this autorearrange mode, click on a blank area of the canvas with the select tool, or choose this menu option again. |
|
||||
| Autorearrange selected | Automatically arranges the selected nodes on the canvas. |
|
||||
| Align to grid | Moves nodes into a grid formation, starting with the smallest-numbered node in the upper-left corner of the canvas, arranging nodes in vertical columns. |
|
||||
| Traffic... | Invokes the CORE Traffic Flows dialog box, which allows configuring, starting, and stopping MGEN traffic flows for the emulation. |
|
||||
| IP addresses... | Invokes the IP Addresses dialog box for configuring which IPv4/IPv6 prefixes are used when automatically addressing new interfaces. |
|
||||
| MAC addresses... | Invokes the MAC Addresses dialog box for configuring the starting number used as the lowest byte when generating each interface MAC address. This value should be changed when tunneling between CORE emulations to prevent MAC address conflicts. |
|
||||
| Build hosts file... | Invokes the Build hosts File dialog box for generating **/etc/hosts** file entries based on IP addresses used in the emulation. |
|
||||
| Renumber nodes... | Invokes the Renumber Nodes dialog box, which allows swapping one node number with another in a few clicks. |
|
||||
| Experimental... | Menu of experimental options, such as a tool to convert ns-2 scripts to IMUNES imn topologies, supporting only basic ns-2 functionality, and a tool for automatically dividing up a topology into partitions. |
|
||||
| Topology generator | Opens a submenu of topologies to generate. You can first select the type of node that the topology should consist of, or routers will be chosen by default. Nodes may be randomly placed, aligned in grids, or various other topology patterns. All of the supported patterns are listed in the table below. |
|
||||
| Debugger... | Opens the CORE Debugger window for executing arbitrary Tcl/Tk commands. |
|
||||
|
||||
#### Topology Generator
|
||||
|
||||
| Pattern | Description |
|
||||
|---|---|
|
||||
| Random | Nodes are randomly placed about the canvas, but are not linked together. This can be used in conjunction with a WLAN node to quickly create a wireless network. |
|
||||
| Grid | Nodes are placed in horizontal rows starting in the upper-left corner, evenly spaced to the right; nodes are not linked to each other. |
|
||||
| Connected Grid | Nodes are placed in an N x M (width and height) rectangular grid, and each node is linked to the node above, below, left and right of itself. |
|
||||
| Chain | Nodes are linked together one after the other in a chain. |
|
||||
| Star | One node is placed in the center with N nodes surrounding it in a circular pattern, with each node linked to the center node. |
|
||||
| Cycle | Nodes are arranged in a circular pattern with every node connected to its neighbor to form a closed circular path. |
|
||||
| Wheel | The wheel pattern links nodes in a combination of both Star and Cycle patterns. |
|
||||
| Cube | Generate a cube graph of nodes. |
|
||||
| Clique | Creates a clique graph of nodes, where every node is connected to every other node. |
|
||||
| Bipartite | Creates a bipartite graph of nodes, having two disjoint sets of vertices. |
|
||||
| Pattern | Description |
|
||||
|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Random | Nodes are randomly placed about the canvas, but are not linked together. This can be used in conjunction with a WLAN node to quickly create a wireless network. |
|
||||
| Grid | Nodes are placed in horizontal rows starting in the upper-left corner, evenly spaced to the right; nodes are not linked to each other. |
|
||||
| Connected Grid | Nodes are placed in an N x M (width and height) rectangular grid, and each node is linked to the node above, below, left and right of itself. |
|
||||
| Chain | Nodes are linked together one after the other in a chain. |
|
||||
| Star | One node is placed in the center with N nodes surrounding it in a circular pattern, with each node linked to the center node. |
|
||||
| Cycle | Nodes are arranged in a circular pattern with every node connected to its neighbor to form a closed circular path. |
|
||||
| Wheel | The wheel pattern links nodes in a combination of both Star and Cycle patterns. |
|
||||
| Cube | Generate a cube graph of nodes. |
|
||||
| Clique | Creates a clique graph of nodes, where every node is connected to every other node. |
|
||||
| Bipartite | Creates a bipartite graph of nodes, having two disjoint sets of vertices. |
|
||||
|
||||
### Widgets Menu
|
||||
|
||||
|
|
@ -306,36 +306,36 @@ The Session Menu has entries for starting, stopping, and managing sessions,
|
|||
in addition to global options such as node types, comments, hooks, servers,
|
||||
and options.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Start or Stop | This starts or stops the emulation, performing the same function as the green Start or red Stop button. |
|
||||
| Change sessions... | Invokes the CORE Sessions dialog box containing a list of active CORE sessions in the daemon. Basic session information such as name, node count, start time, and a thumbnail are displayed. This dialog allows connecting to different sessions, shutting them down, or starting a new session. |
|
||||
| Node types... | Invokes the CORE Node Types dialog, performing the same function as the Edit button on the Network-Layer Nodes toolbar. |
|
||||
| Comments... | Invokes the CORE Session Comments window where optional text comments may be specified. These comments are saved at the top of the configuration file, and can be useful for describing the topology or how to use the network. |
|
||||
| Hooks... | Invokes the CORE Session Hooks window where scripts may be configured for a particular session state. The session states are defined in the [table](#session-states) below. The top of the window has a list of configured hooks, and buttons on the bottom left allow adding, editing, and removing hook scripts. The new or edit button will open a hook script editing window. A hook script is a shell script invoked on the host (not within a virtual node). |
|
||||
| Reset node positions | If you have moved nodes around using the mouse or by using a mobility module, choosing this item will reset all nodes to their original position on the canvas. The node locations are remembered when you first press the Start button. |
|
||||
| Emulation servers... | Invokes the CORE emulation servers dialog for configuring. |
|
||||
| Change Sessions... | Invokes the Sessions dialog for switching between different running sessions. This dialog is presented during startup when one or more sessions are already running. |
|
||||
| Options... | Presents per-session options, such as the IPv4 prefix to be used, if any, for a control network the ability to preserve the session directory; and an on/off switch for SDT3D support. |
|
||||
| Option | Description |
|
||||
|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Start or Stop | This starts or stops the emulation, performing the same function as the green Start or red Stop button. |
|
||||
| Change sessions... | Invokes the CORE Sessions dialog box containing a list of active CORE sessions in the daemon. Basic session information such as name, node count, start time, and a thumbnail are displayed. This dialog allows connecting to different sessions, shutting them down, or starting a new session. |
|
||||
| Node types... | Invokes the CORE Node Types dialog, performing the same function as the Edit button on the Network-Layer Nodes toolbar. |
|
||||
| Comments... | Invokes the CORE Session Comments window where optional text comments may be specified. These comments are saved at the top of the configuration file, and can be useful for describing the topology or how to use the network. |
|
||||
| Hooks... | Invokes the CORE Session Hooks window where scripts may be configured for a particular session state. The session states are defined in the [table](#session-states) below. The top of the window has a list of configured hooks, and buttons on the bottom left allow adding, editing, and removing hook scripts. The new or edit button will open a hook script editing window. A hook script is a shell script invoked on the host (not within a virtual node). |
|
||||
| Reset node positions | If you have moved nodes around using the mouse or by using a mobility module, choosing this item will reset all nodes to their original position on the canvas. The node locations are remembered when you first press the Start button. |
|
||||
| Emulation servers... | Invokes the CORE emulation servers dialog for configuring. |
|
||||
| Change Sessions... | Invokes the Sessions dialog for switching between different running sessions. This dialog is presented during startup when one or more sessions are already running. |
|
||||
| Options... | Presents per-session options, such as the IPv4 prefix to be used, if any, for a control network the ability to preserve the session directory; and an on/off switch for SDT3D support. |
|
||||
|
||||
#### Session States
|
||||
|
||||
| State | Description |
|
||||
|---|---|
|
||||
| definition | Used by the GUI to tell the backend to clear any state. |
|
||||
| configuration | When the user presses the *Start* button, node, link, and other configuration data is sent to the backend. This state is also reached when the user customizes a service. |
|
||||
| instantiation | After configuration data has been sent, just before the nodes are created. |
|
||||
| runtime | All nodes and networks have been built and are running. (This is the same state at which the previously-named *global experiment script* was run.)
|
||||
| datacollect | The user has pressed the *Stop* button, but before services have been stopped and nodes have been shut down. This is a good time to collect log files and other data from the nodes. |
|
||||
| shutdown | All nodes and networks have been shut down and destroyed. |
|
||||
| State | Description |
|
||||
|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| definition | Used by the GUI to tell the backend to clear any state. |
|
||||
| configuration | When the user presses the *Start* button, node, link, and other configuration data is sent to the backend. This state is also reached when the user customizes a service. |
|
||||
| instantiation | After configuration data has been sent, just before the nodes are created. |
|
||||
| runtime | All nodes and networks have been built and are running. (This is the same state at which the previously-named *global experiment script* was run.) |
|
||||
| datacollect | The user has pressed the *Stop* button, but before services have been stopped and nodes have been shut down. This is a good time to collect log files and other data from the nodes. |
|
||||
| shutdown | All nodes and networks have been shut down and destroyed. |
|
||||
|
||||
### Help Menu
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| CORE Github (www) | Link to the CORE GitHub page. |
|
||||
| CORE Documentation (www) | Lnk to the CORE Documentation page. |
|
||||
| About | Invokes the About dialog box for viewing version information. |
|
||||
| Option | Description |
|
||||
|--------------------------|---------------------------------------------------------------|
|
||||
| CORE Github (www) | Link to the CORE GitHub page. |
|
||||
| CORE Documentation (www) | Lnk to the CORE Documentation page. |
|
||||
| About | Invokes the About dialog box for viewing version information. |
|
||||
|
||||
## Connecting with Physical Networks
|
||||
|
||||
|
|
@ -542,10 +542,10 @@ complexity and CPU usage. The availability of certain plug-ins varies depending
|
|||
on platform. See the table below for a brief overview of wireless model types.
|
||||
|
||||
|
||||
|Model|Type|Supported Platform(s)|Fidelity|Description|
|
||||
|-----|----|---------------------|--------|-----------|
|
||||
|Basic|on/off|Linux|Low|Ethernet bridging with nftables|
|
||||
|EMANE|Plug-in|Linux|High|TAP device connected to EMANE emulator with pluggable MAC and PHY radio types|
|
||||
| Model | Type | Supported Platform(s) | Fidelity | Description |
|
||||
|-------|---------|-----------------------|----------|-------------------------------------------------------------------------------|
|
||||
| Basic | on/off | Linux | Low | Ethernet bridging with nftables |
|
||||
| EMANE | Plug-in | Linux | High | TAP device connected to EMANE emulator with pluggable MAC and PHY radio types |
|
||||
|
||||
To quickly build a wireless network, you can first place several router nodes
|
||||
onto the canvas. If you have the
|
||||
|
|
@ -581,11 +581,11 @@ See the [EMANE](emane.md) chapter for details on using EMANE.
|
|||
|
||||
CORE has a few ways to script mobility.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| ns-2 script | The script specifies either absolute positions or waypoints with a velocity. Locations are given with Cartesian coordinates. |
|
||||
| CORE API | An external entity can move nodes by sending CORE API Node messages with updated X,Y coordinates; the **coresendmsg** utility allows a shell script to generate these messages. |
|
||||
| EMANE events | See [EMANE](emane.md) for details on using EMANE scripts to move nodes around. Location information is typically given as latitude, longitude, and altitude. |
|
||||
| Option | Description |
|
||||
|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| ns-2 script | The script specifies either absolute positions or waypoints with a velocity. Locations are given with Cartesian coordinates. |
|
||||
| CORE API | An external entity can move nodes by sending CORE API Node messages with updated X,Y coordinates; the **coresendmsg** utility allows a shell script to generate these messages. |
|
||||
| EMANE events | See [EMANE](emane.md) for details on using EMANE scripts to move nodes around. Location information is typically given as latitude, longitude, and altitude. |
|
||||
|
||||
For the first method, you can create a mobility script using a text
|
||||
editor, or using a tool such as [BonnMotion](http://net.cs.uni-bonn.de/wg/cs/applications/bonnmotion/), and associate the script with one of the wireless
|
||||
|
|
|
|||
|
|
@ -18,22 +18,22 @@ networking scenarios, security studies, and increasing the size of physical test
|
|||
|
||||
## Topics
|
||||
|
||||
| Topic | Description|
|
||||
|-------|------------|
|
||||
|[Installation](install.md)|How to install CORE and its requirements|
|
||||
|[Architecture](architecture.md)|Overview of the architecture|
|
||||
|[Node Types](nodetypes.md)|Overview of node types supported within CORE|
|
||||
|[GUI](gui.md)|How to use the GUI|
|
||||
|[(BETA) Python GUI](pygui.md)|How to use the BETA python based GUI|
|
||||
|[Python API](python.md)|Covers how to control core directly using python|
|
||||
|[gRPC API](grpc.md)|Covers how control core using gRPC|
|
||||
|[Distributed](distributed.md)|Details for running CORE across multiple servers|
|
||||
|[Control Network](ctrlnet.md)|How to use control networks to communicate with nodes from host|
|
||||
|[Config Services](configservices.md)|Overview of provided config services and creating custom ones|
|
||||
|[Services](services.md)|Overview of provided services and creating custom ones|
|
||||
|[EMANE](emane.md)|Overview of EMANE integration and integrating custom EMANE models|
|
||||
|[Performance](performance.md)|Notes on performance when using CORE|
|
||||
|[Developers Guide](devguide.md)|Overview on how to contribute to CORE|
|
||||
| Topic | Description |
|
||||
|--------------------------------------|-------------------------------------------------------------------|
|
||||
| [Installation](install.md) | How to install CORE and its requirements |
|
||||
| [Architecture](architecture.md) | Overview of the architecture |
|
||||
| [Node Types](nodetypes.md) | Overview of node types supported within CORE |
|
||||
| [Python GUI](pygui.md) | How to use the default python based GUI |
|
||||
| [Legacy GUI (deprecated)](gui.md) | How to use the deprecated Tcl based GUI |
|
||||
| [Python API](python.md) | Covers how to control core directly using python |
|
||||
| [gRPC API](grpc.md) | Covers how control core using gRPC |
|
||||
| [Distributed](distributed.md) | Details for running CORE across multiple servers |
|
||||
| [Control Network](ctrlnet.md) | How to use control networks to communicate with nodes from host |
|
||||
| [Config Services](configservices.md) | Overview of provided config services and creating custom ones |
|
||||
| [Services](services.md) | Overview of provided services and creating custom ones |
|
||||
| [EMANE](emane.md) | Overview of EMANE integration and integrating custom EMANE models |
|
||||
| [Performance](performance.md) | Notes on performance when using CORE |
|
||||
| [Developers Guide](devguide.md) | Overview on how to contribute to CORE |
|
||||
|
||||
## Credits
|
||||
|
||||
|
|
|
|||
|
|
@ -37,12 +37,12 @@ sudo modprobe sch_netem
|
|||
### Tools Used
|
||||
The following tools will be leveraged during installation:
|
||||
|
||||
|Tool|Description|
|
||||
|---|---|
|
||||
|[pip](https://pip.pypa.io/en/stable/)|used to install pipx|
|
||||
|[pipx](https://pipxproject.github.io/pipx/)|used to install standalone python tools (invoke, poetry)|
|
||||
|[invoke](http://www.pyinvoke.org/)|used to run provided tasks (install, uninstall, reinstall, etc)|
|
||||
|[poetry](https://python-poetry.org/)|used to install python virtual environment or building a python wheel|
|
||||
| Tool | Description |
|
||||
|---------------------------------------------|-----------------------------------------------------------------------|
|
||||
| [pip](https://pip.pypa.io/en/stable/) | used to install pipx |
|
||||
| [pipx](https://pipxproject.github.io/pipx/) | used to install standalone python tools (invoke, poetry) |
|
||||
| [invoke](http://www.pyinvoke.org/) | used to run provided tasks (install, uninstall, reinstall, etc) |
|
||||
| [poetry](https://python-poetry.org/) | used to install python virtual environment or building a python wheel |
|
||||
|
||||
### Files
|
||||
The following is a list of files that would be installed after running the automated installation.
|
||||
|
|
@ -73,19 +73,19 @@ The following is a list of files that would be installed after running the autom
|
|||
### Installed Executables
|
||||
After the installation complete it will have installed the following scripts.
|
||||
|
||||
| Name | Description |
|
||||
|---|---|
|
||||
| core-cleanup | tool to help removed lingering core created containers, bridges, directories |
|
||||
| core-cli | tool to query, open xml files, and send commands using gRPC |
|
||||
| core-daemon | runs the backed core server providing TLV and gRPC APIs |
|
||||
| core-gui | runs the legacy tcl/tk based GUI |
|
||||
| core-imn-to-xml | tool to help automate converting a .imn file to .xml format |
|
||||
| core-manage | tool to add, remove, or check for services, models, and node types |
|
||||
| core-pygui | runs the new python/tk based GUI |
|
||||
| core-python | provides a convenience for running the core python virtual environment |
|
||||
| core-route-monitor | tool to help monitor traffic across nodes and feed that to SDT |
|
||||
| core-service-update | tool to update automate modifying a legacy service to match current naming |
|
||||
| coresendmsg | tool to send TLV API commands from command line |
|
||||
| Name | Description |
|
||||
|---------------------|------------------------------------------------------------------------------|
|
||||
| core-cleanup | tool to help removed lingering core created containers, bridges, directories |
|
||||
| core-cli | tool to query, open xml files, and send commands using gRPC |
|
||||
| core-daemon | runs the backed core server providing TLV and gRPC APIs |
|
||||
| core-gui | runs the legacy tcl/tk based GUI |
|
||||
| core-imn-to-xml | tool to help automate converting a .imn file to .xml format |
|
||||
| core-manage | tool to add, remove, or check for services, models, and node types |
|
||||
| core-pygui | runs the new python/tk based GUI |
|
||||
| core-python | provides a convenience for running the core python virtual environment |
|
||||
| core-route-monitor | tool to help monitor traffic across nodes and feed that to SDT |
|
||||
| core-service-update | tool to update automate modifying a legacy service to match current naming |
|
||||
| coresendmsg | tool to send TLV API commands from command line |
|
||||
|
||||
## Upgrading from Older Release
|
||||
Please make sure to uninstall any previous installations of CORE cleanly
|
||||
|
|
|
|||
|
|
@ -8,13 +8,13 @@
|
|||
The top question about the performance of CORE is often *how many nodes can it
|
||||
handle?* The answer depends on several factors:
|
||||
|
||||
| Factor | Performance Impact |
|
||||
|---|---|
|
||||
| Hardware | the number and speed of processors in the computer, the available processor cache, RAM memory, and front-side bus speed may greatly affect overall performance. |
|
||||
| Operating system version | distribution of Linux and the specific kernel versions used will affect overall performance. |
|
||||
| Active processes | all nodes share the same CPU resources, so if one or more nodes is performing a CPU-intensive task, overall performance will suffer. |
|
||||
| Network traffic | the more packets that are sent around the virtual network increases the amount of CPU usage. |
|
||||
| GUI usage | widgets that run periodically, mobility scenarios, and other GUI interactions generally consume CPU cycles that may be needed for emulation. |
|
||||
| Factor | Performance Impact |
|
||||
|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Hardware | the number and speed of processors in the computer, the available processor cache, RAM memory, and front-side bus speed may greatly affect overall performance. |
|
||||
| Operating system version | distribution of Linux and the specific kernel versions used will affect overall performance. |
|
||||
| Active processes | all nodes share the same CPU resources, so if one or more nodes is performing a CPU-intensive task, overall performance will suffer. |
|
||||
| Network traffic | the more packets that are sent around the virtual network increases the amount of CPU usage. |
|
||||
| GUI usage | widgets that run periodically, mobility scenarios, and other GUI interactions generally consume CPU cycles that may be needed for emulation. |
|
||||
|
||||
|
||||
On a typical single-CPU Xeon 3.0GHz server machine with 2GB RAM running Linux,
|
||||
|
|
|
|||
180
docs/pygui.md
180
docs/pygui.md
|
|
@ -114,45 +114,45 @@ the left side of the CORE window. Below are brief descriptions for each toolbar
|
|||
item, starting from the top. Most of the tools are grouped into related
|
||||
sub-menus, which appear when you click on their group icon.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Selection Tool | Tool for selecting, moving, configuring nodes. |
|
||||
|  | Start Button | Starts Execute mode, instantiates the emulation. |
|
||||
|  | Link | Allows network links to be drawn between two nodes by clicking and dragging the mouse. |
|
||||
| Icon | Name | Description |
|
||||
|------------------------------|----------------|----------------------------------------------------------------------------------------|
|
||||
|  | Selection Tool | Tool for selecting, moving, configuring nodes. |
|
||||
|  | Start Button | Starts Execute mode, instantiates the emulation. |
|
||||
|  | Link | Allows network links to be drawn between two nodes by clicking and dragging the mouse. |
|
||||
|
||||
### CORE Nodes
|
||||
|
||||
These nodes will create a new node container and run associated services.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Router | Runs Quagga OSPFv2 and OSPFv3 routing to forward packets. |
|
||||
|  | Host | Emulated server machine having a default route, runs SSH server. |
|
||||
|  | PC | Basic emulated machine having a default route, runs no processes by default. |
|
||||
|  | MDR | Runs Quagga OSPFv3 MDR routing for MANET-optimized routing. |
|
||||
|  | PRouter | Physical router represents a real testbed machine. |
|
||||
| Icon | Name | Description |
|
||||
|------------------------------|---------|------------------------------------------------------------------------------|
|
||||
|  | Router | Runs Quagga OSPFv2 and OSPFv3 routing to forward packets. |
|
||||
|  | Host | Emulated server machine having a default route, runs SSH server. |
|
||||
|  | PC | Basic emulated machine having a default route, runs no processes by default. |
|
||||
|  | MDR | Runs Quagga OSPFv3 MDR routing for MANET-optimized routing. |
|
||||
|  | PRouter | Physical router represents a real testbed machine. |
|
||||
|
||||
### Network Nodes
|
||||
|
||||
These nodes are mostly used to create a Linux bridge that serves the
|
||||
purpose described below.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Hub | Ethernet hub forwards incoming packets to every connected node. |
|
||||
|  | Switch | Ethernet switch intelligently forwards incoming packets to attached hosts using an Ethernet address hash table. |
|
||||
|  | Wireless LAN | When routers are connected to this WLAN node, they join a wireless network and an antenna is drawn instead of a connecting line; the WLAN node typically controls connectivity between attached wireless nodes based on the distance between them. |
|
||||
|  | RJ45 | RJ45 Physical Interface Tool, emulated nodes can be linked to real physical interfaces; using this tool, real networks and devices can be physically connected to the live-running emulation. |
|
||||
|  | Tunnel | Tool allows connecting together more than one CORE emulation using GRE tunnels. |
|
||||
| Icon | Name | Description |
|
||||
|---------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
|  | Hub | Ethernet hub forwards incoming packets to every connected node. |
|
||||
|  | Switch | Ethernet switch intelligently forwards incoming packets to attached hosts using an Ethernet address hash table. |
|
||||
|  | Wireless LAN | When routers are connected to this WLAN node, they join a wireless network and an antenna is drawn instead of a connecting line; the WLAN node typically controls connectivity between attached wireless nodes based on the distance between them. |
|
||||
|  | RJ45 | RJ45 Physical Interface Tool, emulated nodes can be linked to real physical interfaces; using this tool, real networks and devices can be physically connected to the live-running emulation. |
|
||||
|  | Tunnel | Tool allows connecting together more than one CORE emulation using GRE tunnels. |
|
||||
|
||||
### Annotation Tools
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Marker | For drawing marks on the canvas. |
|
||||
|  | Oval | For drawing circles on the canvas that appear in the background. |
|
||||
| Icon | Name | Description |
|
||||
|---------------------------------|-----------|---------------------------------------------------------------------|
|
||||
|  | Marker | For drawing marks on the canvas. |
|
||||
|  | Oval | For drawing circles on the canvas that appear in the background. |
|
||||
|  | Rectangle | For drawing rectangles on the canvas that appear in the background. |
|
||||
|  | Text | For placing text captions on the canvas. |
|
||||
|  | Text | For placing text captions on the canvas. |
|
||||
|
||||
### Execution Toolbar
|
||||
|
||||
|
|
@ -160,12 +160,12 @@ When the Start button is pressed, CORE switches to Execute mode, and the Edit
|
|||
toolbar on the left of the CORE window is replaced with the Execution toolbar
|
||||
Below are the items on this toolbar, starting from the top.
|
||||
|
||||
| Icon | Name | Description |
|
||||
|---|---|---|
|
||||
|  | Stop Button | Stops Execute mode, terminates the emulation, returns CORE to edit mode. |
|
||||
|  | Selection Tool | In Execute mode, the Selection Tool can be used for moving nodes around the canvas, and double-clicking on a node will open a shell window for that node; right-clicking on a node invokes a pop-up menu of run-time options for that node. |
|
||||
|  | Marker | For drawing freehand lines on the canvas, useful during demonstrations; markings are not saved. |
|
||||
|  | Run Tool | This tool allows easily running a command on all or a subset of all nodes. A list box allows selecting any of the nodes. A text entry box allows entering any command. The command should return immediately, otherwise the display will block awaiting response. The *ping* command, for example, with no parameters, is not a good idea. The result of each command is displayed in a results box. The first occurrence of the special text "NODE" will be replaced with the node name. The command will not be attempted to run on nodes that are not routers, PCs, or hosts, even if they are selected. |
|
||||
| Icon | Name | Description |
|
||||
|------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
|  | Stop Button | Stops Execute mode, terminates the emulation, returns CORE to edit mode. |
|
||||
|  | Selection Tool | In Execute mode, the Selection Tool can be used for moving nodes around the canvas, and double-clicking on a node will open a shell window for that node; right-clicking on a node invokes a pop-up menu of run-time options for that node. |
|
||||
|  | Marker | For drawing freehand lines on the canvas, useful during demonstrations; markings are not saved. |
|
||||
|  | Run Tool | This tool allows easily running a command on all or a subset of all nodes. A list box allows selecting any of the nodes. A text entry box allows entering any command. The command should return immediately, otherwise the display will block awaiting response. The *ping* command, for example, with no parameters, is not a good idea. The result of each command is displayed in a results box. The first occurrence of the special text "NODE" will be replaced with the node name. The command will not be attempted to run on nodes that are not routers, PCs, or hosts, even if they are selected. |
|
||||
|
||||
## Menu
|
||||
|
||||
|
|
@ -178,58 +178,58 @@ menu, by clicking the dashed line at the top.
|
|||
The File menu contains options for manipulating the **.imn** Configuration
|
||||
Files. Generally, these menu items should not be used in Execute mode.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| New Session | This starts a new session with an empty canvas. |
|
||||
| Save | Saves the current topology. If you have not yet specified a file name, the Save As dialog box is invoked. |
|
||||
| Save As | Invokes the Save As dialog box for selecting a new **.xml** file for saving the current configuration in the XML file. |
|
||||
| Open | Invokes the File Open dialog box for selecting a new XML file to open. |
|
||||
| Recently used files | Above the Quit menu command is a list of recently use files, if any have been opened. You can clear this list in the Preferences dialog box. You can specify the number of files to keep in this list from the Preferences dialog. Click on one of the file names listed to open that configuration file. |
|
||||
| Option | Description |
|
||||
|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| New Session | This starts a new session with an empty canvas. |
|
||||
| Save | Saves the current topology. If you have not yet specified a file name, the Save As dialog box is invoked. |
|
||||
| Save As | Invokes the Save As dialog box for selecting a new **.xml** file for saving the current configuration in the XML file. |
|
||||
| Open | Invokes the File Open dialog box for selecting a new XML file to open. |
|
||||
| Recently used files | Above the Quit menu command is a list of recently use files, if any have been opened. You can clear this list in the Preferences dialog box. You can specify the number of files to keep in this list from the Preferences dialog. Click on one of the file names listed to open that configuration file. |
|
||||
| Execute Python Script | Invokes a File Open dialog box for selecting a Python script to run and automatically connect to. After a selection is made, a Python Script Options dialog box is invoked to allow for command-line options to be added. The Python script must create a new CORE Session and add this session to the daemon's list of sessions in order for this to work. |
|
||||
| Quit | The Quit command should be used to exit the CORE GUI. CORE may prompt for termination if you are currently in Execute mode. Preferences and the recently-used files list are saved. |
|
||||
| Quit | The Quit command should be used to exit the CORE GUI. CORE may prompt for termination if you are currently in Execute mode. Preferences and the recently-used files list are saved. |
|
||||
|
||||
### Edit Menu
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Preferences | Invokes the Preferences dialog box. |
|
||||
| Custom Nodes | Custom node creation dialog box. |
|
||||
| Undo | (Disabled) Attempts to undo the last edit in edit mode. |
|
||||
| Redo | (Disabled) Attempts to redo an edit that has been undone. |
|
||||
| Cut, Copy, Paste, Delete | Used to cut, copy, paste, and delete a selection. When nodes are pasted, their node numbers are automatically incremented, and existing links are preserved with new IP addresses assigned. Services and their customizations are copied to the new node, but care should be taken as node IP addresses have changed with possibly old addresses remaining in any custom service configurations. Annotations may also be copied and pasted.
|
||||
| Option | Description |
|
||||
|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Preferences | Invokes the Preferences dialog box. |
|
||||
| Custom Nodes | Custom node creation dialog box. |
|
||||
| Undo | (Disabled) Attempts to undo the last edit in edit mode. |
|
||||
| Redo | (Disabled) Attempts to redo an edit that has been undone. |
|
||||
| Cut, Copy, Paste, Delete | Used to cut, copy, paste, and delete a selection. When nodes are pasted, their node numbers are automatically incremented, and existing links are preserved with new IP addresses assigned. Services and their customizations are copied to the new node, but care should be taken as node IP addresses have changed with possibly old addresses remaining in any custom service configurations. Annotations may also be copied and pasted. |
|
||||
|
||||
### Canvas Menu
|
||||
|
||||
The canvas menu provides commands related to the editing canvas.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Size/scale | Invokes a Canvas Size and Scale dialog that allows configuring the canvas size, scale, and geographic reference point. The size controls allow changing the width and height of the current canvas, in pixels or meters. The scale allows specifying how many meters are equivalent to 100 pixels. The reference point controls specify the latitude, longitude, and altitude reference point used to convert between geographic and Cartesian coordinate systems. By clicking the *Save as default* option, all new canvases will be created with these properties. The default canvas size can also be changed in the Preferences dialog box.
|
||||
| Wallpaper | Used for setting the canvas background image. |
|
||||
| Option | Description |
|
||||
|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Size/scale | Invokes a Canvas Size and Scale dialog that allows configuring the canvas size, scale, and geographic reference point. The size controls allow changing the width and height of the current canvas, in pixels or meters. The scale allows specifying how many meters are equivalent to 100 pixels. The reference point controls specify the latitude, longitude, and altitude reference point used to convert between geographic and Cartesian coordinate systems. By clicking the *Save as default* option, all new canvases will be created with these properties. The default canvas size can also be changed in the Preferences dialog box. |
|
||||
| Wallpaper | Used for setting the canvas background image. |
|
||||
|
||||
### View Menu
|
||||
|
||||
The View menu features items for toggling on and off their display on the canvas.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Option | Description |
|
||||
|-----------------|-----------------------------------|
|
||||
| Interface Names | Display interface names on links. |
|
||||
| IPv4 Addresses | Display IPv4 addresses on links. |
|
||||
| IPv6 Addresses | Display IPv6 addresses on links. |
|
||||
| Node Labels | Display node names. |
|
||||
| Link Labels | Display link labels. |
|
||||
| Annotations | Display annotations. |
|
||||
| Canvas Grid | Display the canvas grid. |
|
||||
| IPv4 Addresses | Display IPv4 addresses on links. |
|
||||
| IPv6 Addresses | Display IPv6 addresses on links. |
|
||||
| Node Labels | Display node names. |
|
||||
| Link Labels | Display link labels. |
|
||||
| Annotations | Display annotations. |
|
||||
| Canvas Grid | Display the canvas grid. |
|
||||
|
||||
### Tools Menu
|
||||
|
||||
The tools menu lists different utility functions.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Find | Display find dialog used for highlighting a node on the canvas. |
|
||||
| Auto Grid | Automatically layout nodes in a grid. |
|
||||
| IP addresses | Invokes the IP Addresses dialog box for configuring which IPv4/IPv6 prefixes are used when automatically addressing new interfaces. |
|
||||
| Option | Description |
|
||||
|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Find | Display find dialog used for highlighting a node on the canvas. |
|
||||
| Auto Grid | Automatically layout nodes in a grid. |
|
||||
| IP addresses | Invokes the IP Addresses dialog box for configuring which IPv4/IPv6 prefixes are used when automatically addressing new interfaces. |
|
||||
| MAC addresses | Invokes the MAC Addresses dialog box for configuring the starting number used as the lowest byte when generating each interface MAC address. This value should be changed when tunneling between CORE emulations to prevent MAC address conflicts. |
|
||||
|
||||
### Widgets Menu
|
||||
|
|
@ -288,31 +288,31 @@ The Session Menu has entries for starting, stopping, and managing sessions,
|
|||
in addition to global options such as node types, comments, hooks, servers,
|
||||
and options.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| Sessions | Invokes the CORE Sessions dialog box containing a list of active CORE sessions in the daemon. Basic session information such as name, node count, start time, and a thumbnail are displayed. This dialog allows connecting to different sessions, shutting them down, or starting a new session. |
|
||||
| Servers | Invokes the CORE emulation servers dialog for configuring. |
|
||||
| Options | Presents per-session options, such as the IPv4 prefix to be used, if any, for a control network the ability to preserve the session directory; and an on/off switch for SDT3D support. |
|
||||
| Hooks | Invokes the CORE Session Hooks window where scripts may be configured for a particular session state. The session states are defined in the [table](#session-states) below. The top of the window has a list of configured hooks, and buttons on the bottom left allow adding, editing, and removing hook scripts. The new or edit button will open a hook script editing window. A hook script is a shell script invoked on the host (not within a virtual node). |
|
||||
| Option | Description |
|
||||
|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Sessions | Invokes the CORE Sessions dialog box containing a list of active CORE sessions in the daemon. Basic session information such as name, node count, start time, and a thumbnail are displayed. This dialog allows connecting to different sessions, shutting them down, or starting a new session. |
|
||||
| Servers | Invokes the CORE emulation servers dialog for configuring. |
|
||||
| Options | Presents per-session options, such as the IPv4 prefix to be used, if any, for a control network the ability to preserve the session directory; and an on/off switch for SDT3D support. |
|
||||
| Hooks | Invokes the CORE Session Hooks window where scripts may be configured for a particular session state. The session states are defined in the [table](#session-states) below. The top of the window has a list of configured hooks, and buttons on the bottom left allow adding, editing, and removing hook scripts. The new or edit button will open a hook script editing window. A hook script is a shell script invoked on the host (not within a virtual node). |
|
||||
|
||||
#### Session States
|
||||
|
||||
| State | Description |
|
||||
|---|---|
|
||||
| Definition | Used by the GUI to tell the backend to clear any state. |
|
||||
| Configuration | When the user presses the *Start* button, node, link, and other configuration data is sent to the backend. This state is also reached when the user customizes a service. |
|
||||
| Instantiation | After configuration data has been sent, just before the nodes are created. |
|
||||
| Runtime | All nodes and networks have been built and are running. (This is the same state at which the previously-named *global experiment script* was run.)
|
||||
| Datacollect | The user has pressed the *Stop* button, but before services have been stopped and nodes have been shut down. This is a good time to collect log files and other data from the nodes. |
|
||||
| Shutdown | All nodes and networks have been shut down and destroyed. |
|
||||
| State | Description |
|
||||
|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Definition | Used by the GUI to tell the backend to clear any state. |
|
||||
| Configuration | When the user presses the *Start* button, node, link, and other configuration data is sent to the backend. This state is also reached when the user customizes a service. |
|
||||
| Instantiation | After configuration data has been sent, just before the nodes are created. |
|
||||
| Runtime | All nodes and networks have been built and are running. (This is the same state at which the previously-named *global experiment script* was run.) |
|
||||
| Datacollect | The user has pressed the *Stop* button, but before services have been stopped and nodes have been shut down. This is a good time to collect log files and other data from the nodes. |
|
||||
| Shutdown | All nodes and networks have been shut down and destroyed. |
|
||||
|
||||
### Help Menu
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| CORE Github (www) | Link to the CORE GitHub page. |
|
||||
| CORE Documentation (www) | Lnk to the CORE Documentation page. |
|
||||
| About | Invokes the About dialog box for viewing version information. |
|
||||
| Option | Description |
|
||||
|--------------------------|---------------------------------------------------------------|
|
||||
| CORE Github (www) | Link to the CORE GitHub page. |
|
||||
| CORE Documentation (www) | Lnk to the CORE Documentation page. |
|
||||
| About | Invokes the About dialog box for viewing version information. |
|
||||
|
||||
## Connecting with Physical Networks
|
||||
|
||||
|
|
@ -519,10 +519,10 @@ complexity and CPU usage. The availability of certain plug-ins varies depending
|
|||
on platform. See the table below for a brief overview of wireless model types.
|
||||
|
||||
|
||||
|Model|Type|Supported Platform(s)|Fidelity|Description|
|
||||
|-----|----|---------------------|--------|-----------|
|
||||
|Basic|on/off|Linux|Low|Ethernet bridging with nftables|
|
||||
|EMANE|Plug-in|Linux|High|TAP device connected to EMANE emulator with pluggable MAC and PHY radio types|
|
||||
| Model | Type | Supported Platform(s) | Fidelity | Description |
|
||||
|-------|---------|-----------------------|----------|-------------------------------------------------------------------------------|
|
||||
| Basic | on/off | Linux | Low | Ethernet bridging with nftables |
|
||||
| EMANE | Plug-in | Linux | High | TAP device connected to EMANE emulator with pluggable MAC and PHY radio types |
|
||||
|
||||
To quickly build a wireless network, you can first place several router nodes
|
||||
onto the canvas. If you have the
|
||||
|
|
@ -556,11 +556,11 @@ See the [EMANE](emane.md) chapter for details on using EMANE.
|
|||
|
||||
CORE has a few ways to script mobility.
|
||||
|
||||
| Option | Description |
|
||||
|---|---|
|
||||
| ns-2 script | The script specifies either absolute positions or waypoints with a velocity. Locations are given with Cartesian coordinates. |
|
||||
| CORE API | An external entity can move nodes by sending CORE API Node messages with updated X,Y coordinates; the **coresendmsg** utility allows a shell script to generate these messages. |
|
||||
| EMANE events | See [EMANE](emane.md) for details on using EMANE scripts to move nodes around. Location information is typically given as latitude, longitude, and altitude. |
|
||||
| Option | Description |
|
||||
|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| ns-2 script | The script specifies either absolute positions or waypoints with a velocity. Locations are given with Cartesian coordinates. |
|
||||
| CORE API | An external entity can move nodes by sending CORE API Node messages with updated X,Y coordinates; the **coresendmsg** utility allows a shell script to generate these messages. |
|
||||
| EMANE events | See [EMANE](emane.md) for details on using EMANE scripts to move nodes around. Location information is typically given as latitude, longitude, and altitude. |
|
||||
|
||||
For the first method, you can create a mobility script using a text
|
||||
editor, or using a tool such as [BonnMotion](http://net.cs.uni-bonn.de/wg/cs/applications/bonnmotion/), and associate the script with one of the wireless
|
||||
|
|
|
|||
|
|
@ -21,28 +21,28 @@ shutdown commands, and meta-data associated with a node.
|
|||
|
||||
## Available Services
|
||||
|
||||
| Service Group | Services |
|
||||
|---|---|
|
||||
|[BIRD](services/bird.md)|BGP, OSPF, RADV, RIP, Static|
|
||||
|[EMANE](services/emane.md)|Transport Service|
|
||||
|[FRR](services/frr.md)|BABEL, BGP, OSPFv2, OSPFv3, PIMD, RIP, RIPNG, Zebra|
|
||||
|[NRL](services/nrl.md)|arouted, MGEN Sink, MGEN Actor, NHDP, OLSR, OLSRORG, OLSRv2, SMF|
|
||||
|[Quagga](services/quagga.md)|BABEL, BGP, OSPFv2, OSPFv3, OSPFv3 MDR, RIP, RIPNG, XPIMD, Zebra|
|
||||
|[SDN](services/sdn.md)|OVS, RYU|
|
||||
|[Security](services/security.md)|Firewall, IPsec, NAT, VPN Client, VPN Server|
|
||||
|[Utility](services/utility.md)|ATD, Routing Utils, DHCP, FTP, IP Forward, PCAP, RADVD, SSF, UCARP|
|
||||
|[XORP](services/xorp.md)|BGP, OLSR, OSPFv2, OSPFv3, PIMSM4, PIMSM6, RIP, RIPNG, Router Manager|
|
||||
| Service Group | Services |
|
||||
|----------------------------------|-----------------------------------------------------------------------|
|
||||
| [BIRD](services/bird.md) | BGP, OSPF, RADV, RIP, Static |
|
||||
| [EMANE](services/emane.md) | Transport Service |
|
||||
| [FRR](services/frr.md) | BABEL, BGP, OSPFv2, OSPFv3, PIMD, RIP, RIPNG, Zebra |
|
||||
| [NRL](services/nrl.md) | arouted, MGEN Sink, MGEN Actor, NHDP, OLSR, OLSRORG, OLSRv2, SMF |
|
||||
| [Quagga](services/quagga.md) | BABEL, BGP, OSPFv2, OSPFv3, OSPFv3 MDR, RIP, RIPNG, XPIMD, Zebra |
|
||||
| [SDN](services/sdn.md) | OVS, RYU |
|
||||
| [Security](services/security.md) | Firewall, IPsec, NAT, VPN Client, VPN Server |
|
||||
| [Utility](services/utility.md) | ATD, Routing Utils, DHCP, FTP, IP Forward, PCAP, RADVD, SSF, UCARP |
|
||||
| [XORP](services/xorp.md) | BGP, OLSR, OSPFv2, OSPFv3, PIMSM4, PIMSM6, RIP, RIPNG, Router Manager |
|
||||
|
||||
## Node Types and Default Services
|
||||
|
||||
Here are the default node types and their services:
|
||||
|
||||
| Node Type | Services |
|
||||
|---|---|
|
||||
| *router* | zebra, OSFPv2, OSPFv3, and IPForward services for IGP link-state routing. |
|
||||
| *host* | DefaultRoute and SSH services, representing an SSH server having a default route when connected directly to a router. |
|
||||
| *PC* | DefaultRoute service for having a default route when connected directly to a router. |
|
||||
| *mdr* | zebra, OSPFv3MDR, and IPForward services for wireless-optimized MANET Designated Router routing. |
|
||||
| Node Type | Services |
|
||||
|-----------|--------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| *router* | zebra, OSFPv2, OSPFv3, and IPForward services for IGP link-state routing. |
|
||||
| *host* | DefaultRoute and SSH services, representing an SSH server having a default route when connected directly to a router. |
|
||||
| *PC* | DefaultRoute service for having a default route when connected directly to a router. |
|
||||
| *mdr* | zebra, OSPFv3MDR, and IPForward services for wireless-optimized MANET Designated Router routing. |
|
||||
| *prouter* | a physical router, having the same default services as the *router* node type; for incorporating Linux testbed machines into an emulation. |
|
||||
|
||||
Configuration files can be automatically generated by each service. For
|
||||
|
|
|
|||
Loading…
Reference in a new issue