We're trying to setup a VPN between a PIX and an ASL 1.822 box.
The config options on the ASL seem accurate, and match the other (ASL-ASL) VPN's we have configured, and the PIX config options have been taken from discussions in previous threads ...
The PIX however reports
ISAKMP: reserved not zero on payload 5!
during negotiation, and the ASL fails with a suspected authentication error (the ASL is however talking to the PIX and getting info, etc back during initial handshake).
Before I start posting reams of logs, etc has anyone got a simple answer to this?
Basic config is
VPN 1 b.b.b.0/24 / x.x.x.2 -> a.a.a.3 (ASL-ASL)
VPN 2 192.168.0.0/23 / x.x.x.62 -> a.a.a.3 (PIX-ASL)
both routing 192.168.250.0/24 via a.a.a.3
I have tried disabling VPN 1 in case the fact that both remote firewalls being on the same network could confuse the ASL (or with netmasks), but the same error occurs
VPN LiveLog
_Home_1" #25: starting keying attempt 24 of an unlimited number
Jul 18 14:38:16 fw Pluto[8392]:"Work_-_Home_1" #26: initiating Main Mode
Jul 18 14:38:17 fw Pluto[8392]:"Work_-_Home_1" #26: ignoring Vendor ID payload
Jul 18 14:38:17 fw Pluto[8392]:"Work_-_Home_1" #26: no suitable connection for peer '@cerberus.x.net'
Jul 18 14:38:28 fw Pluto[8392][:P]acket from x.x.x.62:500: Quick Mode message is for a non-existent (expired?) ISAKMP SA
Any thoughts?
This thread was automatically locked due to age.