The old way was to simple post a configuration:
# This is a comment
push "route 10.0.0.0 255.255.255.0" #My lan
server 10.3.0.0 255.255.255.0 #Vpn Lan
push "redirect-gateway def1"
push "dhcp-option DNS 123.123.220.220"
push "dhcp-option DNS 123.123.222.222"
;
;
dev tun0
proto udp
port xxxx
; there is a comment here, too
keepalive 10 120
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
management localhost 5001
With oconf, you can add a title and configuration content So, use something like the following:
Code: Select all
[oconf=Server Config]# This is a comment
push "route 10.0.0.0 255.255.255.0" #My lan
server 10.3.0.0 255.255.255.0 #Vpn Lan
push "redirect-gateway def1"
push "dhcp-option DNS 208.67.220.220"
push "dhcp-option DNS 208.67.222.222"
;
;
;
;
;
;
;
;
;
;
;
;
dev tun0
proto udp
port xxxx
; there is a comment here, too
keepalive 10 120
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
management localhost 5001[/oconf]
push "route 10.0.0.0 255.255.255.0" #My lan
server 10.3.0.0 255.255.255.0 #Vpn Lan
push "redirect-gateway def1"
push "dhcp-option DNS 208.67.220.220"
push "dhcp-option DNS 208.67.222.222"
;
;
;
;
;
;
;
;
;
;
;
;
dev tun0
proto udp
port xxxx
; there is a comment here, too
keepalive 10 120
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
management localhost 5001