view_statmux_messages_ssh
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
view_statmux_messages_ssh [2024/04/24 17:01] – created walkeradmin | view_statmux_messages_ssh [2024/04/24 17:08] (current) – walkeradmin | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== View StatMux Messages SSH ====== | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
- | + | ---- | |
- | + | 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. | |
- | + | \\ | |
- | tcpdump -i eno3 -nn port 15778 | + | \\ |
- | dropped privs to tcpdump | + | 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: 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 | ||
Line 24: | Line 35: | ||
15: | 15: | ||
15: | 15: | ||
+ | </ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | ---- |
view_statmux_messages_ssh.1713974470.txt.gz · Last modified: 2024/04/24 17:01 by walkeradmin