<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117063#M8787</link>
    <description>&lt;P&gt;Hi @FireESplunkGuy&lt;/P&gt;

&lt;P&gt;Did you create this post to share the solution that worked for you, or did you actually have a question you needed help with? If you were just posting this out of the kindness of your heart, don't forget to actually post the official answer in the "Enter your answer here..." box at the bottom of this page and click "Accept" on the answer after it has been posted. That will show the post as actually resolved and can prove useful to other users when searching this site. Once you do that, I'll be sure to upvote it &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; Thanks!&lt;/P&gt;

&lt;P&gt;Patrick&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jul 2015 00:07:18 GMT</pubDate>
    <dc:creator>ppablo</dc:creator>
    <dc:date>2015-07-14T00:07:18Z</dc:date>
    <item>
      <title>TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117056#M8780</link>
      <description>&lt;P&gt;For me I found that the TA_pfsense searches for openVPN connections was not returning all the VPN user log entries..&lt;/P&gt;

&lt;P&gt;I discovered that it works just fine with a username, however some of my usernames are their e-mail addresses so contain @-. which were not part of the REGEX..&lt;/P&gt;

&lt;P&gt;here's my updated REGEX entry "transforms.conf" file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[openvpn_auth_ok]
CLEAN_KEYS = 0
FORMAT = user::$1 src::$2 vendor_action::$3
REGEX = :\s+([\w\@\-\.]+)/([^:]+):\d+\s+(MULTI_sva)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Jul 2015 13:02:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117056#M8780</guid>
      <dc:creator>FireESplunkGuy</dc:creator>
      <dc:date>2015-07-13T13:02:41Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117057#M8781</link>
      <description>&lt;P&gt;Pretty sure that as it is, the markup messed up your regex. Please format it as code.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 13:28:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117057#M8781</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2015-07-13T13:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117058#M8782</link>
      <description>&lt;P&gt;Sorry about that.. just pasting quickly... \w only matches on A-Za-z0-9, so misses the '@', '-', '.' which can be seen in e-mails..&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 13:36:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117058#M8782</guid>
      <dc:creator>FireESplunkGuy</dc:creator>
      <dc:date>2015-07-13T13:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117059#M8783</link>
      <description>&lt;P&gt;Thats better. Thanks for sharing &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Now, from what I've seen usernames can usually contain any non-whitespace characters, so maybe &lt;CODE&gt;\S&lt;/CODE&gt; is easier than giving a long, explicit list of allowed characters.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 13:59:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117059#M8783</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2015-07-13T13:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117060#M8784</link>
      <description>&lt;P&gt;Yup that's much better! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 14:17:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117060#M8784</guid>
      <dc:creator>FireESplunkGuy</dc:creator>
      <dc:date>2015-07-13T14:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117061#M8785</link>
      <description>&lt;P&gt;BTW.. &lt;A href="https://regex101.com"&gt;https://regex101.com&lt;/A&gt; is a great site to test out your REGEX&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 14:18:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117061#M8785</guid>
      <dc:creator>FireESplunkGuy</dc:creator>
      <dc:date>2015-07-13T14:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117062#M8786</link>
      <description>&lt;P&gt;That's what I always recommend as well.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 14:22:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117062#M8786</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2015-07-13T14:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117063#M8787</link>
      <description>&lt;P&gt;Hi @FireESplunkGuy&lt;/P&gt;

&lt;P&gt;Did you create this post to share the solution that worked for you, or did you actually have a question you needed help with? If you were just posting this out of the kindness of your heart, don't forget to actually post the official answer in the "Enter your answer here..." box at the bottom of this page and click "Accept" on the answer after it has been posted. That will show the post as actually resolved and can prove useful to other users when searching this site. Once you do that, I'll be sure to upvote it &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; Thanks!&lt;/P&gt;

&lt;P&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jul 2015 00:07:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117063#M8787</guid>
      <dc:creator>ppablo</dc:creator>
      <dc:date>2015-07-14T00:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: TA-pfsense: How to update the transforms.conf regex to parse openVPN logs where the usernames are email addresses?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117064#M8788</link>
      <description>&lt;P&gt;So just to follow up...&lt;/P&gt;

&lt;P&gt;changing the \ w to a \ S allows for much cleaner username capture and covers usernames which might be e-mail addresses.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [openvpn_auth_ok]
 CLEAN_KEYS = 0
 FORMAT = user::$1 src::$2 vendor_action::$3
 REGEX = :\s+(\S+):\d+\s+(MULTI_sva)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 14 Jul 2015 07:25:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/TA-pfsense-How-to-update-the-transforms-conf-regex-to-parse/m-p/117064#M8788</guid>
      <dc:creator>FireESplunkGuy</dc:creator>
      <dc:date>2015-07-14T07:25:15Z</dc:date>
    </item>
  </channel>
</rss>

