Prosíme přihlašte se nebo zaregistrujte.

Přihlašte se svým uživatelským jménem a heslem.
World of Warcraft

Novinky: Školení nejen k OS Ubuntu pro širokou veřejnost, více informací zde.

Autor Téma: Pomoc s nastavením OpenVPN  (Přečteno 423 krát)

milano-m2

  • Návštěvník
  • *
  • Příspěvků: 1
  • Karma: +0/-0
    • Zobrazit profil
Pomoc s nastavením OpenVPN
« kdy: 29 Červen 2017, 17:00:56 »
Zdravím, potřeboval bych pomoct s OpenVPN.
Snažím se to už pár dní rozchodit ,ale pořád narážím na nějaké chyby.
Použil jsem tento návod:    https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04#prerequisites  bez kroku 8, protože to neběhalo vůbec.
 
Takže mám síť 10.0.0.0/24, ap router s ip 10.0.0.1 a veřejnou IP na wan se zapnutým port forwarding 10.0.0.197:1194.
Server s ip 10.0.0.197 na kterém běží vsftpd, transmission a openvpn.

Po připojení klienta "z venku" běží internet, ale nelze se dostat na FTP a transmission.

Někde bude něco špatně, ale sítím moc nerozumím, tak jestli se můžete někdo mrknout....
Díky.

Kód: [Vybrat]
● openvpn@server.service - OpenVPN connection to server
   Loaded: loaded (/lib/systemd/system/openvpn@.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-06-29 16:09:43 CEST; 4min 16s ago
     Docs: man:openvpn(8)
           https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage
           https://community.openvpn.net/openvpn/wiki/HOWTO
  Process: 4728 ExecStart=/usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn --config /etc/openvpn/s
 Main PID: 4730 (openvpn)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/system-openvpn.slice/openvpn@server.service
           └─4730 /usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn --config /etc/openvpn/server.co

čen 29 16:11:49 debian ovpn-server[4730]: client1/95.47.186.19:37770 MULTI: bad source address from client [10.0.0.191], packet dropped
čen 29 16:11:49 debian ovpn-server[4730]: client1/95.47.186.19:37770 MULTI: bad source address from client [10.0.0.191], packet dropped
čen 29 16:11:52 debian ovpn-server[4730]: client1/95.47.186.19:37770 PID_ERR replay-window backtrack occurred [7] [SSL-0] [0000000_000000_0000000
čen 29 16:11:53 debian ovpn-server[4730]: client1/95.47.186.19:37770 MULTI: bad source address from client [10.0.0.191], packet dropped
čen 29 16:11:53 debian ovpn-server[4730]: client1/95.47.186.19:37770 MULTI: bad source address from client [10.0.0.191], packet dropped
čen 29 16:12:01 debian ovpn-server[4730]: Float requested for peer 0 to 37.48.46.125:60290
čen 29 16:12:01 debian ovpn-server[4730]: peer 0 (client1) floated from 95.47.186.19:37770 to [AF_INET]37.48.46.125:60290
čen 29 16:12:39 debian ovpn-server[4730]: client1/37.48.46.125:60290 PID_ERR replay-window backtrack occurred [8] [SSL-0] [00000000_0001111111111
čen 29 16:13:45 debian ovpn-server[4730]: Float requested for peer 0 to 95.47.186.19:37770
čen 29 16:13:45 debian ovpn-server[4730]: peer 0 (client1) floated from 37.48.46.125:60290 to [AF_INET]95.47.186.19:37770

Kód: [Vybrat]
#################################################
# 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



#################################################
# 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 443
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


#################################################
# 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 ca.crt
cert server.crt
key server.key  # This file should be kept secret


#################################################
# Diffie hellman parameters.                    #
# Generate your own with:                       #
#   openssl dhparam -out dh2048.pem 2048        #
#################################################

dh dh2048.pem


#################################################
# Network topology                              #
# Should be subnet (addressing via IP)          #
# unless Windows clients v2.0.9 and lower have  #
# to be supported (then net30, i.e. a /30 per   #
# client) Defaults to net30 (not recommended)   #
#################################################

;topology subnet


#################################################
# 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 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100


####################################################
# 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.10.0 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 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"


##################################################
# 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 ta.key 0 # This file is secret
key-direction 0




##################################################
# Select a cryptographic cipher.                 #
# This config item must be copied to             #
# the client config file as well.                #
# Note that 2.4 client/server will automatically #
# negotiate AES-256-GCM in TLS mode.             #
# See also the ncp-cipher option in the manpage  #
##################################################

cipher AES-256-CBC
auth SHA256