[Pidgin] #10018: Problems to create a Jingle connection (something confusing about IP addresses; libnice?)

[Pidgin]

#10018: Problems to create a Jingle connection (something confusing about IP
addresses; libnice?)
--------------------------+-------------------------------------------------
 Reporter:  mcepl         |     Owner:  rekkanoryo
     Type:  defect        |    Status:  new       
Component:  unclassified  |   Version:  2.6.1     
 Keywords:                |  
--------------------------+-------------------------------------------------
 (Edited and cleared up transcript of IRC chat with Maiku on #pidgin)

 mcepl: I am testing with two guys who have psi 0.13 (who claim it works
 for them) and no luck ... XMLLogs are xml-log-spike.xml and xml-log-
 zenek.xml Any ideas how to make it work? And yes, I have STUN setup to
 stun.ekiga.net And no, it didn't make any difference who initiated the
 call.
 Maiku: dang you have a bunch of IPs
 Maiku: it's weird because psi is the side that's terminating it
 mcepl: OK, can I try it with somebody with pidgin ... interop with itself
 would be a good start ;-)
 Maiku: what exactly happens?
 mcepl: with xml-log-zenek.xml I heard him and he didn't hear me, in xml-
 log-spike.xml I hear nothing and he as well. But it appears to connect and
 windows goes up, and camera gets switched on. A debug log is pidgin-
 log.txt.bz2
 Maiku: well.. it's just sitting on connecting.. I'm not sure why that
 would be though.. which versions of farsight2 and libnice do you have?
 mcepl: farsight2-0.0.14-1.fc11.x86_64
 mcepl: libnice-0.0.9-1.fc11.x86_64
 mcepl: Maiku: works just smoothly between two psi on the very same
 computer with Spike (XML Log is psi-log.txt)
 ...
 mcepl: Maiku: yes, it might be relevant ... I am also on VPN a I have set
 up kvm (although no virual machine is alive at the moment), so I have more
 than one network interfaces.
 Maiku: can you pastebin with "NICE_DEBUG=all" set?
 Maiku: I'm kind of at a loss.. psi worked fine for me when I tried.. the
 only reason it should consistently fail to connect is network issues or
 missing stun apart from a bug in libnice
 ...
 mcepl: Maiku: actually, it is multiple network interfaces ... I have
 switched off VPN and suddenly communication with psi works ... pidgin-log-
 one-network-interface.txt.bz2 Surprisingly libvirtd is still running so
 network 192.168.122.* is still around.
 Maiku: mcepl: that one looks like it connected fine
 Maiku: well always use NICE_DEBUG then and you'll be ok :P jk
 mcepl: Maiku: so, what do you do when you find multiple network
 interfaces? (my boss wouldn't be too happy if I told him that internal VPN
 IP address went around whole internet)
 Maiku: mcepl: it gathers all of them, then sends them to the other person
 with various ports then picks the one it can connect to
 Maiku: a NICE_DEBUG=all of when it doesn't work could be forwarded to the
 person that could help but if two people both have a certain type of NAT
 going on, then I don't know that there's much you can do, but if it
 sometimes connects... and BTW psi manages this well (if VPN is down)
 Maiku: sounds like it's a bug in libnice in that case..
 ...
 mcepl: I just can say that with VPN up I was not able to communicate with
 psi, with VPN down I can.
 Maiku: that NICE_DEBUG=all of if failing would be nice :P
 mcepl: And even with VPN down (but other side hasn't have confirmed
 functionality before) I cannot get voice pidgin-pidgin.
 Maiku: mcepl: ok, sent it to kakaroto. he should be able to provide some
 input and/or fix it, but he's probably sleeping now
 mcepl: ok, I will file a ticket

-- 
Ticket URL: <http://developer.pidgin.im/ticket/10018>
Pidgin <http://pidgin.im>
Pidgin