We have collected the most relevant information on Pulseaudio Port Forwarding. Open the URLs, which are collected below, and you will find all the info you are interested in.
networking - How to carry audio over SSH ... - Ask Ubuntu
https://askubuntu.com/questions/371687/how-to-carry-audio-over-ssh#:~:text=The%20slightly%20more%20complicated%20way%3A%20Enable%20network%20access,port%20%28usually%204713%29%2C%20connect%20with%20ssh%20-R%2024713%3Alocalhost%3A4713
PulseAudio sound forwarding across a network – Joshua ...
https://joshdata.wordpress.com/2009/02/11/pulseaudio-sound-forwarding-across-a-network/
One could configure PulseAudio to use a TCP port instead, but then you have to worry about security. So instead, use the socat tool (you might need to install the socat package) on the remote machine to forward the remote machine’s local port 4000 to its PulseAudio Unix socket: (on the computer with the speakers, e.g. inside the SSH session)
PulseAudio - OpenWrt Wiki
https://openwrt.org/docs/guide-user/hardware/audio/pulseaudio
The first step is to forward a tcp port to the router using ssh. In this example we've decided to use port 4000. ssh-f-N-L4000:localhost: 4000 root @ openwrt. Option -f puts the ssh session the background, because we don't need to actively work with the session anyways.
pulseaudio - How do I forward sound from one computer …
https://askubuntu.com/questions/70556/how-do-i-forward-sound-from-one-computer-to-another-over-the-lan
The below example shows how to create a pulseaudio TCP tunnel to forward sound from computer alpha to computer beta. In my case, both computers are running Ubuntu 14.04. On alpha (the source computer) append the following lines to /etc/pulse/default.pa:.fail load-module module-tunnel-sink sink_name=beta server=tcp:IP_ADDRESS_OF_BETA:4713 .nofail
Running PulseAudio in system mode with TCP listening on ...
https://blog.dhampir.no/content/running-pulseaudio-in-system-mode-with-tcp-listening-on-debian-wheezy
Now set up SSH port forwarding for port 1500, or whichever port you used above, with something like autossh and public key logins, and you’ve got remote sound playing over an encrypted tunnel. Neat. Remember to set the default-server for client computers as well.
Redirect Linux sound to DLNA receivers using PulseAudio ...
https://www.ubuntu-user.com/Magazine/Archive/2015/27/Redirect-Linux-sound-to-DLNA-receivers-using-PulseAudio
Forwarding Sound. For a first test, open any application that plays sound and switch to PulseAudio volume control. Select the corresponding program in the Playback tab and, from the drop-down menu, choose the device to which you want PulseAudio DLNA to forward the sound . The sound will come from the corresponding device a few seconds later – you do not need to …
fedora - Change default port for PulseAudio (line out, not ...
https://unix.stackexchange.com/questions/175930/change-default-port-for-pulseaudio-line-out-not-headphones
Use pavucontrol to change the port to your desired one. Then find the internal name of the port with this command: $ pacmd list | grep "active port" active port: <hdmi-output-0> active port: <analog-output-lineout> active port: <analog-input-linein>
networking - How to carry audio over SSH ... - Ask Ubuntu
https://askubuntu.com/questions/371687/how-to-carry-audio-over-ssh
The slightly more complicated way: Enable network access as above, but tunnel PulseAudio over SSH TCP forwarding. Use pax11publish to discover your PulseAudio port (usually 4713), connect with. ssh -R 24713:localhost:4713 then run. export PULSE_SERVER="tcp:localhost:24713"
vlc - Pulseaudio to output RTP to internet - Stack Overflow
https://stackoverflow.com/questions/14452675/pulseaudio-to-output-rtp-to-internet
I want pulseaudio (remote instance) to push audio sent to the primary alsa device straight to RTP over the internet so that I could listen to it on VLC on my home computer. in my /etc/pulse/default.pa. load-module module-rtp-send source=alsa_output.0.analog-stereo.monitor destination=x.x.x.x port=8080 loop=1.
How do I get send audio from Raspbian over a network ...
https://raspberrypi.stackexchange.com/questions/108346/how-do-i-get-send-audio-from-raspbian-over-a-network
Have you also considered trying PulseAudio over TCP but using SSH port forwarding, so that you don't have to get your IT admins to open PulseAudio-specific ports? (Although the students would need to be able to connect to the Pi via SSH so there's a need for one open port at least).
Now you know Pulseaudio Port Forwarding
Now that you know Pulseaudio Port Forwarding, we suggest that you familiarize yourself with information on similar questions.
