[Psi-devel] upnp support for filetransfers

[Norman Rasmussen]

UPNP and STUN are complementary (actually there's NAT-PMP too).

UPNP/NAT-PMP would be much simpler to implement in the Psi codebase as it
stands (really it's just the extra firewall call to establish the external
IP address, and map the port to the local machine).

Adding STUN support requires Jingle-FT, which probably requires more code
changes, so I really see UPNP/NAT-PMP as a quick win stop-gap until we have
full Jingle-FT support.

On a side note, you might find that someone implements a symmetric firewall
which STUN can't get around.  In this case you'd have to have some sort of
UPNP/NAT-PMP protocol to ask for a port to be opened and forwarded to the
local machine.

On 4/9/07, Francisco Joaquín Rodríguez Prados <prados at gmail.com> wrote:
>
> On 31/03/07, Norman Rasmussen <norman at rasmussen.co.za> wrote:
> > What are the plans for adding upnp support to Psi?
>
> Who wants UPNP when STUN is out there? >:)
>
> Now serious. Aren't we sort of waiting for Jingle file transfer to
> become a standard - which actually uses STUN?
>
> (Technical note: the STUN client asks a server for its IP and opened
> port in the NAT router; afterwards a connection can be established
> trhough this known IP and port.)
>
> Fran.
>
> --
> Francisco Joaquín Rodríguez Prados
> Colegio Mayor Isabel la Católica
> Universidad de Granada
> Granada, Spain
> Phone: (+49) 176 24 255 490
> Phone: (+34) 615 975 631
> E-mail: prados at gmail.com
> JID: franqui at jabber.dk
> _______________________________________________
> psi-devel mailing list
> psi-devel at lists.affinix.com
> http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com
>



-- 
- Norman Rasmussen
- Email: norman at rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.affinix.com/pipermail/psi-devel-affinix.com/attachments/20070409/e7a9db10/attachment.htm