Can't send files, using SOCKS 5 proxy and file transfer proxy

Morgantoni

06-03-2006, 16:32 #1

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

Subject: Can't send files, using SOCKS 5 proxy and file transfer proxy

Hi!

I'm using an SOCKS 5 proxy for chatting... Now I want to send files...

If I don't use any file transfer proxy, I can't send or recieve any file...

But if I use a file transfer proxy like proxy.jabber.org, I can recieve a file, but not send...

Is that a problem by me, by Psi oder by Jabber?

Thanks

michalj (Moderator) 06-03-2006, 17:47 #2

Member since 04/2004 · 2285 posts · Location: Legionowo, Poland
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

Sometimes Psi fails to send or receive files when both parties (sender and receiver) are behind NAT even if both sides have the file transfer proxies set (sometimes this is caused by very restrictive port policies on NAT proxies - most (if not all) file transfer proxies work only on selected port(s), which is usually blocked).

Michał Jazłowiecki (michalj)
Psi Forum & Wiki Moderator :: Psi-Daisy Author

Morgantoni

06-03-2006, 18:06 #3

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

That could be that problem...

But there are no "very restrective" firewalls... Only private routers...

But If I use proxies, that should be a problem, because Proxies should solve that kind of problems...

my pc <-> SOCKS 5 <-> file transfer proxy <-> filetransfer proxy <-> pcc of a friend

What is here that problem?

michalj (Moderator) 06-03-2006, 18:16 #4

Member since 04/2004 · 2285 posts · Location: Legionowo, Poland
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

There ARE very restrictive firewalls. Especially in large international companies.

For example, I know (very well) a company which allows outgoing traffic only on ports 80, 443 and 1863 (MSN Messenger uses the last one). I cannot even use some of my Jabber accounts as Jabber servers where those accounts are located listen (for c2s connections) only on classic Jabber ports (5222 and 5223). I couldn't even use Google Talk account until last week (they have enabled connections on port 443).

And if I'm not mistaken, most of file transfer proxies use port 7777. BTW: I'm not sure whether file transfers do not omit SOCKS5 proxy.

Michał Jazłowiecki (michalj)
Psi Forum & Wiki Moderator :: Psi-Daisy Author

Morgantoni

06-03-2006, 19:05 #5

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

Sorry... I mean home router... I mean private routers, that you use at home not in business...

But PSI should enforce using SOCKS 5 if I select it! I

I want to use my SOCKS 5 proxies obecause of many reasons... So I'm not happy, if Psi ignore my settings...

So I should really setup an restrective Firewall...

Kev (Administrator) 06-03-2006, 19:27 #6

User title: Project Lead
Member since 11/2002 · 3055 posts · Location: Exeter, UK
Group memberships: Administrators, Developers, Members

Show profile ·

Link to this post

The socks5 proxy is for the xmpp stream, not for file transfers, which have their own proxy type. It's true that it'd be sensible to also wrap that in a socks proxy if enabled and it's likely we'll do this at some stage. Until then you could socksify Psi

Psi Project Leader.
Homepage, including development blog

michalj (Moderator) 06-03-2006, 19:36 #7

Member since 04/2004 · 2285 posts · Location: Legionowo, Poland
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

Psi uses SOCKS5 proxies but only for chats, groupchats and other Jabber/XMPP stream stuff. Psi uses JEP-65 proxies for file transfers.

Michał Jazłowiecki (michalj)
Psi Forum & Wiki Moderator :: Psi-Daisy Author

Kev (Administrator) 06-03-2006, 22:34 #8

User title: Project Lead
Member since 11/2002 · 3055 posts · Location: Exeter, UK
Group memberships: Administrators, Developers, Members

Show profile ·

Link to this post

In addition, only XMPP stream stuff is sent over socks5, while file transfers use their own proxy type.

Psi Project Leader.
Homepage, including development blog

Morgantoni

06-04-2006, 04:04 #9

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

Two things..

1.) If I set a SOKCS/HTTP Proxy for using, I want that Psi use only that for communication... Because of firewalling or anonymizing... So I'm not happy with that way of work... Why do you use SOCKS only for other stuff than file transfere?
2.) I can't send any file, if I set using SOCKS 5 Proxy, but can recieve. But I can send and recieve files if I don't use a SOCKS proxy. Both times I use the a file transfere server. So that problem has to do with using SOCKS 5 proxy

Thanks for your time

Bye

IceRAM (Moderator) 06-04-2006, 09:13 #10

Member since 05/2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

I think there are some misunderstandings floating around:

We are talking about 2 types of proxies: Connection Proxy and a File Transfer Proxy.

Connection Proxies can be, as it can be found in "Account Properties > Connection":

SOCKS5 proxy

HTTP Connect

HTTP Polling.

File Transfer Proxies ("Account Properties > Misc" (in 0.11))

must respect JEP-0065 (JEP=Jabber Enhancement Proposal)

they are specific to Jabber

according to the JEP, this type of proxies must implement a subset of the SOCKS5 protocol - Quote: Specifically, this JEP proposes that the Jabber community make use of the SOCKS 5 protocol, which is an IETF-approved, IPv6-ready technology for bytestreams. (Note: Because this proposal uses a subset of the SOCKS5 protocol that is specially adapted for Jabber bytestreams, existing SOCKS5 proxies cannot be used to implement this proposal without modifications.)

Psi known, right now, the following scenarios:

All traffic except File Transfer:

Psi <-> Jabber Server <-> ... (direct connection)

