[freenet-dev] UP&P, again

[Matthew Toseland]

On Thursday 24 May 2007 13:30, Florent Daignière wrote:
> Hi,
>
>  Just to keep people posted, I've written a plugin to provide basic upnp
>  support to the node... Currently it uses two features of the protocol:
>
>  1) external IP address reporting
> I'm confident that  it works in "simple"  cases
>
>  2) port forwarding of the FNP port
> Should work, might not persist, might have some forgotten border cases
>
>  More  work has  to be  done to  make it  behave "properly",  and handle
>  border cases  (more than one IGD  on the LAN, external  IP changes, IGD
>  reboot, ...) but I don't think that it worths the effort.

Thanks for building this. We should support the more common cases IMHO - 
rebooting the IGD, the external IP changing. If it's easy to support two IGDs 
then it might be nice to do so, but generally that suggests trouble; it may 
be sensible to leave it as disabled, or it may be better to tell the user 
about it.

Also I think UP&P should run on every startup, unless we are directly 
connected to the inet.

Anything that improves connectivity and reduces reliance on STUN servers (an 
obvious thing for an attacker to watch) has to be a good thing.

Have you implemented the "my LAN is reasonably secure" option?
>
>  I'm looking forward any feedback testers could provide.
>
> NextGen$
> PS: to try it out, get the testing(trunk) version of freenet and type in
> UPnP# in the plugin-loading box on the plugins toadlet of fproxy.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070524/b5927d01/attachment.pgp