https://bugs.freedesktop.org/show_bug.cgi?id=69429
--- Comment #5 from Tanu Kaskinen <[email protected]> --- (In reply to comment #4) > + > > pactl list sources > > Thanks again for your continued attention, I signed up to the pa > listserv in hopes of gleaning something useful, but am reluctant to > intrude into what seems exclusively to be developers talking to each > other. Please let me know if I should move the discussion there, or > somewhere else... and thanks again for your help. The mailing list is meant for both users and developers, so it's fine to ask help there. > The source appears on the remote box, changes from State: SUSPENDED to > State: RUNNING when the XM receiver is switched on. > > It does not appear on the local box. Manually loaded > 'module-loopback' on both to see if either noticed, no changes > visible. The two PC's are on the same segment. module-loopback won't be of any help before you have the remote source visible locally. > Is that the same module that paprefs would load if the 'loop back > audio' button is pressed on the RTP tab? No, I think the RTP loopback uses some other mechanism. > The RTP modules do not seem to load on the remote box [using ssh with > -X], does the 'module-loopback' loaded with pactl need configuring on > the CLI input? > > So should the RTP stuff be running on both boxes, and do additional > ports [beyond 4713], need to be opened on the firewalls for that to > work? Are any other firewall ports required for anything else? RTP streaming is a different thing than the normal network setup. You don't need the RTP modules for anything. module-zeroconf-publish and module-zeroconf-discover use Avahi for communicating with each other, so the Avahi port (UDP 5353) needs to be open in the firewall. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
