madsurfer Boulet's eradicator | Salut à tous,
J'essai de réaliser ce type de VPN
LAN 172.20.0.0/16 ---- Gate VPN ---- client_VPN 192.168.10.43/24
eth0 eth1
La passerelle VPN à 2 interfaces réseaux :
eth0 : 172.20.211.42/16
eth1 : 192.168.10.42/24
Le serveur VPN est un GNU/Linux Woody (kernel 2.4.20) sous Freeswan 1.99 et le client est un Win98 avec PGPnet 7.
Configuration de la passerelle VPN
----------------------------------
Code :
- vpnserver:~# cat /etc/ipsec.conf
- # /etc/ipsec.conf - FreeS/WAN IPsec configuration file
- # More elaborate and more varied sample configurations can be found
- # in FreeS/WAN's doc/examples file, and in the HTML documentation.
- # Essai
- config setup
- interfaces="ipsec0=eth0 ipsec1=eth1"
- klipsdebug=none
- plutoload=%search
- #klipsdebug=none
- #plutodebug=none
- #plutoload=%search
- plutostart=%search
- #uniqueids=yes
- #conn %default
- #keyungtries=0
- conn cl-se
- left=192.168.10.42
- leftsubnet=172.20.0.0/16
- leftid=@vpn.toto.lan
- right=192.168.10.43
- #rightnexthop=192.168.10.42
- rightid=@cli.toto.lan
- auto=add
|
Code :
- vpnserver:~# cat /etc/ipsec.secrets
- # This file holds shared secrets or RSA private keys for inter-Pluto
- # authentication. See ipsec_pluto(8) manpage, and HTML documentation.
- # RSA private key for this host, authenticating it to any other host
- # which knows the public part. Suitable public keys, for ipsec.conf, DNS,
- # or configuration of other implementations, can be extracted conveniently
- # with "ipsec showhostkey".
- 192.168.10.43 192.168.10.42 172.20.211.42 172.20.0.0 : PSK
- "Ma_belle_clef"
|
Est ce que la config du serveur VPN est bonne ?
Car je ne sais pas s'il y a des erreurs sur la passerelle VPN (freeswan) ou sur le client (PGPnet).
Merci de votre aide. Car je galère depuis pas mal de temps ! 
Voici les logs de FreeSwan (sur la passerelle VPN)
Code :
- Apr 1 11:39:08 vpnserver pluto[2365]: packet from 192.168.10.43:500: ignoring Vendor ID payload
- Apr 1 11:39:08 vpnserver pluto[2365]: "cl-se" #2: responding to Main Mode
- Apr 1 11:39:08 vpnserver pluto[2365]: "cl-se" #2: ignoring informational payload, type IPSEC_INITIAL_CONTACT
- Apr 1 11:39:08 vpnserver pluto[2365]: "cl-se" #2: no suitable connection for peer '192.168.10.43'
- Apr 1 11:39:10 vpnserver pluto[2365]: "cl-se" #2: ignoring informational payload, type IPSEC_INITIAL_CONTACT
- Apr 1 11:39:10 vpnserver pluto[2365]: "cl-se" #2: no suitable connection for peer '192.168.10.43'
- Apr 1 11:39:12 vpnserver pluto[2365]: "cl-se" #2: ignoring informational payload, type IPSEC_INITIAL_CONTACT
- Apr 1 11:39:12 vpnserver pluto[2365]: "cl-se" #2: no suitable connection for peer '192.168.10.43'
- Apr 1 11:39:16 vpnserver pluto[2365]: "cl-se" #2: ignoring informational payload, type IPSEC_INITIAL_CONTACT
- Apr 1 11:39:16 vpnserver pluto[2365]: "cl-se" #2: no suitable connection for peer '192.168.10.43'
- Apr 1 11:40:18 vpnserver pluto[2365]: "cl-se" #2: max number of retransmissions (2) reached STATE_MAIN_R2
|
Message édité par madsurfer le 01-04-2003 à 15:52:19
|
FORUM HardWare.fr
