The second one connects it's standard I/O ("-" is a synonym for "STDIO") to UDP, connecting out to port 11111 of localhost. So this is a UDP server listening on port 11111. The first command is the server because it connects its standard I/O to the UDP-LISTEN: (UDP-L for short) address. Recall from the previous article that socat's command-line structure requires two addresses. But first a quick reminder of one way socat does UDP. We'll abandon the comparisons to netcat, as we've exceeded what netcat can do. It turns out there are a lot of subleties when dealing with UDP, even before multicast is mixed in. After this article will be one more that discusses advanced socat features. This article picks up where the last one left off, with respect to UDP. It skimped on socat's UDP-related features, because netcat only implements a subset of them. The last article teaches how to use socat by comparing it first to cat then to netcat.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |