[pulseaudio-tickets] [PulseAudio] #656: No more network tunnels

PulseAudio trac-noreply at tango.0pointer.de
Sat Sep 19 06:59:10 PDT 2009


#656: No more network tunnels
---------------------+------------------------------------------------------
  Reporter:  towolf  |       Owner:  lennart
      Type:  defect  |      Status:  new    
 Milestone:          |   Component:  daemon 
Resolution:          |    Keywords:         
---------------------+------------------------------------------------------

Comment(by towolf):

 If you have ipv6 set up it will use it.

 So what does this mean?


  Tunnels will not be mentioned in the debug until:

   a) module-gconf is loaded

 check

   b) paprefs has the option for "Make discovered devices available
 locally"
  ticked.

 check

   c) remote pulseaudio daemon has suitable tcp protocol modules loaded
 with
  appropriatly loose authentication (can be enabled in remote system's
 paprefs).

 check

   d) firewall allows port 4713

 check

   e) Avahi is setup and installed and on the local machine {{{avahi-browse
  -t _pulse-sink_._tcp}}} correctly sees the remote pulseaudio.

 check

  I've tested it here and pulseaudio 0.9.18 correctly finds and adds a
  tunnel for a remote PA instance, so I suspect whatever the problem is, it
  is in your setup or the ubuntu packages.

 Well my routerbox doesn’t do IPv6. I can "dig -4 hostname" but not "dig -6
 hostname". Is this the problem?

-- 
Ticket URL: <http://pulseaudio.org/ticket/656#comment:7>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server


More information about the pulseaudio-bugs mailing list