File transfers not working

[slack woody]

I have an ejabberd server and set up the internal file transfer proxy on port 10000:

  mod_proxy65:
    hostname: "mydomain.com"
    port: 10000

At one point Psi was working for transfers but for some reason it stopped and I can't figure out why.

I've been testing with a friend and we have tried various stun servers, file proxy servers and the only thing that works is inband.

When we try to send something and I check netstat I see my client is trying to connect to his LAN IP...

tcp        0      1 192.168.1.3:33547       192.168.10.101:8010     SYN_SENT    22418/psi-plus


At this point I'm unsure what to do. I have tried forwarding ports in my router to my laptop running Psi(-plus) and he has done the same but nothing seems to work.

I have looked around for some definitive guide or howto but all I can find are RFCs. Can someone tell me what the problem is?

[Rion]

did you try to set "Data transfer external address" in Psi settings?

can you check with any online tool that port is open and forwarded?

look at xml console for details what IP will be used.

afaik Psi doesn't use STUN for file transfer.

2013/11/14 slack woody <slac...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Psi-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to psi-users+...@googlegroups.com.
To post to this group, send email to psi-...@googlegroups.com.
Visit this group at http://groups.google.com/group/psi-users.
For more options, visit https://groups.google.com/groups/opt_out.

[slack woody]

Is the data transfer external address my IP or is it the IP/URL of the file proxy? Also does it need to port number - ie :10000 on the end (if it's for file proxy)

[Rion]

it's external address of your router. the address assigned by ISP

2013/11/14 slack woody <slac...@gmail.com>

[slack woody]

Ok that worked just fine. Thanks for the help.

But I have an observation: a stun server is meant to get your IP for you so you don't need to enter it manually whenever it changes. It's not that big a deal for me because mine rarely changes, but friends on dynamic IPs will get a new one each time they come online.

I don't see why each account would need its own stun server setting (which doesn't appear to work anyway). Why not just have one in the options page the same that pidgin does and use that?

Can I put that in as a feature request? If I can't here, where is the best place to do that?

[Rion]

stun server often can be determined by special dns request to jabber server subdomain. moreover this allows to disable stun per account. not sure how useful this feature is.

but I'm agreed to have some defaults sounds reasonable.

I'll add stun support for ft one day.

I also have to note I'm now working on upnp-igd support as an alternative approach of receiving external address and port forwarding.

about the place, try our bug tracker on github

2013/11/14 slack woody <slac...@gmail.com>

[slack woody]

Great, thanks for the info. Unfortunately transfers to me stopped working again :/

[Rion]

what clients do you have on both sides?

2013/11/14 slack woody <slac...@gmail.com>

[slack woody]

I'm using Psi+, friend is using Psi

[Rion]

exact versions?

xml log would be useful too.

[Rion]

can you update your Psi+ first and then repeat the test?

2013/11/14 slack woody <slac...@gmail.com>

Cleaned log: http://pastebin.slackadelic.com/p/zPkPrl64.html
The IPs are correct. The proxy stream shows 7777 rather than the 8010 which I opened on the router. I'll add a forward for it.

Sender Psi v0.15
Receiver Psi+ v0.16.130 (2013-07-04) 

[slack woody]

I don't see any newer version of Psi+

[Rion]

please join our conference xmpp:psi...@conference.jabber.ru?join

[slack woody]

I tried to join it earlier, and I was taken to a webpage to enter some text, but no text showed.

On Thursday, 14 November 2013 07:04:34 UTC, Rion wrote:

please join our conference xmpp:psi-dev@conference.jabber.ru?join