No more network tunnels

[towolf]

Salve.

I have a laptop and a server-like thing connected to my stereo. Both are running 0.9.18 now. I used to be fond of the tunnels feature, where you could move streams back and forth in pavucontrol.

Now, since 0.9.16 or so there are no more tunnels. Both zeroconf modules are loaded on both sides, avahi-browse shows them, padevchooser can see the other server. And I can play to the other PA server (running in system mode) directly via PULSE_SERVER.

Only pavucontrol has no record of anything other than the local sink. Was network support removed? I see no mention in the last ChangeLogs?.

[coling]

Avahi support was accidentally broken in 0.9.16 and 0.9.17 but it should be fixed in 0.9.18 in [05f6236a83414573587c73dbc439e68dae5f529e]

Are you sure that this is still not working with 0.9.18?

[towolf]

paman says:

server1: linked to 0.9.18; compiled with 0.9.14 server2: linked to 0.9.18; compiled with 0.9.14

The modules are loaded, but in pavucontrol I only see local. And right-clickign doesn’t offer me to move a stream.

[towolf]

Oh and pavucontrol is at version: 0.9.8+git20090701-0ubuntu3~ubuntuaudiodev1

[coling]

pavucontrol is a bit old but it doesn't matter really.

paman is pretty much a useless tool (it's really just a nice gui around "pacmd list" :)

Anyway, I've tested avahi detection of roap sinks here with 0.9.18 and it works fine... normal networks sinks should be the same.

Can you attach pulseaudio -vvv output? (you may have to kill pulse with pulseaudio -k first and it may autospawn again very quickly so run the two commands together - you may have to try it a few times before the timing is right and pulse startup up :).

[towolf]

pulseaudio -k; pulseaudio -vvv

[towolf]

Last time I tried debug output, there was no mention of tunnels at all.

Now, why is it trying IPv6 at all? I’m not sure I have IPv6 set up ...

[coling]

If you have ipv6 set up it will use it.

Tunnels will not be mentioned in the debug until:

a) module-gconf is loaded b) paprefs has the option for "Make discovered devices available locally" ticket. c) remote pulseaudio daemon has suitable tcp protocol modules loaded with appropriatly loose authentication (can be enabled in remote system's paprefs). d) firewall allows port 4713 e) Avahi is setup and installed and on the local machine avahi-browse -t _pulse-sink_._tcp correctly sees the remote pulseaudio.

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.

[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?

[towolf]

trac’s wiki-autoformat is seriously retarded.

[towolf]

Oh, did or did you not look at the output I attached above?

Excerpt:

$ grep ^E: pa-vvv.log 
E: main.c: Failed to kill daemon: No such process
E: module-tunnel.c: Failed to connect to server '[fe80::200:f0ff:fe83:5b47]:4713'
E: module.c: Failed to load  module "module-tunnel-source" (argument: "server=[fe80::200:f0ff:fe83:5b47]:4713 source=alsa_input.pci-0000_00_1f.5.analog-stereo format=s16le channels=2 rate=44100 source_name=tunnel.sams.local.alsa_input.pci-0000_00_1f.5.analog-stereo channel_map=front-left,front-right"): initialization failed.
E: module-tunnel.c: Packet too long

[coling]

Oh right, sorry, I missed that one (think I was thrown by the "no mention of tunnels at all" comment which made me associate the problem with the avahi issue). Seems there is indeed a problem somewhere. You can perhaps disable ipv6 (I'm not sure the correct way but perhaps just setting up avahi with use-ipv6=no in /etc/avahi/avahi-daemon.conf on both ends and see if it helps. It at least rules it out even if it doesn't fix it, but I suspect the problem is in the code somewhere itself...

[coling]

Right this should be fixed now in [592345f] and [c194db7]. It didn't trigger for me due to the remote server in question being somewhat out of data so apologies for that one.

Please reopen if these don't fix things for ya.

PS I've also applied these two fixes to the 0.9.18-stable branch, the commits on which are recommended for packages to include when distributing.