view_statmux_messages_ssh
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| view_statmux_messages_ssh [2024/04/24 17:02] – walkeradmin | view_statmux_messages_ssh [2024/04/24 17:05] – walkeradmin | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ---- | ---- | ||
| - | When using | + | StatMux messages originate from the Multiplexer and are received by the Encoding Live. Even though the Encoder may be started, it will not output anything when in a StatMux group if it does not receive any StatMux messaging. |
| - | + | \\ | |
| - | + | \\ | |
| - | + | Remember, for this to work the Encoder and Mux have to be started, and the StatMux group has to be set in both the Multiplexer and the Encoder. | |
| - | + | \\ | |
| - | + | \\ | |
| - | < | + | In this example I am looking at eno3 on Encoder, this is because in this example the StatMux messages are going across the Data Network. |
| + | \\ | ||
| + | \\ | ||
| + | We can use the following to see the StatMux messages: | ||
| + | \\ | ||
| + | \\ | ||
| tcpdump -i eno3 -nn port 15778 | tcpdump -i eno3 -nn port 15778 | ||
| - | + | \\ | |
| + | < | ||
| tcpdump: verbose output suppressed, use -v or -vv for full protocol decode | tcpdump: verbose output suppressed, use -v or -vv for full protocol decode | ||
| listening on eno3, link-type EN10MB (Ethernet), capture size 262144 bytes | listening on eno3, link-type EN10MB (Ethernet), capture size 262144 bytes | ||
view_statmux_messages_ssh.txt · Last modified: 2024/04/24 17:08 by walkeradmin