File: Overlay/Overlay.ned
(no description)
The following diagram shows usage relationships between modules, networks and channels. Unresolved module (and channel) types are missing from the diagram. Click here to see the full picture.
If a module type shows up more than once, that means it has been defined in more than one NED file.
SingleHost | simulates a single host to connect it to a real network |
OverlayHost | Host that participates in the overlay |
OverlayRouter | Router in the overlay network |
OverlayAccessRouter | Access router that participates in the overlay |
SimpleMultiOverlayHost | Host in the simple network that participates in the overlay |
SimpleOverlayHost | Host in the simple network that participates in the overlay |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
from_app | input | gate from the application |
to_udp | output | gate to the UDP layer |
to_app | output | gate to the application connections nocheck: from_udp --> overlay.from_udp++; to_udp <-- overlay.to_udp++; from_app --> chord.from_app; to_app <-- chord.to_app; |
Name | Type | Description |
---|
module Overlay gates: in: from_udp; // gate from the UDP layer // in: from_tcp; // gate from the TCP layer in: from_app; // gate from the application out: to_udp; // gate to the UDP layer // out: to_tcp; // gate to the TCP layer out: to_app; // gate to the application // connections nocheck: // from_udp --> overlay.from_udp++; // to_udp <-- overlay.to_udp++; // from_app --> chord.from_app; // to_app <-- chord.to_app; endmodule