| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
some fixes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to be looked after. Maybe use any as default snort.conf?
|
| |
|
| |
|
| |
|
|
|
|
| |
custom_rules since its not used
|
| |
|
| |
|
|
|
|
| |
needed anyumore
|
|
|
|
| |
for that
|
| |
|
| |
|
|
|
|
| |
make snort var settings generic and overridable in all of its definitions
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
begining
|
|\
| |
| | |
Standard pfSense version check, fix promiscuous mode setting
|
|/
|
|
|
| |
future versions of pfsense.
Previously, promiscuous mode was always stuck on - the bandwidthd default is "promiscuous true" and the code assumed the default was "false". This fix always specifies promiscuous mode explicitly so that it does not matter what the default is, the setting will always follow whatever the user has selected in the GUI check box. See forum thread http://forum.pfsense.org/index.php/topic,50878.0.html
|
| |
|
| |
|
| |
|