IPSEC: 3 Site-to-Site VPN's - Only 2 are working, keep getting IKE link timeout: state linking
I'm fairly new to VPN services so I don't really know what's happening and why.
I am trying to connect 3 remote sites to HQ by using site-to-site VPN and have managed to get 2 working.
The 3th one won't come online and I cant really figure out why, I have used the exact same config on all 3 routers (Vigor2925) for Outbound connections (except for local subnet ofcourse) and the same inboud settings for HQ router (also Vigor2925).
When I check the syslog on the remote site, it gives the following error:
[IPSEC][L2L][1:Wessem-Out]
On HQ I keep getting this one:
Responding to Main Mode from <WAN IP REMOTE SITE>
Accept Phase1 prorosals : ENCR OAKLEY_DES_CBC, HASH OAKLEY_MD5
Can someone maybe explain what im doing wrong??
I am trying to connect 3 remote sites to HQ by using site-to-site VPN and have managed to get 2 working.
The 3th one won't come online and I cant really figure out why, I have used the exact same config on all 3 routers (Vigor2925) for Outbound connections (except for local subnet ofcourse) and the same inboud settings for HQ router (also Vigor2925).
When I check the syslog on the remote site, it gives the following error:
[IPSEC][L2L][1:Wessem-Out]
On HQ I keep getting this one:
Responding to Main Mode from <WAN IP REMOTE SITE>
Accept Phase1 prorosals : ENCR OAKLEY_DES_CBC, HASH OAKLEY_MD5
Can someone maybe explain what im doing wrong??
Who is Participating?
1. Question - Have all routers the same firmware?
2. Question - Are all routers directly connected to the internet without other devices between them? All with fixed IPs?
2. Question - Are all routers directly connected to the internet without other devices between them? All with fixed IPs?
IKE requires port 500/UDP should be allowed in a firewall.
(For NAT-T also allow 4500/UDP)
You say 3DES/MD5/DH2, but allowed is DES this is different. (btw,Phase 1 doesn't seem to be completed).
DES/3DES & MD5 should not be used anymore. Try AES-192 or AES-256 and SHA-1 or better for hashing.
DES is only 56bit keys, that is broken for about 15 years now. Colisions for MD5 can probably be generated in real time now.
3DES is more or less 112 bits of key material.
Also DH5 should be considered.
(For NAT-T also allow 4500/UDP)
You say 3DES/MD5/DH2, but allowed is DES this is different. (btw,Phase 1 doesn't seem to be completed).
DES/3DES & MD5 should not be used anymore. Try AES-192 or AES-256 and SHA-1 or better for hashing.
DES is only 56bit keys, that is broken for about 15 years now. Colisions for MD5 can probably be generated in real time now.
3DES is more or less 112 bits of key material.
Also DH5 should be considered.
@noci I'm agreed of what you are saying but everything depends on the model of the router he has.
Technically speaking, I'm guessing he's knows all that and I'm just giving him a general idea of what could it be.
And where to go.
Technically speaking, I'm guessing he's knows all that and I'm just giving him a general idea of what could it be.
And where to go.
Thanks for the advice people, it's been a couple of days but I've solved my issue.
I don't really understand why it's working now, but rebuilding my config (exactly the same) fixed this issue.
I don't really understand why it's working now, but rebuilding my config (exactly the same) fixed this issue.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
The HQ is saying I am responding to your request from your IP address and I am accpeting phase 1 of the negotiation.
But phase 2 is not taking action.
Makse sure you are using the same encryption method.
Encryption 3des
Hash MD5
Group 2
Authentication Pre-Shared key " this means password for negotiations between peers"