All Apps and Add-ons

pfsense:syslog (openvpn) usernames not being extracted properly

bradp1234
Path Finder

The openVPN log extract for TA-pfsense version 1.1 was not working for my pfsense 2.1.5 which runs openvpn 2.3.3. The src ip and usernames are not being extracted properly.

Tags (1)
0 Karma
1 Solution

bradp1234
Path Finder

I was able to resolve this issue by modifying the transforms in the TA-pfsense app. The problem with the usernames was with the field transform pfsense_syslog_user_subject_04. It was not able to handle the '.' in the username format we use. The problem with the src ip was a missing space. Below are my regex changes.

openvpn: user \'(.*?)\' authenticated
openvpn.* (\d+\.\d+\.\d+\.\d+):(\d+)

View solution in original post

bradp1234
Path Finder

I was able to resolve this issue by modifying the transforms in the TA-pfsense app. The problem with the usernames was with the field transform pfsense_syslog_user_subject_04. It was not able to handle the '.' in the username format we use. The problem with the src ip was a missing space. Below are my regex changes.

openvpn: user \'(.*?)\' authenticated
openvpn.* (\d+\.\d+\.\d+\.\d+):(\d+)

my2ndhead
SplunkTrust
SplunkTrust

Will fix it in a future release...

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...