![pulseaudio ssh pulseaudio ssh](https://linux-blog.anracom.com/wp-content/uploads/2021/04/ssh_data_transfer_LO_draw_directSSH.png)
They will use a direct (unencrypted) connection for audio streaming. Other computers, with the option "Make discoverable network devices available locally" enabled (module-zeroconf-discover), will automatically list outputs (sinks) that your computer exports. This will load "module-zeroconf-publish". If you have avahi-daemon and pulseaudio-zeroconf installed, you can activate "Allow other machines to discover local devices". Use automatic direct connection with DNS-SD discovery They will try to establish a direct (non-SSH, unencrypted) connection to your computer for audio streaming.
![pulseaudio ssh pulseaudio ssh](http://www.ubuntugeek.com/wp-content/uploads/2010/03/Screenshot-Hardwaremap.png)
Whenever you SSH with X11 forwarding enabled, PulseAudio programs use X11 to discover your sound server (use pax11publish or xprop -root PULSE_SERVER to see for yourself). Use automatic direct connection with X11-based discovery
![pulseaudio ssh pulseaudio ssh](https://i.ytimg.com/vi/IpZJdFnKjD8/maxresdefault.jpg)
Copy your authentication cookie (~/.config/pulse/cookie) to that computer.Connect to another computer with ssh -R 24713:localhost:4713 (the remote port '24713' was chosen arbitrarily).Use pax11publish to discover your PulseAudio listener port (usually 4713).Manually forward the TCP connection over SSH You can now access the PulseAudio server in several ways: pulseaudio does not need to be restarted, and no configuration has to be done on host or in image either. This will load "module-native-protocol-tcp" in PulseAudio. Assuming pulseaudio is installed on host and in image, one can provide pulseaudio sound over tcp with only a few steps. First, run paprefs, go to Network Server and check Enable network access to local sound devices.