> > > 1) Extend the current openvpn definition/instance to be either client >> > or server. >>> >>> 2) Create a new openvpn client definition/instance (openvpnclient) >>> that acts as a separate openvpn client, using OVPNC_* variables. >>> >>> >>> It is possible, currently, to define your own /mnt/kd/openvpn/ >>> openvpn.conf file configured as a client, superseding the OVPN_* >>> rc.conf variables. If this file exists, the web interface will prompt >>> the user to edit the file instead of showing the OpenVPN sub-tab. >>> >>> I know Darrick has a lot of experience with this, so I look forward to >>> his comments. >> >>Lonnie's description is accurate. If you need a client example, I can >>post one later. >> >>Darrick > >Thanks for your answers. > >@Darrick: It would be great if you could post an example. > >Michael
I got a working connection between both boxes by creating a "/mnt/kd/openvpn/openvpn.conf" with a client config now. One issue is, that I cannot reach the internal LAN on the client side from the server side. The internal LAN on the server is accessable. On both sides "Allow OpenVPN tunnel to the 1st LAN Interface" in the Firewall-Tab is checked. Another question: How is it possible to reach the client Astlinux box from "external" to remote administer it (over the tunnel)? It does not work, when I have another OpenVPN connection from "extern" to the server. The 2 VPN connections are not "bridged". Maybe that is normal. Michael ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
