[Oisf-users] restarted machine and now pfring_open error
Smith, Jason A (COT)
Jason.Smith at ky.gov
Thu May 16 21:03:40 UTC 2013
It might help if my interfaces were configured to start correctly on boot. Sorry for jumping to conclusions!
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Jason A. Smith
Information Security Analyst
GCIA, GCFA, CHFI, CEH, SEC+, Linux+, LPIC-1
Office: (502) 564-6345
Security Administration Branch
Office of the CISO
Commonwealth Office of Technology
Commonwealth of Kentucky
Jones Building
120 Glenns Creek Road
Frankfort, Kentucky 40601
Commonwealth Service Desk: (502) 564-7576
Security Administration On-Call<mailto:COTSecurityOnCall at ky.gov>: (502) 229-5886
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
From: Smith, Jason A (COT)
Sent: Thursday, May 16, 2013 4:57 PM
To: 'oisf-users at openinfosecfoundation.org'
Subject: restarted machine and now pfring_open error
I used the following installation guide to install pf_ring and suricata. Everything seems to work great. However, after restarting the machine, I get the following error when restarting suricata;
[ERRCODE: SC_ERR_PF_RING_OPEN(34)] - opening eth1 failed: pfring_open error
Did I skip some sort of initialization at boot or something? Is there an easy fix that I'm not seeing? Starting and restarting suricata worked perfectly before the system reboot.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Jason A. Smith
Information Security Analyst
GCIA, GCFA, CHFI, CEH, SEC+, Linux+, LPIC-1
Office: (502) 564-6345
Security Administration Branch
Office of the CISO
Commonwealth Office of Technology
Commonwealth of Kentucky
Jones Building
120 Glenns Creek Road
Frankfort, Kentucky 40601
Commonwealth Service Desk: (502) 564-7576
Security Administration On-Call<mailto:COTSecurityOnCall at ky.gov>: (502) 229-5886
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20130516/73ef96c0/attachment-0002.html>
More information about the Oisf-users
mailing list