Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Pozostałe kwestie techniczne (sprzętowe i programowe) dotyczące internetu radiowego - np. konfiguracja firewalli, antywirusów, przeglądarek internetowych.

Moderator: Moderatorzy

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-12, 09:19

Witajcie,
trafiłem na to forum przekopując internet by spróbować rozwiązać mój problem.
A więc do rzeczy:
Byłem (albo jeszcze jestem) nieszczęśliwym posiadaczem neostrady 20 (20 tylko z nazwy). Jaka była ale miała otwarte porty i publiczne ip.
Wziąłem na testy T mobile internet domowy 60. Fajnie działa ale niestety nie ma możliwości uzyskania publicznego ip.
Trochę lipa.
Posiadam w domu server Synology 215j i na nim transmission- na neo jakoś to działało. Pobieranie i sedd chodziło dość dobrze przy tym łączu.
A usłudze od T mobile mam problem z wysyłem a status portu mam closed.
Wertując wasze forum wyczytałem żeby postawić vps na nim centosa i vpn i zrobić tunel.
Fajnie się czyta ale działa już dużo mniej.
Całą sobotę walczyłem i udało mi się na arubie postawić vps na nim systam centos 7 i zdalny pulpit.
Dalej już nie umiem i nie rozumiem co , gdzie zainstalować i jak skonfigurować.
A może po prostu nie ma możliwości otworzyć (przekierować , tunelować) portów w ten sposób?
Był bym wdzięczny za sugestię i rady.

Awatar użytkownika
wojteks
*** Administrator ***
Posty: 21993
Rejestracja: 2007-12-02, 11:51
Lokalizacja: Krosno

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: wojteks » 2017-12-12, 09:56

Ale gdzie ten CentOS będzie postawiony? W tej samej sieci domowej?
Nie pomagam na PW!
Wyszukiwarka usług szerokopasmowych viewtopic.php?f=30&t=55724

key
*Mistrz bezprzewodowy*
Posty: 8945
Rejestracja: 2010-08-01, 18:30
Lokalizacja: Nürnberg

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: key » 2017-12-12, 10:31

VPN sluzy do polaczenia sie z serwerem ktory ma interesujace Cie mozliwosci - n.p. otwarcie portow. Ten serwer musi byc umiejscowiony w internecie, nie w twojej sieci. Najprosciej jest chyba wykupic VPN u jakiegos zewnetrznego dostawcy.

Synology ma w swoim SW clientow VPN.

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-12, 13:45

wojteks pisze:Ale gdzie ten CentOS będzie postawiony? W tej samej sieci domowej?


Centos jest postawiony na płatnym serwerze aruba.
Na tym własnie serwerze vps chciałem postawić vpn i zrobić tunel z synology.


witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-12, 17:16

Ta procedura jest pewnie pod inne distro linuxa bo na centosa 7 nie wchodzą mi te komendy i nie pasują mi lokalizację plików.(No such file or directory)
A nie jestem specem w te klocki.

Awatar użytkownika
wojteks
*** Administrator ***
Posty: 21993
Rejestracja: 2007-12-02, 11:51
Lokalizacja: Krosno

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: wojteks » 2017-12-13, 07:16

Nie wiem czy wybór CentOSa był dobry, to system podobny do RedHata i odbiegający komendami od np. Debiana który pewnie w tym przykładzie z linku był użyty (ale nie jestem specem od linuxów więc bardziej nie pomogę).
Nie pomagam na PW!
Wyszukiwarka usług szerokopasmowych viewtopic.php?f=30&t=55724

key
*Mistrz bezprzewodowy*
Posty: 8945
Rejestracja: 2010-08-01, 18:30
Lokalizacja: Nürnberg

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: key » 2017-12-13, 08:41

Nie ma pakietow, poniewaz:
Before we start we'll need to install the Extra Packages for Enterprise Linux (EPEL) repository. This is because OpenVPN isn't available in the default CentOS repositories. The EPEL repository is an additional repository managed by the Fedora Project containing non-standard but popular packages.


Sprobuj ta strone:
https://www.digitalocean.com/community/tutorials/how-to-setup-and-configure-an-openvpn-server-on-centos-7

