libnice sometimes can't establish connection on multihomed hosts

Question

libnice sometimes can't establish connection on multihomed hosts

Closed this issue 9 years ago · 9 comments

On my computer I have this interface, setup by Virtualbox.

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Having this interface blocks me from joining audio. I can see the shared screen though, and the chat.

If I disable the interface with:

sudo ip link set virbr0 down

...then I can connect just fine.

Answer 1 · 2016-05-27T10:27:48.000Z

I have a very strange observation. When I enabled exhaustive logging, I could connect to the audio even though virbr0 was present. I tried 3 times successfully. (I had GST_DEBUG=5 running)

Could this be some kind of race condition? That the i/o was slowing down the system enough for the setup of the call to be established?

Answer 2 · 2016-05-27T12:21:04.000Z

I do have the same i/f, I can join audio, though I still have audio problems (even after the May 23rd patch), maybe related ?

Answer 3 · 2016-05-27T15:34:14.000Z

@tmuehlhoff If you can join audio, can you be more specific what your actual 'audio problems' are? Bad sound quality, you can hear the others speaking but they can't hear you, or something else?

Answer 4 · 2016-05-27T15:35:56.000Z

@tmuehlhoff Or maybe you're experiencing something like #85?

Answer 5 · 2016-05-30T10:38:27.000Z

Behaviour is strange. If I started pidgin normally (without logging), I could connect - no problem. The problem is there if I start Pidgin with logging. BUT if the logging is EXHAUSTIVE, I can AGAIN connect to audio. It is consistent, but strange consistent :-)

Answer 6 · 2016-05-30T16:47:21.000Z

I guess the title is not true, but I don't have a better name for it.... :-(

Answer 7 · 2016-06-01T11:49:39.000Z

@xnandersson Because the recent larger libnice update may have rendered this issue obsolete, I'm switching its state to 'more information needed'.

Please try to reproduce the bug with up-to-date PPA. Otherwise I'll close the ticket after 14 days, as is my common practice.

Answer 8 · 2016-06-01T11:51:55.000Z

@xhaakon Sure thing! I'll get at it :-)

Answer 9 · 2016-06-16T12:28:21.000Z

This issue hasn't been reproduced after a libnice update, so closing.