I think I need to start to put some Racoon feeders out, because I keep hearing some odd noises…  Coming from the console….

10/8/09 6:48:56 PM	racoon[240]	IKE Packet: receive success. (Responder, 
     Aggressive-Mode message 1).
10/8/09 6:48:56 PM	racoon[240]	IKE Packet: transmit success. (Responder, 
     Aggressive-Mode message 2).
10/8/09 6:48:56 PM	racoon[240]	IKEv1 Phase1 AUTH: success. (Responder, 
     Aggressive-Mode Message 3).
10/8/09 6:48:56 PM	racoon[240]	IKE Packet: receive success. (Responder, 
     Aggressive-Mode message 3).
10/8/09 6:48:56 PM	racoon[240]	IKEv1 Phase1 Responder: success. (Responder, 
     Aggressive-Mode).
10/8/09 6:49:01 PM	racoon[240]	IKE Packet: transmit success. (Information message).
10/8/09 6:49:01 PM	racoon[240]	IKEv1 Information-Notice: transmit success. (Delete ISAKMP-SA).

From my understanding, see the manual page below, racoon is a daemon responsible for managing the IKE protocol.

NAME
     racoon -- IKE (ISAKMP/Oakley) key management daemon

SYNOPSIS
     racoon [-46BdFLv] [-f configfile] [-l logfile] [-P isakmp-natt-port] [-p isakmp-port]

DESCRIPTION
     racoon speaks the IKE (ISAKMP/Oakley) key management protocol, to establish security associations with
     other hosts.  The SPD (Security Policy Database) in the kernel usually triggers racoon.  racoon usually
     sends all informational messages, warnings and error messages to syslogd(8) with the facility
     LOG_DAEMON and the priority LOG_INFO.  Debugging messages are sent with the priority LOG_DEBUG.  You
     should configure syslog.conf(5) appropriately to see these messages.

From my understanding, see the manual page below, racoon is a daemon responsible for managing the IKE protocol.  The IKE protocol use a key exchange method to setup a shared session secret, from which the security keys are derived from.