Ik heb dus een Freeswan linux server en een winXP client. Ik heb de freeswan install gepatched met x.509. Het probleem wat is heb is dat ik de melding "no suitable connection to peer" krijg. Hieronder een uitgebreider log
Het volgende heb ik er over kunnen vinden in de FAQ van Frees/Wan:
Maar waarom werkt het dan nog niet????
Hier nog m`n ipsec.conf
Wie kan mij helpen? Thnx.
code:
1
2
3
4
5
6
7
8
9
10
| Aug 19 14:56:11 Debian pluto[269]: packet from 213.194.1.179:500: ignoring Vendor ID payload Aug 19 14:56:11 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: responding to Main Mode from unknown peer 213.194.1.179 Aug 19 14:56:13 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: Peer ID is ID_DER_ASN1_DN: 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=aa, E=aa@aa.nl' Aug 19 14:56:13 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: no suitable connection for peer 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2,E=aa@aa.nl' Aug 19 14:56:14 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: Peer ID is ID_DER_ASN1_DN: 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2, E=aa@aa.nl' Aug 19 14:56:14 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: no suitable connection for peer 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2,E=aa@aa.nl' Aug 19 14:56:16 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: Peer ID is ID_DER_ASN1_DN: 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2,E=aa@aa.nl' Aug 19 14:56:16 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: no suitable connection for peer 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2, E=aa@aa.nl' Aug 19 14:56:20 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: Peer ID is ID_DER_ASN1_DN: 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2, E=aa@aa.nl' Aug 19 14:56:20 Debian pluto[269]: "roadwarrior"[1] 213.194.1.179 #1: no suitable connection for peer 'C=NL, ST=NH, L=aa, O=aa, OU=TD, CN=Flappie2, E=aa@aa.nl' |
Het volgende heb ik er over kunnen vinden in de FAQ van Frees/Wan:
Die ID komt netjes aan, inclusief alle gegevens. Kortom het certificaat is ook goed geinstalleerd. De naam Flappie2 zit nml in het certificaat ingebakken...When a connection is initiated by the peer, Pluto must choose which entry in the conf file best matches the incoming connection. A preliminary choice is made on the basis of source and destination IPs, since that information is available at that time.
A payload containing an ID arrives later in the negotiation. Based on this id and the *id= parameters, Pluto refines its conn selection. ...
The message "no suitable connection" indicates that in this refining step, Pluto does not find a connection that matches that ID.
Maar waarom werkt het dan nog niet????
Hier nog m`n ipsec.conf
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
| # /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.
# basic configuration
config setup
# THIS SETTING MUST BE CORRECT or almost nothing will work;
# %defaultroute is okay for most simple cases.
interfaces=%defaultroute
# Debug-logging controls: "none" for (almost) none, "all" for lots.
klipsdebug=none
plutodebug=none
# Use auto= parameters in conn descriptions to control startup actions.
plutoload=%search
plutostart=%search
# Close down old connection when new one using same ID shows up.
uniqueids=yes
conn %default
keyingtries=1
compress=yes
disablearrivalcheck=no
authby=rsasig
leftrsasigkey=%cert
rightrsasigkey=%cert
conn roadwarrior
right=%any
left=111.11.11.111
leftsubnet=10.1.0.0/24
leftcert=host.example.com.pem
rightcert=winhost.example.com.pem
auto=add
pfs=yes |
Wie kan mij helpen? Thnx.