Difference between revisions of "PulseAudio and Firewalls"
Jump to navigation
Jump to search
(Created page with "Really PA? Port 9875? Why!? If you're reading this, just know that to get PulseAudio RTP working through a firewall; * the RTP Server should EXPLICITLY define a port to send to: port=WXYZ * And the following ports should be open on the client side; ** WXYZ (IE, what was explicitly defined on the PA server) ** 9875 (this port too, not documented at all, except for in regards to PipeWire, and deeply ironic given that it is on the PulseAudio website: https://pipewire.pa...") |
m |
||
| Line 3: | Line 3: | ||
If you're reading this, just know that to get PulseAudio RTP working through a firewall; | If you're reading this, just know that to get PulseAudio RTP working through a firewall; | ||
* the RTP Server should EXPLICITLY define a port to send to: port=WXYZ | *the RTP Server should EXPLICITLY define a port to send to: port=WXYZ | ||
* And the following ports should be open on the client side; | *And the following ports should be open on the client side; | ||
** WXYZ (IE, what was explicitly defined on the PA server) | **WXYZ (IE, what was explicitly defined on the PA server) | ||
** 9875 (this port too, not documented at all, except for in regards to PipeWire, and deeply ironic given that it is on the PulseAudio website: https://pipewire.pages.freedesktop.org/pipewire/page_module_rtp_sap.html, and even more deeply warped that PulseAudio has no facility for defining the "SAP Port", and really, really, really messed up especially considering that when destination_ip= is explicitly defined, SAP is / should be disabled!) | **9875 (this port too, not documented at all, except for in regards to PipeWire, and deeply ironic given that it is on the PulseAudio website: https://pipewire.pages.freedesktop.org/pipewire/page_module_rtp_sap.html, and even more deeply warped that PulseAudio has no facility for defining the "SAP Port", and really, really, really messed up especially considering that when destination_ip= is explicitly defined, SAP is / should be disabled!) | ||
This is a serious deficiency in PulseAudio. TCPDUMP it and find out for yourself. | This is a serious deficiency in PulseAudio. TCPDUMP it and find out for yourself how retarded the PulseAudio developers are for doing this and NOT documenting it (yup, very pissed about it). | ||
Revision as of 19:04, 7 January 2025
Really PA? Port 9875? Why!?
If you're reading this, just know that to get PulseAudio RTP working through a firewall;
- the RTP Server should EXPLICITLY define a port to send to: port=WXYZ
- And the following ports should be open on the client side;
- WXYZ (IE, what was explicitly defined on the PA server)
- 9875 (this port too, not documented at all, except for in regards to PipeWire, and deeply ironic given that it is on the PulseAudio website: https://pipewire.pages.freedesktop.org/pipewire/page_module_rtp_sap.html, and even more deeply warped that PulseAudio has no facility for defining the "SAP Port", and really, really, really messed up especially considering that when destination_ip= is explicitly defined, SAP is / should be disabled!)
This is a serious deficiency in PulseAudio. TCPDUMP it and find out for yourself how retarded the PulseAudio developers are for doing this and NOT documenting it (yup, very pissed about it).