Hi,
I am not sure to exactly understand your problem, but, if you want
to add a route to a remote subnet owned by tinc, you could try
something like this :
ip r a 192.168.2.0/24 dev nb003004
This will send all traffic destined to 192.168.2.0/24 via the tinc
interface. Tinc will use his internal routing table to route the
traffic to the remote node that own the subnet 192.168.2.0. (send
signal USR2 on tinc deamon to dump internal network informations).
Cédric
Le 06/01/11 13:01, Perry Couprie a écrit :
Hi,
I have a routing problem.
When i start tinc it creates the following route in the main
routing table.
192.168.2.0/24 dev nb003004 proto kernel scope link src
192.168.2.8
The problem is that i want to use extra routing tables for each
tinc vpn.
When i set the netmask for the tinc device to 255.255.255.255.
The route is not created, how can i add it to a another route
table.
Setting a new route in the extra table is no problem:
ip route add table company10703004 10.0.0.0/24 via 192.168.2.7
But how can i add the routing for the tinc device to
company10703004 routing table.
The following does not work:
ip route add table company10703004 192.168.2.0/24 via 192.168.2.8
ip route add table company10703004 10.0.0.0/24 via 192.168.2.7
ip route add table company10703004 10.0.11.0/24 via 192.168.2.9
Greeting and best wishes for 2011,
Perry
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
--
Cédric
Lemarchand
52 avenue
de l'Europe
78160 Marly-le-Roi
France
Tel. +33
(0)1 30 08 88 88
Cell. +33 (0)6 37 23 40 93
|
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