BTW: certyfikaty mozesz wygenerowac pod windowsem - wystarczy sciagnac i zainstalowac openVPN.

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-13, 13:08

Wczoraj trochę siedziałem nad tym i zainstalowałem openvpn wygenerowałem klucze ale i tak poległem.
Synology nie mógł się połączyć z vps. Rozumiem że na vps ma być server vpn a na synology klient tak?
Czy odwrotnie?
Dziś lub juto zrobię wszystko od nowa.

key
*Mistrz bezprzewodowy*
Posty: 8945
Rejestracja: 2010-08-01, 18:30
Lokalizacja: Nürnberg

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: key » 2017-12-13, 14:11

VPS ma byc serverem, Synology klientem.

Sprobuj najpierw z SW klienta na PC.

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-14, 20:05

Na ostatnim etapie konfigurowania opnvpn wywala mi przy poleceniu:

Kod: Zaznacz cały

systemctl start openvpn@server.service


Błąd:

Kod: Zaznacz cały

Job for openvpn@server.service failed because the control process exited with error code. See "systemctl status openvpn@server.service" and "journalctl -xe" for details.


Log:

Kod: Zaznacz cały

@witek80 keys]# systemctl status openvpn@server.service
● openvpn@server.service - OpenVPN Robust And Highly Flexible Tunneling Application On server
   Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since czw 2017-12-14 12:51:36 EST; 2min 24s ago
  Process: 6218 ExecStart=/usr/sbin/openvpn --cd /etc/openvpn/ --config %i.conf (code=exited, status=1/FAILURE)
 Main PID: 6218 (code=exited, status=1/FAILURE)

gru 14 12:51:36 witek80 systemd[1]: Starting OpenVPN Robust And Highly Flexible Tunneling Application On server...
gru 14 12:51:36 witek80 systemd[1]: openvpn@server.service: main process exited, code=exited, status=1/FAILURE
gru 14 12:51:36 witek80 systemd[1]: Failed to start OpenVPN Robust And Highly Flexible Tunneling Application On server.
gru 14 12:51:36 witek80 systemd[1]: Unit openvpn@server.service entered failed state.
gru 14 12:51:36 witek80 systemd[1]: openvpn@server.service failed.


Kod: Zaznacz cały

-- Subject: Jednostka openvpn@vpnname.service się nie powiodła
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Jednostka openvpn@vpnname.service się nie powiodła.
--
-- Wynik: failed.
gru 14 14:16:54 witek80 systemd[1]: Unit openvpn@vpnname.service entered failed state.
gru 14 14:16:54 witek80 systemd[1]: openvpn@vpnname.service failed.



Co poradzić?

key
*Mistrz bezprzewodowy*
Posty: 8945
Rejestracja: 2010-08-01, 18:30
Lokalizacja: Nürnberg

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: key » 2017-12-17, 10:07

Wstaw pliki konfiguracyjne serwera

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-18, 17:53

Postanowiłem zrobić vps od początku i już nie potrafie dojść do tego do czego doszedłem.
Czyli chociażby zdalny pulpit.
Wymiękam już. Prawie dwa tygodnie się już z tym męczę

witgit
Początkujący użytkownik forum
Posty: 11
Rejestracja: 2012-05-16, 13:36
Lokalizacja: kuj-pom

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: witgit » 2017-12-18, 20:48

Witam,
znowu wywala błędami:

Kod: Zaznacz cały

