Subnet specification for tinc node as default gateway

[Guus Sliepen]

On Sun, Sep 01, 2013 at 01:14:25PM -0700, Nikolaus Rath wrote:

> I want to use a tinc node as a default gateway in router mode.
> 
> My first attempt was to just add an extra, lower priority subnet for the
> host that should act as the gateway:
> 
> Subnet = 192.168.12.2/32
> Subnet = 0.0.0.0/0#20
> 
> but this doesn't seem to work:
> 
> # route add 173.255.235.238 gw 192.168.12.2
> # ping 173.255.235.238
> 
> results in the local tinc process complaining that
> 
> Read packet of 98 bytes from Linux tun/tap device (tun mode)
> Cannot route packet from vostro (MYSELF): unknown IPv4 destination address 173.255.235.238

Did you restart the tincd on the gateway after you added that Subnet? It should
work otherwise. You don't even have to add #20; subnets with a larger netmask
are always lower in priority than those with a smaller netmask.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20130901/66ec4a1a/attachment.sig>