Debian LXC: Instalacija openvpn-server-a

[dropbear]

Instalacija container-a je ista kao kod Debian: Instalacija LXC.
Znači kad instalirate container počinjemo sa promenama.
Naš container ima naziv: openvpn-server
Koristićemo isti bridge na HOST server kao kod Debian: Instalacija LXC.

Sada ćemo napraviti openvpn-server container.

root:

lxc-create -n openvpn-server -t debian -- -r jessie

Kao root otvorite ovaj fajl i editujte ga /var/lib/lxc/openvn-server/config.

root:

nano /var/lib/lxc/openvpn-server/config

Tamo gde piše lxc.network.type=none promeniti da izgleda kao ispod

lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.ipv4 = 192.168.22.8/24 192.168.22.255
lxc.network.ipv4.gateway = 192.168.22.1

Sada je još potrebno promeniti još jedan konfiguracijski fajl na vašem container-u a nalazi se ovde /var/lib/lxc/openvn-server/rootfs/etc/network/interfaces

root:

nano /var/lib/lxc/openvpn-server/rootfs/etc/network/interfaces

Posle editovanja mora da izgleda ovako:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

Na HOST serveru editovaćemo fajl /etc/sysctl.conf

root:

nano /etc/sysctl.conf

#net.ipv4.ip_forward=1

Da izgleda ovako, sklonili smo tarabu ili ti hashtag(eng)

net.ipv4.ip_forward=1

Restartujte server.

Startujemo openvpn-server.

root:

lxc-start -n openvpn-server -d

Kod prvog startovanja na kraju inicializacije napisaće i lozinku ali je mi nećemo koristiti jer ćemo napraviti svoju sa ovim ukazom.

root:

chroot /var/lib/lxc/openvpn-server/rootfs passwd

Da bi se konektovali sa vašim container-om upišite sledeći ukaz.

root:

lxc-attach -n openvpn-server

Došlo je vreme da instaliramo openvpn-server.

root:

apt-get update && apt-get upgrade
apt-get install openvpn libssl-dev openssl easy-rsa
make-cadir /etc/openvpn/easy-rsa

Editujemo fajl /etc/openvpn/easy-rsa/vars

root:

nano /etc/openvpn/easy-rsa/vars

Promenimo ove parametre na fajlu:

export KEY_COUNTRY="RS" ## Država
export KEY_PROVINCE="Palilula" ## ovde stavite šta hoćete
export KEY_CITY="Belgrade" ## ili vaš grad
export KEY_ORG="dropbear" ## Vaša organizacija, vaš izbor
export KEY_EMAIL="[email protected]" ##  vaš email

Sada generišemo ključeve sa ovim ukazima.

root:

cd /etc/openvpn/easy-rsa/
source vars
./clean-all
./build-dh
./pkitool --initca
./pkitool --server server
cd keys
openvpn --genkey --secret ta.key

Sada kopiramo ključeve u /etc/openvpn direktorij.
Napomena: Da bi kopirali ključeve morate biti u direktorijumu /etc/openvpn/easy-rsa/

root:

cp server.crt server.key ca.crt dh2048.pem ta.key /etc/openvpn/

Napravićemo još ključeve za korisnike.

root:

cd /etc/openvpn/easy-rsa/ 
source vars
./pkitool vaše ime korinika ## npr. dropbear-korisnik

Sa tim ukazom smo napravili vaše ime kornika.crt i vaše ime korisnika.key
Napravićemo još dva male scripte. Jedna je kad se startuje openvn-server druga kod stopiranja openvn-server-a.

root:

nano /etc/openvpn/up.sh

Kopirajte ovo:

#!/bin/sh
BR=$1
DEV=$2
MTU=$3
/sbin/ifconfig $DEV mtu $MTU promisc up
/sbin/brctl addif $BR $DEV

i za stop openvn-server-a

root:

nano /etc/openvpn/down.sh

Kopirajte ovo:

