Acces au lan via OPENVPN

Résolu/Fermé
Signaler
-
Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
-
Bonjour

J'ai monté un serveur OPENVPN sur mon hyperviseur (windows) pour permettre a un autre serveur distant de se connecter a celui ci

Le vpn entre le serveur distant et l'hyperviseur fonctionne,
J'ai donné en Reseau VPN le subnet 192.168.200.0/24

Mon hyperviseur a l'adresse 192.168.200.1
Mon serveur distant a l'adresse 192.168.200.6

L'un et l'autre se ping correctement

En revanche, j'aimerais depuis mon serveur distant, avoir acces au LAN de mon hyperviseur qui est en 192.168.100.0/24

Et c'est ici que ça bloque

Sur mon serveur openvpn, j'ai ajouté

push "route 192.168.100.0 255.255.255.0"


Voici un route print depuis mon serveur distant :
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric

127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.100.0 255.255.255.0 On-link 192.168.100.4 261
192.168.100.0 255.255.255.0 192.168.200.1 192.168.100.6 21
192.168.100.0 255.255.255.0 192.168.100.5 192.168.100.6 276


Voici un route print depuis mon HyperV (serveur OVPN) :

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric

127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
192.168.100.0 255.255.255.0 On-link 192.168.100.2 271
192.168.100.0 255.255.255.0 On-link 192.168.100.1 36
192.168.100.0 255.255.255.0 192.168.100.2 192.168.100.1 35
192.168.100.0 255.255.255.252 On-link 192.168.100.1 291


Je dois oublier quelquechose mais je ne vous pas quoi

Merci d'avance
Max
A voir également:

2 réponses

Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
13 389
Salut,
sauf si j'ai mal lu les route print,
tu as le même LAN 192.168.100.0/24 des deux côtés, si c'est le cas, il faut renuméroter l'un des deux en 192.168.101.0/24, le plus petit de préférence.
Ou si tu dois avoir le même réseau IP des deux côtés, configurer openvpn en mode pont au lieu de routeur (interface TAP au lieu de TUN).
De plus ce genre de routes:
192.168.100.0 255.255.255.0 192.168.100.5 192.168.100.6 276
192.168.100.0 255.255.255.0 192.168.100.2 192.168.100.1 35
ça ne peut pas fonctionner, je me demande comment windows fait pour accepter ça.
1
Merci pour la réponse rapide
En effet je veux avoir le meme lan d'un coté et de l'autre
J'ai changé mon serveur.ovpn en mettant tap au lieu de tun mais il me manque maintenant des arguments

(Pour les autres routes je les ai virées, c'était des tentatives désespérées on va dire)

Voici pour l'instant le bout de ma conf serveur.ovpn qui nous interesse
# 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 192.168.100.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.100.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


Je me loupe quelquepart ? ou bien le souci est ailleurs ?
0
Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
13 389
Tu peux enlever le push route en bridge.
Tu as cet exemple, je n'ai pas d'openvpn en bridge chez moi, désolé, il faudrait que je maquette, c'est du temps à prendre sur le reste.
0
Merci beaucoup
Je me connecte a nouveau

Par contre, a nouveau j'ai accès au serveur auquel je suis directement connecté (entre le serveur distant et mon hyperviseur), en revanche, je ne ping pas ma VM qui est pourtant dans le même résaux local que mon hyperviseur

Conf de mon serveur distant :
Windows IP Configuration
Ethernet adapter vEthernet (VLAN ajouté en ip fixe):

Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.100.40
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.2

Ethernet adapter Ethernet 3 (auto par OVPN):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::a4aa:f12a:f65e:f5f1%16
IPv4 Address. . . . . . . . . . . : 192.168.100.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Conf de mon hyperviseur :
Ethernet adapter vEthernet (LAN ajouté en ip fixe):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::3de0:a613:9552:be08%23
IPv4 Address. . . . . . . . . . . : 192.168.100.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :


Ethernet adapter Ethernet 3 (auto par OVPN) :

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::8cc3:cc0f:fc69:7400%9
IPv4 Address. . . . . . . . . . . : 192.168.100.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Conf de ma machine virtuelle :
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.100.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :192.168.100.2

Depuis mon serveur distant
Je ping vers le 192.168.100.1 uniquement
Je ne ping pas le 100.10 ni 100.4 (le tracert indique qu'il sort sur internet et se perd)

Depuis mon serveur HyperV
Je ping vers le 192.168.100.2 uniquement (et le 100.4 évidement)
Je ne ping pas le 100.40 (le tracert indique qu'il sort sur internet et se perd)

Depuis ma VM
Je ping vers le 192.168.100.10 uniquement

Tu vois une faute grossière ?
Merci encore !!!
0
Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
13 389 > Max
Tu peux mettre autre chose que 192.168.100.0/24 sur ton vpn ?
Du 10. Ketchose par exemple ?
Le pont ne semble pas fonctionner
0
J'ai tenté, les adresses fournies par OVPN sont maintenant en 192.168.10.x
Mais je ne ping pas mes adresses en 100.x et a la fois je trouve ça logique car je ne lui spécifie nulle part que j'ai un LAN en .100 et un en .10

Je loupe une étape de la conf ?

Je me permet de balancer l'énorme fichier server.ovpn
# Which local IP address should OpenVPN
# listen on? (optional)
;xx

# 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

# 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 "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\TAPHV01.crt"
key "C:\\Program Files\\OpenVPN\\config\\TAPHV01.key" # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh "C:\\Program Files\\OpenVPN\\config\\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 192.168.10.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.100.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 213.186.33.99"
;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
0
Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
13 389
Bien joué,
On passe en résolu alors ?
1
Je viens de voir que j'étais pas connecté
Je peux pas passer en résolu ducoup

Merci encore !
0
Messages postés
101905
Date d'inscription
lundi 16 juillet 2001
Statut
Membre
Dernière intervention
25 janvier 2022
13 389 > Max
OK,
je mets en résolu.
0