FW: ISAKMP errors

[Horia Georgescu <hgeorges@oasis-technology.com>]

Hi all,

After I had the VPN working, I have made some changes (mostly cosmetic, I   
think) which somehow damaged my attempts to bring the IPSEC up.

You may ask why don't I just go back to what was working before. I didn't   
save the original configuration...

It seemed that everything started when I changed the authentication   
string in isakmpd.conf file (I was using the default one), forgetting to   
update the isakpmd.policy. It didn't work, so I put everything back. And   
it refued to work since then, even if the original string was restored.
   

I don't think anything is cached on the disk. The PC was rebooted since   
several times and there is nothing left in the memory.

I ran out of any ideas. I thought it requires fully qualified host names,   
and I registered a new domain for the remote firewall. I may only provide   
direct name resolution, though. I'm now waiting for the dns information   
to be synchronized. But it shouldn't rely on that, I think.

I would appreciate any suggestions.

Thanks and regards,
Horia Georgescu

I'm attaching an excerpt of the errors:

Apr  8 10:03:49 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 102 in payload
 of type 5
Apr  8 10:03:49 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE
Apr  8 10:05:05 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 132 in payload of type 5
Apr  8 10:05:05 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE
Apr  8 10:05:12 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 132 in payload of type 5
Apr  8 10:05:12 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE
Apr  8 10:05:21 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 132 in payload of type 5
Apr  8 10:05:21 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE
Apr  8 10:05:32 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 132 in payload of type 5
Apr  8 10:05:32 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE
Apr  8 10:05:45 lavpn isakmpd: message_parse_payloads: invalid next   
payload type 132 in payload of type 5
Apr  8 10:05:45 lavpn isakmpd: dropped message from 199.212.40.220 port   
500 due to notification type INVALID_PAYLOAD_TYPE

WINMAIL.DAT