#!/bin/sh
BR=$1
DEV=$2
/sbin/brctl delif $BR $DEV
/sbin/ifconfig $DEV down

Napravićemo još da skripte može da startuje root.

root:

chmod 755 /etc/openvpn/down.sh

root:

chmod 755 /etc/openvpn/up.sh

Da bi imali manje problema i još više editovanja, kopirajte ovaj ukaz.

root:

cp /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz /etc/openvpn/

Znači koristićemo prednastavljeni fajl koji je došao sa openvpn.

root:

gzip -d /etc/openvpn/server.conf.gz

Otvorite fajl /etc/openvpn/server.conf

root:

nano /etc/openvpn/server.conf

I neka izgleda ovako, kao ovaj fajl ispod:

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
;dev tun
dev tap0

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca /etc/openvpn/ca.crt
cert /etc/openvpn/server.crt
key /etc/openvpn/server.key  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys. 
dh /etc/openvpn/dh2048.pem

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
;server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
server-bridge 192.168.22.8 255.255.255.0 192.168.22.90 192.168.22.95

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
push "route 192.168.22.1 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 192.168.22.1"
push "dhcp-option DNS 8.8.8.8"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth /etc/openvpn/ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
up "/etc/openvpn/up.sh br0"
down "/etc/openvpn/down.sh br0"
script-security 3

Kopirajte ove ključeve jer će vam trebati za korinika.

/etc/openvpn/ca.crt
/etc/openvpn/ta.key
/etc/openvpn/easy-rsa/keys/vaše ime koristika.crt
/etc/openvpn/easy-rsa/keys/vaše ime koristika.key

Kod pravljenja config fajla za korisnika ja koristim ključeve već u konfiguraciji.
Napomena: Ovi ključi nisu tačni, vaši će sigurno biti duži jer je ovo samo primer.
Moja konfiguracija izgleda ovako:

client
dev tap
proto udp
remote ## vaša statična ip adresa ## 1194
resolv-retry infinite
nobind
persist-key
persist-tun
<ca>
-----BEGIN CERTIFICATE-----
MIIE7jCCA9agAwIBAgIJAOoIC1Z1KoyOMA0GCSqGSIb3DQEBCwUAMIGqMQswCQYD
VQQGEwJTSTESMBAGA1UECBMJUHJpbW9yc2thMRMwEQYDVQQHEwpBamRvdnNjaW5h
MREwDwYDVQQKEwhkcm9wYmVhcjERMA8GA1UECxMIZHJvcGJlYXIxFDASBgNVBAMT
C2Ryb3BiZWFyIENBMRAwDgYDVQQpEwdFYXN5UlNBMSQwIgYJKoZIhvcNAQkBFhVk
ZXZudWxsLnM3MUBnbWFpbC5jb20wHhcNMTcwMTExMTgzNjAwWhcNMjcwMTA5MTgz
NjAwWjCBqjELMAkGA1UEBhMCU0kxEjAQBgNVBAgTCVByaW1vcnNrYTETMBEGA1UE
BxMKQWpkb3ZzY2luYTERMA8GA1UEChMIZHJvcGJlYXIxETAPBgNVBAsTCGRyb3Bi
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
MIIFTjCCBDagAwIBAgIBAzANBgkqhkiG9w0BAQsFADCBqjELMAkGA1UEBhMCU0kx
EjAQBgNVBAgTCVByaW1vcnNrYTETMBEGA1UEBxMKQWpkb3ZzY2luYTERMA8GA1UE
ChMIZHJvcGJlYXIxETAPBgNVBAsTCGRyb3BiZWFyMRQwEgYDVQQDEwtkcm9wYmVh
ciBDQTEQMA4GA1UEKRMHRWFzeVJTQTEkMCIGCSqGSIb3DQEJARYVZGV2bnVsbC5z
NzFAZ21haWwuY29tMB4XDTE3MDExMTE4NTUyN1oXDTI3MDEwOTE4NTUyN1owgasx
CzAJBgNVBAYTAlNJMRIwEAYDVQQIEwlQcmltb3Jza2ExEzARBgNVBAcTCkFqZG92
c2NpbmExETAPBgNVBAoTCGRyb3BiZWFyMREwDwYDVQQLEwhkcm9wYmVhcjEVMBMG
A1UEAxMMY2xpZW50LWVyaWthMRAwDgYDVQQpEwdFYXN5UlNBMSQwIgYJKoZIhvcN
AQkBFhVkZXZudWxsLnM3MUBnbWFpbC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQCz97woyKyAt3CyFZHeeE7axztZCd+UDOCvvrpQqVMgtBaVPxY+
awy9bq7+YBoD9H3wZGfvjrMxmy9hAflggs309MJ8lvJ3a4KeL2LzkomPVKMYHFu3
yWOlmAFJjx518NmNDf9YPrPoEGzxkKFD4IjVoBu0Di4AlayklI6GN6NpBGnM4yDv
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
MIIEwAIBADANBgkqhkiG9w0BAQEFAASCBKowggSmAgEAAoIBAQCz97woyKyAt3Cy
FZHeeE7axztZCd+UDOCvvrpQqVMgtBaVPxY+awy9bq7+YBoD9H3wZGfvjrMxmy9h
Aflggs309MJ8lvJ3a4KeL2LzkomPVKMYHFu3yWOlmAFJjx518NmNDf9YPrPoEGzx
kKFD4IjVoBu0Di4AlayklI6GN6NpBGnM4yDv8ns9kGTNOt97Uzrn4UnRwYxRfgPY
mYZ934/eNBGnRVOffCWx7D2/jYPbp51cueEcgNifZwQaLaN7tuEfaHM+wAV3v3u5
ou6YcmRsvnsJssOugOBsmG/KcjvH6bEAmVwv8WLeAHCkHQ5BLfIp9/GnaELBDQuU
-----END PRIVATE KEY-----
</key>
remote-cert-tls server
tls-client
tls-auth ta.key 1
comp-lzo
verb 3

