Server side of the EtherCli model -- generates EtherAppResp packets with the number of bytes requested by the client in EtherAppReq. It should be connected directly to EtherLLC or a Ieee802NicXXX module.
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram. Click here to see the full picture.
The following diagram shows inheritance relationships for this type. Unresolved 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.
EtherHost (compound module) |
An example host with one Ethernet port and traffic generators that generate Ethernet traffic directly. This host model does not contain higher layer protocols (IP, TCP). |
EtherHost2 (compound module) |
Example host model with one Ethernet port and several traffic generators to create traffic in the test network. |
Name | Type | Default value | Description |
---|---|---|---|
registerSAP | bool |
whether to sent IEEE802CTRL_REGISTER_DSAP on startup |
Name | Value | Description |
---|---|---|
display | i=block/app |
Name | Direction | Size | Description |
---|---|---|---|
in | input | ||
out | output |
// // Server side of the EtherCli model -- generates EtherAppResp packets // with the number of bytes requested by the client in EtherAppReq. // It should be connected directly to EtherLLC or a Ieee802NicXXX module. // simple EtherAppSrv { parameters: bool registerSAP; // whether to sent IEEE802CTRL_REGISTER_DSAP on startup @display("i=block/app"); gates: input in @labels(Ieee802Ctrl/up); output out @labels(Ieee802Ctrl/down); }