Exactly, that does the trick! I think it should become part of the
documentation, shouldn't it?
Add the line
echo 1 /proc/sys/net/ipv4/ip_forward
to every host running tinc and serving part of the vpn.
Thanks all for your kind help.
And, of course, thanks to Guus and Ivo for this gem.
Sorry, got distracted.
I wanted to say
Add the line
echo 1 /proc/sys/net/ipv4/ip_forward
to tinc-up and
echo 0 /proc/sys/net/ipv4/ip_forward
to tinc-down on every host running tinc and serving part of the vpn.
Ulli
2010/9/14 albi a...@albi.life.de:
To be honest, I don't know. I don't
On Wed, 15 Sep 2010, Peter Meier wrote:
I wanted to say
Add the line
echo 1 /proc/sys/net/ipv4/ip_forward
to tinc-up and
echo 0 /proc/sys/net/ipv4/ip_forward
to tinc-down on every host running tinc and serving part of the vpn.
Note:
Don't do the echo 0 on tinc-hosts which are also
Correct. I was looking from my point of view. Here all computers
of a subnet have only access to the VPN or are strictly local.
Cheers
Ulli
2010/9/15 Sven-Haegar Koch hae...@sdinet.de:
On Wed, 15 Sep 2010, Peter Meier wrote:
I wanted to say
Add the line
echo 1
2. idea: Did you avtivate routing/forwarding on thor?
To be honest, I don't know. I don't have the routing tables handy right now,
but what do you mean exactly? What do I have to check? Do you have
an example for it?
2010/9/14 albi a...@albi.life.de:
On Tue, 14 Sep 2010 14:26:10 +0200, Peter
To be honest, I don't know. I don't have the routing tables handy right
now,
but what do you mean exactly? What do I have to check? Do you have
an example for it?
You must activate forwaring on a computer to act as a router between the
two interfaces.
Linux:
