Exposing extra subnet via Tinc

[Hamish Moffatt]

On 6/12/18 11:45 am, Daniel Lo Nigro wrote:
> I worked this out - I just had to manually add a route on the Windows 
> machines:
>
> route add 192.168.122.0 mask 255.255.255.0 10.123.1.4
>
> (where 10.123.1.4 is the local IP on the Tinc interface)
> I was hoping that Tinc would automatically configure the routing 
> tables, but configuring it manually is fine.


Tinc will run its hook scripts subnet-up and subnet-down when it learns 
about subnets at other nodes. 
https://www.tinc-vpn.org/documentation/Scripts.html


Unfortunately I could not find an example of these for Windows. I posted 
about this a couple of weeks back but did not get any response.



Hamish

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20181206/8de9e6ff/attachment.html>