Znači kopiram ključeve u konfiguraciju vaše ime korinika.ovpn.
Tamo gde piše <ca> kopiram ca.crt
Tamo gde piše <cert> kopiram vaše ime korisnika.crt
Tamo gde piše <key> kopiram vaše ime korisnika.key

Sada imamo samo dva fajla, vaše ime korisnika.ovpn i ta.key koji kopirate u C:\Program Files\OpenVPN\config

Napomena: Nemojte da probate da se povežete iz lokalne mreže jer neće raditi. Idite do kafića sa laptopom i probajte.

Ja uvek instaliram openssl-server i povezem se preko putty zbog lakseg editovanja.
Kod linux-a je dosta jednostavnije, otvorite konzolu i pišite

ssh vaš[email protected]

Sad je još potrebno da startuje openvpn-server.

root:

systemctl enable [email protected]
systemctl start [email protected]

Pogledajte još status server-a da li je vaš openvpn-server startovao bez greške:

root:

systemctl status [email protected] -l

Na HOST server-u dodamo u /etc/hosts

nano /etc/hosts

192.168.22.8 openvpn-server

Da bi startovali LXC container kod starta vašeg HOST servera dodajte u /var/lib/lxc/openvn-server/config.

root:

nano /var/lib/lxc/openvn-server/config

Dodajte na kraju config fajla.

## for openvpn
lxc.mount.entry = /dev/net dev/net none bind,create=dir
lxc.cgroup.devices.allow = c 10:200 rwm

# Autostart
lxc.start.auto = 1
lxc.start.delay = 5

Da bi sve to radilo morate na vašem routeru da otvorite port 1194 udp.
Ako nemate statičnu ip adresu, probajte no-ip servis ili neki sličan.

Unapred se izvinjujem za gramatične greške. Godinama sam u inostranstvu. Novi jezik nisam naučio a Srpski sam zaboravio. LOL

Ako imate neko pitanje, tu sam da pomognem.