On Thu, Jan 06, 2011 at 09:11:04PM +0100, Perry Couprie wrote: > On 01/06/2011 01:48 PM, ZioPRoTo (Saverio Proto) wrote: > >>But how can i add the routing for the tinc device to company10703004 routing > >>table. > >you need to set up some policy with "ip rule" to make the desired > >traffic match that extra table
Saverio is right that you need to use "ip rule" in conjunction with "ip route
add table ..." before it makes any sense.
> I have two company tinc vpns. Each company has a tinc interface and 1 or more
> eth devices. For example:
>
> company01: tinc01 and eth0,eth1
> company02: tinc02 and eth2,eth3
>
> With default routing the 2 company networks can connect to each
> other networks.
> By using the extra routing tables i want to prevent that.
>
> Is that possible and can some one give me a hint where to look.
Isn't that better solved by adding an iptables rule that blocks forwarding
between tinc01 and the unwanted eth interface?
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@tinc-vpn.org>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list tinc@tinc-vpn.org http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
