|
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 12 December 2003 17:26, Marc Lentwojt wrote: > Hi, > > i think, the problem is, that sedi does not know, where ginas network can > be reached. You have to add the route for ginas network manually on sedi. > Try to add the following routes on sedi: > > > 10.0.0.4 via 10.0.0.1 > > and on ginas side: > > 10.0.0.2 via 10.0.0.3 > > Because gina reaches sedi via the tunnel-IP and vice versa. > > So it was on my setup :-)) I worked thank you very very much for your help greetings, chris - -- If it compiles, commit to CVS. If it links, ship to customer. It it runs without bugs, ..., nah, never had that case. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2hkCAgmexFOwd6YRAqixAJsHPGeqd1EDVCon/MsuV8XyTJsKBgCfdQRC j4wW4QNNnY95+YJwAiC5th8= =kXdL -----END PGP SIGNATURE----- ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |