Hello

Pour faire court ,
Undo wrote:Peut-on faire écouter le même port à deux programmes différents ? Est-il possible de faire écouter un port apache (80 ou 443 notamment... )(avec apache lancé) à OpenVPN ?
Non c'est impossible de binder plus qu'un process sur un même port.

Par contre, une solution, c'est d'utiliser OpenVPN en mode UDP. Dans ce cas, oui, tu peux avoir OpenVPN en UDP/443 et Apache SSL en TCP/443.
C'est la seule solution que je vois. De plus, OpenVPN est vraiment très performant en UDP, puisqu'on s'affranchit de tous les mécanismes de reprises d'erreur de TCP.

A toi de choisir 🙂
hugsy_75 wrote:Hello

Pour faire court ,
Undo wrote:Peut-on faire écouter le même port à deux programmes différents ? Est-il possible de faire écouter un port apache (80 ou 443 notamment... )(avec apache lancé) à OpenVPN ?
Non c'est impossible de binder plus qu'un process sur un même port.

Par contre, une solution, c'est d'utiliser OpenVPN en mode UDP. Dans ce cas, oui, tu peux avoir OpenVPN en UDP/443 et Apache SSL en TCP/443.
C'est la seule solution que je vois. De plus, OpenVPN est vraiment très performant en UDP, puisqu'on s'affranchit de tous les mécanismes de reprises d'erreur de TCP.

A toi de choisir 🙂
C'est plus que parfait pourquoi moi.

On m'avait cependant dit que le TCP était plus rapide...

Je suppose qu'il est possible de faire la même chose sur le port 80 du coup.

Je vais tester dès que possible, je poste pour confirmer.


Merci à tous 😉
Ah bah nan =D

OpenVPN se lance bien sur le port 443 pas de pb... Mais impossible de connecter un client Windows (je vais essayer avec un Client Fedora on sait jamais)...

Même si je mets autre chose que le port 443, par exemple pour les tests j'utilise le port 8080 : en TCP OK, en UDP pas ok...

Le serveur reçoit bien la demande, mais la "poignée de main" échoue (TLS error, handshake failed). Alors qu'en TCP elle fonctionne.

Le client est bien passé en mode UDP aussi évidemment... Bizarre. (et je précise que le port est bien débloqué dans le routeur du client Windows)

edit : Exactement la même erreur (soft, tls-error, handshake failed) sous Fedora.
Je vous mets les sorties client / serveur si ça peut aider :

client (windows ou fedora, même sortie)
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Re-using SSL/TLS context
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: LZO compression initialized
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Local Options hash (VER=V4): '41690919'
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Expected Remote Options hash (VER=V4): '530fdded'
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: Socket Buffers: R=[124928->131072] S=[124928->131072]
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: UDPv4 link local: [undef]
Aug 26 07:59:18 Troll-Fedora openvpn[9228]: UDPv4 link remote: 188.165.44.16:8080
Aug 26 07:59:44 Troll-Fedora openvpn[9206]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Aug 26 07:59:44 Troll-Fedora openvpn[9206]: TLS Error: TLS handshake failed
Aug 26 07:59:44 Troll-Fedora openvpn[9206]: TCP/UDP: Closing socket
Aug 26 07:59:44 Troll-Fedora openvpn[9206]: SIGUSR1[soft,tls-error] received, process restarting
Aug 26 07:59:44 Troll-Fedora openvpn[9206]: Restart pause, 2 second(s)
serveur
Wed Aug 26 07:59:46 2009 us=344495 90.57.34.113:51495 TLS: Initial packet from 90.57.34.113:51495, sid=660d9e10 31280079
Wed Aug 26 08:00:18 2009 us=862062 90.57.34.113:46482 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Aug 26 08:00:18 2009 us=862166 90.57.34.113:46482 TLS Error: TLS handshake failed
Wed Aug 26 08:00:18 2009 us=862364 90.57.34.113:46482 SIGUSR1[soft,tls-error] received, client-instance restarting
Wed Aug 26 08:00:34 2009 us=598059 90.57.34.113:1373 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Aug 26 08:00:34 2009 us=598144 90.57.34.113:1373 TLS Error: TLS handshake failed
Wed Aug 26 08:00:34 2009 us=598337 90.57.34.113:1373 SIGUSR1[soft,tls-error] received, client-instance restarting
Edit 2 : J'en profite pour poser une autre question :