Psi <-> Connection Proxy <-> Jabber Server <-> ... (proxy connection)

File Transfer:

Psi <-> Remote Client* (direct connection)

Psi (with Data Transfer External Address set - "Options > Application") <-> Remote Client* (direct connection)

Psi <-> File Transfer Proxy ("Account Properties > Misc" in 0.11) <-> Remote Client* (proxy connection)

From what I understand, the desired behaviour described by you is:

Psi <-> Connection Proxy <-> File Transfer Proxy <-> Remote Client* (double-proxy connection)

which currently is not possible in Psi. Apparently, this sounds right.

However, this is a bit complicated compared to the alternative scenario:

Psi <-> Connection Proxy <-> Remote Client* (proxy connection)

where Psi connects directly to the Remote client through the Connection Proxy - this will most likely work if the Remote Client accepts connections (I'm not sure if the File Transfer Proxies can accept connections on behalf of the clients)

--
* I think Remote Client can also be the File Transfer Proxy declared by the other party (I'm not sure if the File Transfer Proxies can accept connections on behalf of the clients)

P.S. I think I will wikify this in the future

Edit 1: added "alternative scenario"
Edit 2: corrected bottom note

::/ my .net presence / weblog | psi

This post was edited 2 times, last on 06-04-2006, 10:14 by IceRAM.

Morgantoni

06-04-2006, 09:31 #11

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

That explination is great...

You're right, I desire the last version.. "Psi <-> Connection Proxy <-> File Transfer Proxy <-> Remote Client* (proxy connection)"

It's only a Pis implentation problem, that that not works now, or not?
But why... All application, that I know and supports SOCKS 5, use for all connection types SOCKS 5... Not only for one type...

It would be very great, if you can fix that bug in a future version

Thanks

IceRAM (Moderator) 06-04-2006, 09:54 #12

Member since 05/2003 · 1286 posts · Location: Bucharest, Romania
Group memberships: Global Moderators, Members

Show profile ·

Link to this post

Quote by Morgantoni:
It's only a Pis implentation problem, that that not works now, or not?
[...]
It would be very great, if you can fix that bug in a future version

Well, I wouldn't call it an implementation problem, nor a bug. I think nobody thought about this "proxied proxy situation" - it is a bit un-natural, in my opinion.

Quote by Morgantoni:
But why... All application, that I know and supports SOCKS 5, use for all connection types SOCKS 5... Not only for one type...

Well, most applications have only one type of connection (just like the usual client <-> jabber server connection). The proxy setting applies to all connections of that type.

In jabber, the "File Transfer Proxy" appeared because there were people behind NAT but with no restricted outside access (=no firewalls) or with firewalls allowing outside connections. So, the File Transfer Proxy is like a temporary proxy used only for File Transfer.

However, some firewalled users behind NAT might not be able to access the File Transfer Proxies - this situation was overlooked most likely because it seems a bit un-natural, as I've said above.

::/ my .net presence / weblog | psi

Morgantoni

06-04-2006, 11:02 #13

Member since 06/2006 · 37 posts
Group memberships: Members

Show profile ·

Link to this post

Quote by IceRAM:
Quote by Morgantoni:
It's only a Pis implentation problem, that that not works now, or not?
[...]
It would be very great, if you can fix that bug in a future version
Well, I wouldn't call it an implementation problem, nor a bug. I think nobody thought about this "proxied proxy situation" - it is a bit un-natural, in my opinion.

I don't think so.. Because, if I use a proxy, I've restrictions, that could be, that I'm not allowdto make any direct connection. I know many students, they're living in camps and had to use socks and http proxies...

Quote by IceRAM:
Quote by Morgantoni:
But why... All application, that I know and supports SOCKS 5, use for all connection types SOCKS 5... Not only for one type...
Well, most applications have only one type of connection (just like the usual client <-> jabber server connection). The proxy setting applies to all connections of that type.

In jabber, the "File Transfer Proxy" appeared because there were people behind NAT but with no restricted outside access (=no firewalls) or with firewalls allowing outside connections. So, the File Transfer Proxy is like a temporary proxy used only for File Transfer.

However, some firewalled users behind NAT might not be able to access the File Transfer Proxies - this situation was overlooked most likely because it seems a bit un-natural, as I've said above.

But if I've to use a socks proxy I had to use a file transfer proxy, too. Because I'm not able to use any kinid of connection without socks...

So I'm looking forward to an option like (file transfer proxy: "use xxxx proxy for connect to file connection proxy"...

That would be great...

Thanks ....

infiniti (Administrator) 06-06-2006, 19:05 #14

Member since 09/2002 · 1442 posts · Location: California, USA
Group memberships: Administrators, Developers, Members

Show profile ·

Link to this post

I'm reworking the networking code, which should make it easier to stack proxies like this. So file transfer proxy over connection proxy should be possible in the future.

-Justin

Ephraim 06-07-2006, 07:20 #15

User title: just a human!
Member since 08/2005 · 263 posts · Location: Germany -- Bavaria -- Augsburg
Group memberships: Members

Show profile ·

Link to this post

That would be great Infiniti!!!!

I'm looking forward to the day I can use data transfer proxies via a connection proxy !!!

If you need help testing or so, just ask!

Ciao Ephraim

43 69 61 6f 20 45 70 68 72 61 69 6d 21 0A 00
4c 69 6e 75 78 20 69 73 20 74 68 65 20 62 65 73 74 2c 0A
66 6f 72 67 65 74 20 74 68 65 20 72 65 73 74 21 00

Announcement