How do I forward sound from one computer to another over the Lan?

I have two computers. Computer A is running Ubuntu 11.10 with Gnome Clasic. Computer B is running Mythbuntu 11.10. Computer B has a sweet digital audio sound system.

I want to play music from Banshee on Computer A, but have the sound output sent over the LAN and come out on computer B’s speakers.

I found this question which indicated I should use something called “paprefs” to acheive this. So, I installed paprefs and then in the “Network Server” dialog, I selected these settings:


And then… I have no idea what is supposed to happen. I checked the paprefs home page, and all they say under Documentation is “There is not much to say. Just run paprefs and see for yourself.”

I don’t see anything happening or any way I’m supposed to make the connection from Computer A to Computer B.

How is this supposed to work? Can someone provide clear instructions on what one does to actually make the connection?

Ideally, the hope is that I can have a set up that allows me to always play certain applications, like Banshee, over the LAN using Computer B’s sound system. In other words, once set up, it is the default, and does not have to be manually reconnected every time.

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 1

The least complicated method to send audio from one Pulse Audio server to another over the LAN is to use the RTP/Multicast feature that you are able to set up using paprefs How do I forward sound from one computer to another over the Lan?.

On the sender:

How do I forward sound from one computer to another over the Lan?

Choose your local soundcard or choose a separate device you can select as audio output from Audio Preferences.

On the receiver:

How do I forward sound from one computer to another over the Lan?

By doing so audio will be sent from the sender to the receiver via your LAN.

Solution 2

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/

load-module  module-tunnel-sink  sink_name=beta  server=tcp:IP_ADDRESS_OF_BETA:4713

(Choose any unique value for sink_name. I arbitrarily chose to use the value beta.)

On beta (the destination computer) append the following line to /etc/pulse/

load-module  module-native-protocol-tcp  auth-ip-acl=;LAN_NAME

In the above, LAN_NAME and IP_ADDRESS_OF_BETA will be specific to your computers and your LAN. For example, they might be:

LAN_NAME            =

After making the above changes, restart pulseaudio, first on beta, then on alpha. The order matters. I restart pulseaudio with pulseaudio --kill. I run pulseaudio --kill as my pesonal UID (not as root), as pulseaudio is already running as my personal UID.

If everything worked successfully, you should now see the tunnel on the Output Devices tab of pavucontrol on alpha. When an audio source is playing, you should be able to route the source to the tunnel on the Playback tab of pavucontrol on alpha.

As long as the tunnel is intact, you should also be able to see the tunnel on the Playback tab of pavucontrol on beta. If the tunnel disappears, restart pulseaudio, first on beta, then on alpha. The tunnel is only created when pulseaudio starts on alpha.

Note 1: This example assumes pulseaudio is running on both alpha and beta. As of 2016, pulseaudio runs by default on Ubuntu, and has for years.

Note 2: This example does not use Avahi Zero-configuration networking. Avahi may be enabled by default on Ubuntu, but I have disabled Avahi on my systems. On my LAN, beta (the destination computer) always has the same IP address, and I know that address.

Note 3: The above auth-ip-acl grants access to any device on the LAN. Pulseaudio also supports other (more secure) authentication methods. I use auth-ip-acl to simplify configuration.

More information can be found at the following pages:

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply