Forum Discussion

3 Replies

  • Yes exactly, I've created a ticket and will share the information as soon as I get a response from F5.

     

  • F5 logging deployment for racoon is to a file which seems to override the default logging mechanism to syslog. It could be also a case of there has been no defined filter for syslog-ng to catch the messages. May be a good idea to open a ticket with F5 Support and ask for improvement for raccoon to log to syslog of which it then becomes flexible for one to send the logs remotely.

     

    *** Extract from raccoon manual ***

     

    "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."