Help with initial setup
-
- OpenVpn Newbie
- Posts: 1
- Joined: Wed Sep 18, 2013 1:39 pm
Help with initial setup
I can not find much documentation. I am trying to setup the Openvpn server to pull dhcp from domian controler and it wont. Also i am trying to setup groups to only allow access to certain networks/hosts and it will not work it allows access to whatever is set as main and doesnt use the group acl settings. Please point me in right direction. We need a new software base for our remote access. Also is it capable of being setup as a L2TP server? so we dont have to use the openvpn client? Would like to use windows built in setup if possible.
-
- OpenVPN User
- Posts: 31
- Joined: Sun Sep 08, 2013 8:05 pm
Re: Help with initial setup
I am not sure about the L2TP - my guess is not. It sounds like you are trying to make the connection process easy to manage from a client perspective insofar that there is little or no installation required for a new client?
http://openvpn.net/index.php/open-sourc ... ility.html
You can push dhcp options to clients - but I am not sure this is exactly what you want (see url below). Do you want them on the same subnet as your remote network?
http://openvpn.net/index.php/open-sourc ... howto.html
You definitely can setup different groups to have different access levels. I use the --client-config-dir option to point to a directory that contains configuration extensions based on the client that is connecting (you put files in the directory with configuration directives named the common name of the client - same as the name in their certificate). Combining that with a firewall on the server you can control access based on the client. If you need something more integrated, you can build these configurations when the client connects using a script.
http://openvpn.net/index.php/open-sourc ... ility.html
You can push dhcp options to clients - but I am not sure this is exactly what you want (see url below). Do you want them on the same subnet as your remote network?
http://openvpn.net/index.php/open-sourc ... howto.html
You definitely can setup different groups to have different access levels. I use the --client-config-dir option to point to a directory that contains configuration extensions based on the client that is connecting (you put files in the directory with configuration directives named the common name of the client - same as the name in their certificate). Combining that with a firewall on the server you can control access based on the client. If you need something more integrated, you can build these configurations when the client connects using a script.