Openvpn[325]: Options error: Unrecognized option or missing parameter(s) in /var



  • Hi I'm using "1.2-BETA-1-PRERELEASE-SNAPSHOT-04-23-07" and I dont use vpn at all but it still give a error msg in System logs > OpenVPN.

    Apr 25 11:59:46 openvpn[329]: Use –help for more information.
    Apr 25 11:59:46 openvpn[329]: Options error: Unrecognized option or missing parameter(s) in /var/etc/openvpn_client0.conf:14: remote (2.0.6)
    Apr 25 11:59:45 openvpn[325]: Use –help for more information.
    Apr 25 11:59:45 openvpn[325]: Options error: Unrecognized option or missing parameter(s) in /var/etc/openvpn_server0.conf:14: lport (2.0.6)



  • You're using the latest snapshot ?
    Do you have an empty line in your openvpn-configiguration for client or server ?
    can you paste the content of /var/etc/openvpn_client0.conf please ?



  • pease try the following:

    Seems as if it would be caused by some line like <config>in the openvpn-client-config-area in the config.xml… what causes the empty settings, too

    When deleting all openvpn-settings in /etc/var, then resetting to firmware defaults, editing the config.xml and deleting the <config>-tag, then restoring the config, it works...

    No empty settings and the error gone... (which occured only once with the empty config on my test-system, too)

    Regards,

    Martin</config></config>



  • I fixed these blank config issues yesterday.  Please wait for 1.2-BETA-1.



  • I already saw this in the timeline a minute ago…  ;)

    sorry...

    But now energy has some sort of manual bug fix for it  :D



  • A number of people are going to run into this if they ran a recent snapshot or pre-release snapshot.  I have added a new option to 1.2-BETA-1 called the pfSense php shell.  To fix this issue once you upgrade to 1.2-BETA-1 do something like this (from the console or SSH menu):

    Enter an option: 12

    Starting the pfSense shell system…............

    Example commands:

    print_r($config);
        $config['interfaces']['lan']['ipaddr'] = "192.168.1.1";
        write_config();

    pfSense shell>unset($config['openvpnclient']); write_config();
    pfSense shell>unset($config['openvpnserver']); write_config();
    pfSense shell>exit

    NOTE!  This will wipe out the openvpn server and openvpn client configuration.  Be careful if you already have a configuration setup for openvpn.



  • I'm experiencing the same issue.

    http://forum.pfsense.org/index.php/topic,4696.0.html

    To fix this issue once you upgrade to 1.2-BETA-1

    I'm a little confused after you warned everyone in no uncertain terms not to use any more snapshots or upgrades until the 1.2 release:  http://forum.pfsense.org/index.php/topic,4603.0.html

    Which of the upgrades in

    http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/updates/

    are we allowed to upgrade to?



  • Yes, RELENG_1 was the problem which has been removed.

    It is safe to upgrade to RELENG_1_2 but if you have recently upgraded during previous snapshots chances are you have empty configuration items in config.xml and they need to be removed.  I outlined this in the openvpn thread somewhere on here.



  • @rcarr:

    To fix this issue once you upgrade to 1.2-BETA-1

    I'm a little confused after you warned everyone in no uncertain terms not to use any more snapshots or upgrades until the 1.2 release:  http://forum.pfsense.org/index.php/topic,4603.0.html

    At this point you should probably run 1.2b1 unless told otherwise, as I said in the linked thread. What Scott said there was just a confirmation of that, and he didn't say "don't use any snapshots until the 1.2 release". As it says in that thread, unless you're told otherwise, don't use snapshots, use the 1.2 beta release. Things can get broken between beta releases, like right now OPT outbound NAT is broken on snapshots but works fine on 1.2b1.

    For now, we follow this rule of thumb - If you run into a problem that was probably fixed by a snapshot since the last beta release and there currently is no major breakage in the snapshots, we'll suggest you upgrade to a snapshot. Unless you know, or have been told, that a snapshot is what you should be running, run the official 1.2 beta releases.


Log in to reply