Hi,
From what Colin says, the standard port is 4713 for pulseaudio. As I said
before all network ports are blocked except port 22 which is only for ssh
connections.
I should be able to tunnel port 4713 through ssh by doing this: ssh -L
4713:localhost:4713 user@server. Then I can tell pulseaudio
Hi,
I found this message when I am trying to tunnel 4713 via ssh ssh -L
4713:localhost:4713 user@server:
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 4713
Could not request local forwarding.
Hi,
I finally got some more details from pulseaudio. I did this on the client:
--
# stop pulseaudio
# pulseaudio --system --high-priority -C
--
Now, when I run pactl stat on the server, pulseaudio on the client
reports:
Hi,
Some more attempts. I have now tried this:
client (session 1): stop pulseaudio
client (session 1): pulseaudio --system --high-priority -C
client (session 2): ssh -R 4000:localhost:4000 user@server
client (session 3): socat TCP-LISTEN:4000,fork
UNIX-CONNECT:/var/run/pulse/native
server:
Hi,
why following command does not work
load-module module-null-sink sink_description=tuned\ patchbay:\ TCP\
source\ xxx,sink_name=tuned.patchbay.source.xxx
while this one works:
load-module module-null-sink
sink_name=tuned.patchbay.source.xxx,sink_description=tuned\
patchbay:\ TCP\ source\
Hi,
I did a LANG=C pulseaudio --system --high-priority -
/root/pulseverbose.log 21 on the client to write a detailed log file.
Here is the results when the remote client tries to connect:
-
I: client.c: Created 9 Native client
Hi,
I think you're maybe getting a little confused by client and server in
terms of how things work here (perhaps not, as I've not thoroughly read
all the many posts in this thread).
As I know how to do what you want to do, I'll just write the
instructions here:
1. Start of on the machine you