Dec 18 20:40:32 witek80 polkitd[696]: Registered Authentication Agent for unix-process:1967:422732 (system bus name :1.182 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/
Dec 18 20:40:32 witek80 systemd[1]: Starting OpenVPN Robust And Highly Flexible Tunneling Application On vpnname...
-- Subject: Unit openvpn@vpnname.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit openvpn@vpnname.service has begun starting up.
Dec 18 20:40:32 witek80 openvpn[1973]: Options error: In [CMD-LINE]:1: Error opening configuration file: vpnname.conf
Dec 18 20:40:32 witek80 openvpn[1973]: Use --help for more information.
Dec 18 20:40:32 witek80 systemd[1]: openvpn@vpnname.service: main process exited, code=exited, status=1/FAILURE
Dec 18 20:40:32 witek80 systemd[1]: Failed to start OpenVPN Robust And Highly Flexible Tunneling Application On vpnname.
-- Subject: Unit openvpn@vpnname.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit openvpn@vpnname.service has failed.
--
-- The result is failed.
Dec 18 20:40:32 witek80 systemd[1]: Unit openvpn@vpnname.service entered failed state.
Dec 18 20:40:32 witek80 systemd[1]: openvpn@vpnname.service failed.
Dec 18 20:40:32 witek80 polkitd[696]: Unregistered Authentication Agent for unix-process:1967:422732 (system bus name :1.182, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (dis
Dec 18 20:40:44 witek80 sshd[1965]: Received disconnect from 110.53.183.228 port 46387:11:  [preauth]
Dec 18 20:40:44 witek80 sshd[1965]: Disconnected from 110.53.183.228 port 46387 [preauth]
~



Pliki konfiguracyjne:
server.conf

Kod: Zaznacz cały

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

# 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
# ** Zabronione ** 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 ** Zabronione ** 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

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that v2.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

# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# 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 nobody

# 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

# Notify the client that when the server restarts so it
# can automatically reconnect.
;explicit-exit-notify 1


vars

Kod: Zaznacz cały

# easy-rsa parameter settings

# NOTE: If you installed from an RPM,
# don't edit this file in place in
# /usr/share/openvpn/easy-rsa --
# instead, you should copy the whole
# easy-rsa directory to another location
# (such as /etc/openvpn) so that your
# edits will not be wiped out by a future
# OpenVPN package upgrade.

# This variable should point to
# the top level of the easy-rsa
# tree.
export EASY_RSA="`pwd`"

#
# This variable should point to
# the requested executables
#
export OPENSSL="openssl"
export PKCS11TOOL="pkcs11-tool"
export GREP="grep"


# This variable should point to
# the openssl.cnf file included
# with easy-rsa.
export KEY_CONFIG=`$EASY_RSA/whichopensslcnf $EASY_RSA`

# Edit this variable to point to
# your soon-to-be-created key
# directory.
#
# WARNING: clean-all will do
# a rm -rf on this directory
# so make sure you define
# it correctly!
export KEY_DIR="$EASY_RSA/keys"

# Issue rm -rf warning
echo NOTE: If you run ./clean-all, I will be doing a rm -rf on $KEY_DIR

# PKCS11 fixes
export PKCS11_MODULE_PATH="dummy"
export PKCS11_PIN="dummy"

# Increase this to 2048 if you
# are paranoid.  This will slow
# down TLS negotiation performance
# as well as the one-time DH parms
# generation process.
export KEY_SIZE=2048

# In how many days should the root CA key expire?
export CA_EXPIRE=3650

# In how many days should certificates expire?
export KEY_EXPIRE=3650

# These are the default values for fields
# which will be placed in the certificate.
# Don't leave any of these fields blank.
export KEY_COUNTRY="US"
export KEY_PROVINCE="CA"
export KEY_CITY="SanFrancisco"
export KEY_ORG="Fort-Funston"
export KEY_EMAIL="me@myhost.mydomain"
export KEY_OU="MyOrganizationalUnit"

# X509 Subject Field
export KEY_NAME="server"

# PKCS11 Smart Card
# export PKCS11_MODULE_PATH="/usr/lib/changeme.so"
# export PKCS11_PIN=1234

# If you'd like to sign all keys with the same Common Name, uncomment the KEY_CN export below
# You will also need to make sure your OpenVPN server config has the duplicate-cn option set
# export KEY_CN="CommonName"

key
*Mistrz bezprzewodowy*
Posty: 8945
Rejestracja: 2010-08-01, 18:30
Lokalizacja: Nürnberg

Re: Tunel z Synology na vps przez b525s z t mobile - czy możliwy?

Postautor: key » 2017-12-18, 22:09

Brakuje Ci pliku konfiguracyjnego:

Dec 18 20:40:32 witek80 openvpn[1973]: Options error: In [CMD-LINE]:1: Error opening configuration file: vpnname.conf


Wróć do „Internet bezprzewodowy - pozostałe zagadnienia”

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 2 gości