Archived from groups: comp.security.firewalls (More info?)
I am upgrading all my compaines firewalls with the new 7.0 on
all our pixes. We have one enviroment with a Watchguard V60. With
version
6.3.4 of the pix software, I have successfully created a VPN tunnel
from the
v60 to the pix many times in the past. Now that my test PIX has been
upgraded to 7.0, I have been unable to do so and it is a major hold up
to my project...but what isn't a hold up right? See partial packet
dump below... Keeps saying PAYLOAD_MALFORMED where i have it marked
with <<<<<<<<<. Nothing of the configs has changed....in fact..Phase I
negotiates properly...when used to try and negotiate Phase II...the
watchgaurd sends the all delete SA message...
I have logs, configs, all available....Anyone have a similar
problem...maybe with a VPN concentrator 3000? I hear they took the
code from the 3000 and used it in the new pix 7.0...any ideas?
ISAKMP Header
Initiator COOKIE: 5f f9 10 cc c4 c7 92 5a
Responder COOKIE: 6b 03 45 83 42 a9 fb 9f
Next Payload: Hash
Version: 1.0
Exchange Type: Informational
Flags: (Encryption)
MessageID: F718DDC0
Length: 68
Payload Hash
Next Payload: Notification
Reserved: 00
Payload Length: 24
Data:
0c c2 e2 c0 da a3 f8 63 10 f5 cc 15 19 9e d4 71
1c 49 d2 9f
Payload Notification
Next Payload: None
Reserved: 00
Payload Length: 16
DOI: IPsec
Protocol-ID: PROTO_IPSEC_ESP
Spi Size: 4
Notify Type: PAYLOAD_MALFORMED <<<<<<<<<<<<<<<<<<<<<<<<<<<
SPI: 7c 8a 79 bc
Sep 15 12:48:17 [IKEv1]: IP = 12.156.2.254, IKE DECODE RECEIVED Message
(msgid=f718ddc0) with payloads : HDR + HASH (8) + NOTIFY (11) + NONE
(0) total length : 68
Sep 15 12:48:17 [IKEv1 DEBUG]: Group = 12.156.2.254, IP = 12.156.2.254,
processing hash
Sep 15 12:48:17 [IKEv1 DEBUG]: Group = 12.156.2.254, IP = 12.156.2.254,
Processing Notify payload
Archived from groups: comp.security.firewalls (More info?)
In article <1126822002.709287.216210@g43g2000cwa.googlegroups.com>,
jbuice@gmail.com says...
> I am upgrading all my compaines firewalls with the new 7.0 on
> all our pixes. We have one enviroment with a Watchguard V60. With
> version
> 6.3.4 of the pix software, I have successfully created a VPN tunnel
> from the
> v60 to the pix many times in the past. Now that my test PIX has been
> upgraded to 7.0, I have been unable to do so and it is a major hold up
> to my project...but what isn't a hold up right? See partial packet
> dump below... Keeps saying PAYLOAD_MALFORMED where i have it marked
> with <<<<<<<<<. Nothing of the configs has changed....in fact..Phase I
> negotiates properly...when used to try and negotiate Phase II...the
> watchgaurd sends the all delete SA message...
>
> I have logs, configs, all available....Anyone have a similar
> problem...maybe with a VPN concentrator 3000? I hear they took the
> code from the 3000 and used it in the new pix 7.0...any ideas?
Depending on the appliance, I've found a couple things cause that error
you mention:
On the WG unit, try changing the following one at a time to see if you
can match it up with the PIC:
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.