Ciao tutti!
Non riesco a concludere positivamente una connessione in vpn tra il mio nuovo server vpn (il 7.4. sul quale e' installato il contrib OpenVPn ) ed il mio pc in ufficio sul quale ho installato OpenVPn per win xp.
Scenario:
Pc Lan Ufficio-openvpn client (172.16.X.XXX) --> FW --> Router Uff --> internet <-- Router casa (alice gate 2 plus wifi) <-- sme server (in modalita' srv+gw dove eth0(WAN)=192.168.1.2 gw=192.168.1.1 ed eth1(LAN)=172.16.X.XXY.
Ho messo il client in ufficio perche' tutto il traffico in uscita e' concesso, sul router casa e sullo sme server ho forwardato la porta 1194 (sia interna che esterna poiche' questo modem/router non permette l'apertura di un range di porte).
configurazione server:
========================================================
# at
http://www.contribs.org/development/#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
# Virtual Interface Configuration
port 1194
proto udp
dev tap0
# Drop down privileges
user nobody
group nobody
chroot /etc/openvpn/bridge
persist-key
persist-tun
# Certificates config
dh pub/dh.pem
ca pub/cacert.pem
cert pub/cert.pem
key priv/key.pem
tls-server
tls-auth priv/takey.pem 0
# CRL file for certificates verification
crl-verify pub/cacrl.pem
# Plugin for user-auth
# Server mode
server-bridge 172.16.X.XXX 255.255.255.0 172.16.5.155 172.16.5.160
# Options
keepalive 10 120
push "dhcp-option DOMAIN miodominio.com"
push "dhcp-option DNS 172.16.X.XXX"
push "dhcp-option WINS 172.16.X.XXX"
push "route 192.168.1.0 255.255.255.0 172.16.X.XXX"
mtu-test
reneg-sec 3600
nice 5
# Management interface
management localhost 11194 management-pass.txt
# Clients options
client-config-dir ccd
max-clients 20
comp-lzo
# Log
status-version 2
status bridge-status.txt
verb 3
===================================================
Configurazione client:
# 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 "OpenVPN"
# 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 miodominio.com 1194
# 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 clientmicuff.crt
key clientmicuff.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 key.txt 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
---------------------------------------------------------------------
ed ecco l'errorone:
TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
che significa tutto e niente...
premetto che la connettività lato client e server esiste ed e' perfettamente funzionante lato client traffico in uscita ok lato server forward richiesti effettuati.
Premetto che ho testato la connessione vpn client xp/vpn server sme virtuale utilizzanod lato cliente l'ip interno della lan del server ed il tunnel si e' instaurato correttamente.
Avete qualche prova da suggerirmi?
Oppure un alternativa per lavorare sullo sme di casa dall'uff
Grazie in anticipo a tutti!
Michele
ps:
il forward sul router va' fatto porta esterna 1194 su porta interna 1194 ?
o il client puo' tentare di entrare con una porta diversa dall 1194?
( dubbissimo da newbissimo
15 Replies
6440 Views