IPSEC: 3 Site-to-Site VPN's - Only 2 are working, keep getting IKE link timeout: state linking
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?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
When I check the syslog on the remote site, it gives the following error:This means cannot reach the other remote peer.
[IPSEC][L2L][1:Wessem-Out][@WAN IP] IKE link timeout: state linking
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.
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"
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial(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.
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.
I don't really understand why it's working now, but rebuilding my config (exactly the same) fixed this issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
2. Question - Are all routers directly connected to the internet without other devices between them? All with fixed IPs?