Socket PDU: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(add note for 3.10) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
For server modes, leave Host blank to bind to all interfaces (equivalent to 0.0.0.0). | For server modes, leave Host blank to bind to all interfaces (equivalent to 0.0.0.0). | ||
<b>Note for 3.10</b> This block has been moved from gr-blocks to gr-network, which causes a name change of the id. See [[Porting_Existing_Flowgraphs_to_a_Newer_Version]] for details. | |||
== Parameters == | == Parameters == | ||
Latest revision as of 14:52, 27 January 2022
Creates socket interface and translates traffic to PDUs.
For server modes, leave Host blank to bind to all interfaces (equivalent to 0.0.0.0).
Note for 3.10 This block has been moved from gr-blocks to gr-network, which causes a name change of the id. See Porting_Existing_Flowgraphs_to_a_Newer_Version for details.
Parameters
- Type
- Socket type (TCP/UDP, Client/Server)
- Host
- Network address to use
- Port
- Network port to use
- MTU
- Maximum transmission unit
- TCP No delay
- TCP No Delay option (set to True to disable Nagle algorithm)
Example Flowgraph
Insert description of flowgraph here, then show a screenshot of the flowgraph and the output if there is an interesting GUI. Currently we have no standard method of uploading the actual flowgraph to the wiki or git repo, unfortunately. The plan is to have an example flowgraph showing how the block might be used, for every block, and the flowgraphs will live in the git repo.
Source Files
- C++ files
- [1]
- Header files
- [2]
- Public header files
- [3]
- Block definition
- [4]