Project

General

Profile

Actions

Bug #6266

closed

OpenVPN configuration mix-up

Added by László Bakóczy almost 8 years ago. Updated almost 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
04/26/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

Hi!

A few days ago, my PfSense's Openvpn section make a mistake. i have a server with tunnel mode and client specific overrides. Working good, with no problems. The system on geomirror, and protected by UPS. Unfortunately the UPS is broken, and the PfSense is stopped. After restart, the openvpn server's advanced configuration field's contents rewritten to two of three client specific override. the "route x.x.x.x 255.255.255.0 vpn_gateway" lines. Of course the server not working perfectly. The log is: "openvpn36103: home/1.2.3.4:1194 Options error: option 'route' cannot be used in this context (/var/etc/openvpn-csc/home)"

Before the blackout, the config is working perfect.

This is maybe a bug...

sorry my english.

2.2.6-RELEASE (amd64)
built on Mon Dec 21 14:50:08 CST 2015
FreeBSD 10.1-RELEASE-p25

Actions #1

Updated by Chris Buechler almost 8 years ago

  • Status changed from New to Not a Bug
  • Affected Version deleted (2.2.6)

A reboot didn't change anything in the advanced box or CSC. Only admin actions determine what's in both of those. That looks to be because you had a route statement in a CSC, which isn't valid. It's possible there are OpenVPN CSC configurations that are fine with an already-running server that then fail once the server is stopped/started, that appears to be the case here.

Actions

Also available in: Atom PDF