I just tried to set up a tinc test installation, but I guess I did
something wrong, because I can only ping one direction.
Here's my setup
(lan1,192.168.99.0)<-->firewall1<-vpn->firewall2<-->(lan2,192.168.100.0)
firewall1 has tap0 on 192.168.88.2
firewall2 has tap0 on 192.168.88.3
i set up the following routes :
on firewall1 : 192.168.100.0 gw firewall2(192.168.88.3)
on firewall2 : 192.168.99.0 gw firewall1(192.168.88.2)
firewall2 is the "server" (does not connect) and firewall1 connects to
it.
A link is established on server start and I can ping the eth address
(192.168.100.1) of firewall2 from firewall1, but not the eth address of
fw1 from fw2.
If I switch fw1 to server and fw2 to client, it works the other way round.
The situation is though, that client can access server eth but server
cannot access client eth.
----------------------------------------------------------------------
Johannes Walch NWE Network-Engineering GmbH
Linux-Systemhaus
Wingertstr. 70/1
D-68809 Neulussheim
central: +49 (0) 6205 3090-0
e-mail: j.walch@nwe.de voice: +49 (0) 6205 3090-14
web: http://www.nwe.de fax: +49 (0) 6205 3090-29
----------------------------------------------------------------------
-
Tinc: Discussion list about the tinc VPN daemon
Archive: http://mail.nl.linux.org/lists/
Tinc site: http://ftp.nl.linux.org/pub/linux/tinc/
