Date: Tue, 12 Jul 2011 15:42:51 -0700 From: Chuck Swiger <cswiger@mac.com> To: Paul Keusemann <pkeusem@visi.com> Cc: freebsd-net@freebsd.org Subject: Re: Debugging dropped shell connections over a VPN Message-ID: <5458975C-9FA3-4AB6-9535-3D7BD152378B@mac.com> In-Reply-To: <4E1C9FEA.2080608@visi.com> References: <4E159C5A.5090702@visi.com> <13D65A4C-F874-4970-A070-AA0392416680@mac.com> <4E1C9FEA.2080608@visi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 12, 2011, at 12:26 PM, Paul Keusemann wrote: > So, any other ideas on how to debug this? Gather data with tcpdump. If you do it on one of the VPN endpoints, you ought to see the VPN contents rather than just packets going by in the encrypted tunnel. > Anybody know how to get racoon to log everything to one file? Right now, depending on the log level, I am getting messages in racoon.log (specified with -l at startup), messages and debug.log. It would really be nice to have just one log to look at. This is likely governed by /etc/syslog.conf, but if you specify -l then racoon shouldn't use syslog logging. Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5458975C-9FA3-4AB6-9535-3D7BD152378B>