Sauf que...
Impossible d'y accéder que ce soit en lt2p ou en openvpn.
Je cherche du coup les questions et avis d'un expert !
sudo ufw allow 1194
###############################################################################
# OpenVPN 2.0 Sample Configuration File
# !!! YOU HAVE TO REVIEW IT BEFORE USE AND MODIFY IT AS NECESSARY !!!
#
# However, before you try it, you should review the descriptions of the file
# to determine the necessity to modify to suitable for your real environment.
# If necessary, you have to modify a little adequately on the file.
# For example, the IP address or the hostname as a destination VPN Server
# should be confirmed.
#
# Note that to use OpenVPN 2.0, you have to put the certification file of
# the destination VPN Server on the OpenVPN Client computer when you use this
# config file. Please refer the below descriptions carefully.
###############################################################################
# Specify the type of the layer of the VPN connection.
#
# To connect to the VPN Server as a "Remote-Access VPN Client PC",
# specify 'dev tun'. (Layer-3 IP Routing Mode)
#
# To connect to the VPN Server as a bridging equipment of "Site-to-Site VPN",
# specify 'dev tap'. (Layer-2 Ethernet Bridgine Mode)
dev tun
###############################################################################
# Specify the underlying protocol beyond the Internet.
# Note that this setting must be correspond with the listening setting on
# the VPN Server.
#
# Specify either 'proto tcp' or 'proto udp'.
proto udp
###############################################################################
# The destination hostname / IP address, and port number of
# the target VPN Server.
#
# You have to specify as 'remote <HOSTNAME> <PORT>'. You can also
# specify the IP address instead of the hostname.
#
# Note that the auto-generated below hostname are a "auto-detected
# IP address" of the VPN Server. You have to confirm the correctness
# beforehand.
#
# When you want to connect to the VPN Server by using TCP protocol,
# the port number of the destination TCP port should be same as one of
# the available TCP listeners on the VPN Server.
#
# When you use UDP protocol, the port number must same as the configuration
# setting of "OpenVPN Server Compatible Function" on the VPN Server.
# Note: The below hostname is came from the Dynamic DNS Client function
# which is running on the VPN Server. If you don't want to use
# the Dynamic DNS hostname, replace it to either IP address or
# other domain's hostname.
remote vpn.trucmachin.net 1194
###############################################################################
# The HTTP/HTTPS proxy setting.
#
# Only if you have to use the Internet via a proxy, uncomment the below
# two lines and specify the proxy address and the port number.
# In the case of using proxy-authentication, refer the OpenVPN manual.
;http-proxy-retry
;http-proxy [proxy server] [proxy port]
###############################################################################
# The encryption and authentication algorithm.
#
# Default setting is good. Modify it as you prefer.
# When you specify an unsupported algorithm, the error will occur.
#
# The supported algorithms are as follows:
# cipher: [NULL-CIPHER] NULL AES-128-CBC AES-192-CBC AES-256-CBC BF-CBC
# CAST-CBC CAST5-CBC DES-CBC DES-EDE-CBC DES-EDE3-CBC DESX-CBC
# RC2-40-CBC RC2-64-CBC RC2-CBC
# auth: SHA SHA1 MD5 MD4 RMD160
cipher AES-128-CBC
auth SHA1
###############################################################################
# Other parameters necessary to connect to the VPN Server.
#
# It is not recommended to modify it unless you have a particular need.
resolv-retry infinite
nobind
persist-key
persist-tun
client
verb 3
auth-user-pass
###############################################################################
# The certificate file of the destination VPN Server.
#
# The CA certificate file is embedded in the inline format.
# You can replace this CA contents if necessary.
# Please note that if the server certificate is not a self-signed, you have to
# specify the signer's root certificate (CA) here.
<ca>
-----BEGIN CERTIFICATE-----
Lorem Ipsum et tout
-----END CERTIFICATE-----
</ca>
<ca>
-----BEGIN CERTIFICATE-----
bla bla bla
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
bla bla bla
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN RSA PRIVATE KEY-----
bla bla bla
-----END RSA PRIVATE KEY-----
</key>
To: arch-announce@archlinux.org
Subject: [arch-announce] OpenVPN 2.4.0 update requires administrative
interaction
Message-ID: <mailman.2.1483099201.4211.arch-announce@archlinux.org>
Content-Type: text/plain; charset="us-ascii"
The upgrade to OpenVPN 2.4.0 makes changes that are incompatible with previous
configurations. Take **special care** if you depend on VPN connectivity for
**remote access**! Administrative interaction is required:
* Configuration is expected in sub directories now. Move your files from
`/etc/openvpn/` to `/etc/openvpn/server/` or `/etc/openvpn/client/`.
* The plugin lookup path changed, remove extra `plugins/` from relative paths.
* The systemd unit `openvpn@.service` was replaced with `openvpn-
client@.service` and `openvpn-server@.service`. Restart and reenable
accordingly.
This does not affect the functionality of `networkmanager`, `connman` or
`qopenvpn`.
URL: https://www.archlinux.org/news/openvpn-240-update-requires-administrative-interaction/
openvpn --config tralala.ovpn