search

iniwf / psi-dev

Automatically exported from code.google.com/p/psi-dev
0 stars 0 forks source link

IPv6 for file transfer #440

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Версия: Psi+ 0.15.4113 (Jun 25 2011) (и боле старые)
Баг: Psi+ прослушивает tcp порт для передачи 
данных только на 0.0.0.0 (любой IPv4 адрес)
Пожалуйста добавьте поддержку IPv6 для 
передачи файлов.

Version: Psi+ 0.15.4113 (Jun 25 2011) (and older)
Bug: Psi+ listen tcp port 8010 for file transfer only at 0.0.0.0 (any IPv4 
address)
Please add IPv6 support for file transfer.

Original issue reported on code.google.com by bart...@gmail.com on 1 Jul 2011 at 8:50

GoogleCodeExporter commented 9 years ago 
After troubleshooting for quite some time I also noticed that Psi+ 
v0.15.5160-58 (Dec 25 2011) does not support filetransfer via IPv6.
This makes it impossible to transfer files via XMPP.

Original comment by eim...@etherkiller.de on 28 Dec 2011 at 2:14

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Most interesting thing is that for dual-stack (both IPv6 and IPv4) machine Psi+ 
0.16.105 always choose IPv6 address for file transfers (then host name, then 
bytestream proxy), despite Windows priority set for IPv4 over IPv6.

Original comment by ache...@gmail.com on 22 Mar 2013 at 6:56

GoogleCodeExporter commented 9 years ago 
I have dual stack machine under Linux and Psi+ listens only IPv4 port 8010.

Original comment by g.shura0 on 16 Apr 2013 at 12:35

GoogleCodeExporter commented 9 years ago 
from what I can see in the code, Psi listens for file transfer on the same 
addresses from which xmpp connection was done. + external address from main 
settings.

I'm agreed, most of jabber servers are on ipv4 now but using ipv6 may make life 
easier in case of file transfer

Original comment by rion4ik on 29 Aug 2013 at 6:09

GoogleCodeExporter commented 9 years ago 
Just to note, popular jabber.ru is dual-stack too (mainly due to its yandex 
hosting), and from dual-stack-machine client connection can go to any of its 
IPv6/IPv4 addresses.

Original comment by ache...@gmail.com on 29 Aug 2013 at 11:09

GoogleCodeExporter commented 9 years ago 
IPv6 will be preferred in case of IPv6 xmpp server since Psi does IPv6 dns 
resolve first and tries to connect and in case of fail switches to IPv4

Original comment by rion4ik on 29 Aug 2013 at 11:18

GoogleCodeExporter commented 9 years ago 
There is mechanism called round-robin (rotation). It depends of which of 
jabber.ru's 4 addresses is resolved first then cached locally, which in turn 
depends of which NS will answer first. In the wild I notice both IPv6 and IPv4 
connections to jabber.ru in equal chance from my dual-stack machine.

Original comment by ache...@gmail.com on 29 Aug 2013 at 11:26

GoogleCodeExporter commented 9 years ago 
that's strange.
jabber.ru on srv always returns jabber.ru:5222 (tested with 8.8.8.8)
then Psi requests AAAA for jabber.ru and tries to connect with resolved 
addresses. and if fails it starts resolving A records and connect to IPv4.

most probably on you system IPv6 sometimes fails to connect.

Original comment by rion4ik on 29 Aug 2013 at 11:57