Ce server VPN va servir de passerelle vers Internet aux clients qui s'y connecteront. Actuellement, avec iptables désactivé ça fonctionne.

Cependant pour que le serveur soit protégé, toutes les connexions entrantes et sortantes sont par défaut refusées (avec un petit tas d'exceptions évidemment pour tous les services utilisés)... Sauf que j'imagine que cela va bloquer le traffic des clients du coup, refusant les connexions qu'ils demandent vers l'extérieur.

Mais je pense qu'on doit pouvoir dire à iptables "ne bloque pas les connexions venant de xxx ou créées par le processus xxxx" non ?
A mon avis c'est possible vu que ce j'ai déjà vu en configuration iptables... mais non seulement j'en suis pas certain à 100%, mais en plus je ne sais pas quels paramètres lui passer ^^
Bon, alors avec d'autres tests je suis tombé sur d'autres trucs encore plus bizarres...

Visiblement le port 8080 est filtré sur mon autre réseau. C'est assez étrange, j'ai ceci :


Connection established on XX.XXX.XXX.XX:8080
...
...
Error [soft, tls-failed] Handshake failed


Pourtant si je ne change rien du tout à la configuration mais que je vais sur un autre réseau, cela fonctionne.

J'ai essayé avec le port TCP 80 aussi (en virant Apache sur le serveur hôte) mais ça me dit pareil... pourtant OpenVPN écoute le bon port, et je peux utiliser le port TCP 80 à travers Firefox !! Une idée ?

SVP ça devient très pressant pour moi d'avoir le VPN fonctionnel...
Je ne perds pas espoir 😃
Si t'as un problème d'établissement de connexion TLS, ce n'est pas en rapport avec le numéro de port, tu peux donc utiliser 443/TCP ou 443/UDP.

2 questions :
- ton iptables est il actif côté serveur ? si oui, penses à vérifier les policies pour l'UDP
- si le problème ne vient pas d'iptables, donnes nous ton fichier de conf serveur et client
Non iptables inactif. C'est très bizarre comme je vous dis ça fonctionne quand je me connecte depuis un réseau standard, et pas depuis un autre réseau...

Sans parler de l'UDP qui ne fonctionne pas non plus...

Alors configuration serveur :
#################################################      
# 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 443                                                                                                                                                    
;port 1194                                                                                                                                                   
;port 8080                                                                                                                                                    

# 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 /etc/openvpn/ca.crt                              
cert /etc/openvpn/PCWVPN.crt                        
key /etc/openvpn/PCWVPN.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/dh1024.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                      
server 192.168.252.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 /etc/openvpn/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 208.67.222.222"     
;push "dhcp-option DNS 208.67.220.220"     

# 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          

# 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 openvpn
group openvpn

# 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 /etc/openvpn/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  /etc/openvpn/openvpn1.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 4

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
Configuration client (Windows) :
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# 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,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
;remote 90.29.8.214 143
;remote my-server-2 1194
remote 188.165.44.16 443

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
ca ca.crt
cert clientvpn.crt
key clientvpn.key

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server".  This is an
# important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server".  The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20
(Là c'est port 443, mais port 80 c'est idem, port 8080 aussi d'ailleurs, peu importe lequel au final)



Merci bien =)
5 jours plus tard
J'ai lu que le dernier post mais si y'a pas d'iptables sur la machine et que cela fonctionne en local cela veut dire que c'est le routeur qui redirige pas les ports vers la machine qui héberge le server.
Salut,

Merci pour ta réponse.

Ça m'étonnerait.

Avec OpenVPN en UDP, donc, ça ne fonctionne pas.

Mais Bind9 tourne sur le serveur, et donc sur le port UDP 43 et ça fonctionne parfaitement...

Non je n'ai pas testé UDP en local tiens... J'ai fait fonctionné le tout en TCP en local & remote. Donc j'ai pas re-testé l'UDP en local avant de tester en remote...

Peut-être je devrais, peut-être ça vient du client... Mais y'a toujours cette histoire de TCP qui fonctionne sur un réseau et pas l'autre...
un mois plus tard