UPnP support in tinc

[fauno]

Etienne Dechamps <etienne at edechamps.fr> writes:

> On 12 November 2015 at 01:15, fauno <fauno at kiwwwi.com.ar> wrote:
>> Etienne Dechamps <etienne at edechamps.fr> writes:
>>> (I realize that this means UPnP support could possibly be achieved
>>> simply by suggesting that the user spawn some standalone UPnP client
>>> process in the background from the tinc-up hook. That's not very
>>> user-friendly, though. Especially on Windows.)
>>
>> something like this :P
>>
>> https://github.com/LibreVPN/librevpn/blob/develop/lib/skel/scripts/port-forwarding
>
> Unless I'm missing something, the problem with that script is that it
> won't keep the mapping alive. If the home router expires the mapping
> after a while (which is bound to happen, otherwise it would end up
> with accumulating garbage) or resets, there's nothing to "refresh" it.

of course, the mapping is set to a long time (all the 9s are seconds)
but if the router resets or decides to drop the mapping there's nothing
to do, except restart the tinc node.

> Ideally, one would want a daemon (or at least some kind of periodic
> event) that keeps refreshing the mapping (like every minute or so).
> Which at best would be annoying to manage (on POSIX), or at worse
> would be a PITA (on Windows). Hence my suggestion to integrate it
> directly into tincd.

+1 :D

-- 
http://librevpn.org.ar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 584 bytes
Desc: not available
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20151112/f9c4cbe9/attachment.sig>