Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Persistent error in racoon.cnf

    Scheduled Pinned Locked Moved IPsec
    4 Posts 1 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tracer
      last edited by

      When I reboot my PFSense 1.2.2 or right 1.2.3 rc1 I always get the follwing errors in IPsec log:


      May 24 18:03:27 racoon: ERROR: fatal parse failure (1 errors)
      May 24 18:03:27 racoon: ERROR: /var/etc/racoon.conf:67: "ne" syntax error
      May 24 18:03:27 racoon: INFO: Resize address pool from 0 to 255
      May 24 18:03:27 racoon: INFO: Reading configuration from "/var/etc/racoon.conf"
      May 24 18:03:27 racoon: INFO: @(#)This product linked OpenSSL 0.9.8e 23 Feb 2007 (http://www.openssl.org/)


      And this seems to be connected to a syntax error in /var/etc/racoon.conf:

      remote anonymous {
              exchange_mode aggressive;
              my_identifier fqdn" "racer.dyndns.org"";
      

      Every time I change this file, it's been overwritten by pfsense…
      Editing the IPsec tunnels didn't help either.
      If I remember correctly this appeared after updating from 1.2 to 1.2.1 or so.

      Any hints ?

      1 Reply Last reply Reply Quote 0
      • T
        tracer
        last edited by

        Can anybody tell me where pfsense stores the values to build racoon.conf ?

        1 Reply Last reply Reply Quote 0
        • T
          tracer
          last edited by

          strange ?
          Nobody home who knows this or is this forum just not frequented enough ?

          1 Reply Last reply Reply Quote 0
          • T
            tracer
            last edited by

            found it.
            It was a incomplete IPSec profile for mobile clients.
            This screwed up the config.xml. fixed it.
            :)

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.