Date: Mon, 15 Jul 2002 16:44:25 +0900 From: Shoichi Sakane <sakane@kame.net> To: campbell@neotext.ca Cc: security@FreeBSD.ORG Subject: Re: racoon/FreeBSD 4.5 problems & observations Message-ID: <20020715164425B.sakane@kame.net> In-Reply-To: Your message of "Wed, 10 Jul 2002 09:43:38 -0000" <200207100943.g6A9hcA01547@localhost.neotext.ca> References: <200207100943.g6A9hcA01547@localhost.neotext.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> Then I upgraded (several months or so ago) ww0 to run 4.5. On doing this > I first found my /var/log/racoon.log would bloat and overrun the > filesystem (the 110% useage syndrome). So I then linked /var/log/racoon.log > to /dev/null and ran like that. No good. The racoon task would bloat > by 4k per packet transmitted across the VPN to the 4.5 node and would > quickly reach 2, 3 or 4 hundred megabytes in memory useage. Didn't matter > whether I was setting up for tunnel or transport. And it didn't matter > which version of the racoon task I was using: binaries from 4.3 behaved > as badly on the 4.5 system as did the latest release. Same with binaries > I compiled on both systems. there is no difference of racoon between 4.5 and 4.3. what kind of message did you find in the racoon.log ? i think these messages relatived to routing informations. racoon watches the routing socket in order to get addresses which are assigned to interfaces. when racoon gets either RTM_NEWADDR, RTM_DELADDR, RTM_DELETE or RTM_IFINFO, racoon will re-start to get address list. if your routing table changes frequently, racoon dumps plenty of messages into the racoon.log. to prevent this, you should define addresses to have racoon listened by using the listen directive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020715164425B.sakane>