Trisul Probe Configuration File
All configuration parameters for each Trisul Probe is stored in a single XML main configuration file called trisulProbeConfig.xml. This file is found on all Trisul-Probe nodes.
for context named data1 the path would be …probe0/context_data1/trisulProbeConfig.xml
SectionsClick on a section to see the config parameters inside that section.
|Section||What part of trisul does it configure|
|App||The trisul running process|
|Logging||Logging policy – file sizes and rotation|
|Ring||Full content storage and retention policy|
|Reassembly||TCP reassembly and advanced metering|
|File Extraction||Configure File Extraction|
|IDS Alerts||Unix sockets for accepting Unified and Unified2 alerts|
|Offline Import||For importing large pcap dumps (mostly used for testing|
|Tuning||Tuning packet processing pipeline|
Settings for the Trisul daemon process
|User||trisul.trisul||Which user/group should trisul run as after dropping root privileges.|
|DBRoot||/usr/local/var/lib/trisul/CONTEXT0||The base directory under which Trisul stores all its data.|
|ConfigDB||/usr/local/var/lib/trisul/CONTEXT0/ config/TRISULCONFIG.SQDB||Location of the configuration database.|
|PluginsLibDirectory||/usr/local/lib/trisul/plugins||Where trisul looks for dynamic (called
|PluginsConfDirectory||/usr/local/etc/trisul||Where trisul looks for additional configuration files and server certificates (for TRP).|
|PluginsDataDirectory||/usr/local/share/trisul/plugins||Where trisul looks for plugin configuration data.|
|ProbeID||SE-LINK||A mnemonic to identify this instance of Trisul, this string is reported via TRP.|
|ProbeDesc||Trisul Probe monitors the S-E link traffic only||A short description of this instance of trisul.|
|RunStateDirectory||/usr/local/var/lib/trisul-probe/domain0/probe0/context0/run||Volatile data for current run stored here|
|PluginsDataDirectory||/usr/local/share/trisul-probe/plugins||Plugins store data here; eg from downloaded feeds|
|PidFile||/usr/local/var/run/trisul.pid||File where trisul stores the process id of the current running instance.|
|TrisulMode||TAP||This determines whether you run Trisul in raw packets mode or Netflow mode.
|ValidTrisulModes||TAP,NETFLOW_TAP||Unused – just a hint for the previous parameter.|
|LicenseFile||/usr/local/etc/trisul-probe/LicenseKey.txt||Location of the license file.|
Configures logging and rotation of the probe process
|Logdir||/usr/local/var/log/trisul||Where the log files are stored.|
|Logfile||ns-???.log||Log file pattern. The default is ns-001.log, ns-002.log, etc.|
|Loglevel||DEBUG||All messages higher than this level are logged. The available log levels in order of severity (most severe one first is).
DEBUG — Recommended default level
|LogRotateSize||5000000||Size of each log file is allowed to grow to this size before Trisul moves to the next file.|
|LogRotateCount||5||The number of files in the log ring, oldest files will be rotated.|
Full content storage policy.
The Ring section allows you to control.
- How big each full content file gets
- How many such full content files are in a slice
- How many slices in operational, reference, and archive areas
- Passphrase file (the content files are AES-128 CTR mode encrypted)
- Flow rules for content trimming
|Enabled||True||Setting this to False will disable all options below, full content will not be saved.|
|Parent directory under which full content files are saved.|
|Encryption||AES-128-CTR||The encryption cipher. Currently supported modes are AES-128-CTR and NONE. Specify NONE to disable encryption of raw packet storage.|
|The encryption passphrase for the full content files.|
|FilePrefix||RCF_||Content files are called RCF_001.triscap, RCF_001.triscap, etc.. This options allows you to change the RCF_ part.|
|FileSizeMB||100||Size of each full content file in megabytes.
Maximum allowed value = 8000 (8GB). If you specify a size greater than this limit, Trisul will ignore it and use 8GB as the value.
|SyncSeconds||60||Diagnostic use only.|
|SysStatsUpdateSecs||2||Diagnostic use only.|
|DefaultMode||FULL||To cut down on full content data, Trisul allows you to apply a variety of policies. The supported modes are
|RuleChain||Each packet is evaluated against a rule chain, which is a list of rules.|
Controls how much of raw packet data is stored. There are three areas oper, ref, and archive The packet slices are always written in oper then slide into ref , archive, and then deleted as specified by the SlicePolicy below.
|SliceCount||32||Number of operational slices. The size of each slices is fixed as specified by FileSizeKB parameter|
|SliceCount||32||Number of reference slices. Setting this to zero will move slices straight to the archive.|
|SliceCount||0||Number of archive slices. If you set this to 0, slices move directly to /dev/null (ie are deleted).|
Rule chains are used to control full packet storage policies.
- Each rule is an expression in the Trisul filter format
- Treatment of each packet is one of : Store full packet, Store header, or Ignore
- The first rule to match determines the treatment given to the packet
- If no rule matches, the treatment specified in the DefaultMode parameter is applied
If present, packets which match this rule get stored completely.
- packets which match this rule and
- belong to a flow which has transferred less than 10MB bidirectionally get stored fully.
- packets which match this rule and
- belong to a flow which has transferred less than 1MB bidirectionally get stored fully.
- packets which match this rule and
- belong to a flow which has transferred less than 100KB bidirectionally get stored fully.
- packets which match this rule and
- belong to a flow which has transferred less than 10KB bidirectionally get stored fully.
If present, packets which match get only their headers stored. The headers include at least the Ethernet/IP/TCP/UDP layers.
If present, packets which match get ignored (sent to /dev/null).
Specifies how many files you want to keep in each of the three areas. The size of each file is capped by the FileSizeKB parameter.
You want this policy :
- Each Slice file is 1GB
- Store 20GB in the operational area (maybe you have limited SSD or RAID5)
- Store 500GB in the reference area
- Store 1TB in the archive
Then the SliceCounts will be 20,500,1000 for the operational,ref, archive areas.
Controls how Trisul handles IP fragmentation and TCP reassembly.
|Enabled||True||Reassembles IP fragments.|
Flow tracking keeps track of how much data has been transmitted in either direction in a single TCP flow.
- Required for flow based full content storage policy (like storing first 1M of each flow)
- Required for TCP Reassembly
- Required for all reassembly based applications like XFF Deproxy, URI Log, Content Type meters, etc
|HiWater||8000||Hi water mark for number of simultaneous flows that can be tracked. If the number of simultaneous active flows exceeds the high water mark, Trisul will prune the oldest active flows until the number of flows goes one below the low water mark.|
|LoWater||6000||Lo water mark for TCP flow pruning. See explanation for HiWater.|
Controls TCP Reassembly.
- Required for all reassembly based applications like XFF Deproxy, URI Log
- Required for reassembly based meters like HTTP Content Types, HTTP Hosts, URL Filter, etc
|KickoffBytes||5000||Some meter within Trisul must express an interest in reassembled data for a given flow before this limit is reached. Otherwise reassembly is stopped at this point for this flow.|
|Ports||Traffic on these ports are reassembled. By default Trisul this is "" because uses heuristics to detect applications independent of port. You can override this behaviour by setting to a string like 3000,80,443,22,21 to reassemble only these ports|
* IN Only the IN direction; direction of first SYN+ACK is reassembled
* OUT Only the OUT direction; direction of initial SYN is reassembled
* INOUT Both directions are reassembled
Some advanced applications.
Since these applications depend on the TCP Reassembly feature, they are resistant to TCP fragmentation evasions.
|EnableXFFDeproxy||True||Useful in a corporate environment with web proxies. If set to true, Trisul can deproxy web traffic by looking at the X-Forwarded-For HTTP header. The actual IP is substituted for all metering and flow analysis instead of the proxy’s IP.|
|EnableURILog||True||Logs all HTTP URLs requested. These URLS show up as Resources in Trisul where they are correlated and made searchable.|
|EnableHostMeter||True||Add traffic metering by HTTP Host header. The net effect of enabling this is that the HTTP Host counter group is made active.|
|EnableContentTypeMeter||True||Add traffic metering by HTTP Content-Type header. Activates the HTTP Content Type counter group.|
|EnableSSLCertLog||True||Logs all SSL certificate chains|
|EnableHTTPFTS||True||Full Text Search (FTS) enabled for all HTTP Headers seen|
|EnableSSLFTS||True||FTS enabled for all SSL Certificates seen|
|EnableFTPTrack||True||Tracks FTP data session by matching the corresponding control flows|
|EnableSSLRecordExtraction||False||If you want access to the raw TLS Protocol PDUs. If set to “True” ; Trisul will generate “TLS:RECORD” callbacks you can hook on to in the Reassembly engine. Unless you are working deep with TLS you typically can leave this as False.|
Controls the file extraction feature.
trisulctl_probe createramfs probe0 defaultA 100MB partition would suffice for loads < 1Gbps. For more read File Extraction LUA API in detail
|Enabled||False||Feature is enabled or not|
|RamFsDir||The directory mounted on the TMPFS file system|
|ChunkSizeMB||5||For large files your LUA script will be handed chunks of this size. Tweak this based on how much RAM you can allocate to the
Controls how security alerts from Snort/Barnyard2 are handled
|Enabled||True||Enables this feature. If this is set to FALSE, alerts will not be processed even if trisul is running in fullblown or idsalert modes.|
|SnortUnixSocket||/tmp/snort_alert||Trisul opens this unix socket and listens for alerts. Typically this is ’’snort_alert’’ for Unified events from Snort and ’’barnyard2_alert’’ for Unified2 events from Barnyard2.|
|SnortVersion||2.9+||Trisul uses Unix Sockets to read alerts from Snort. Snort 2.9 and above use a different structure compared to earlier versions. This string helps decide which version we are using.
Example : If you are running Snort 2.8, then set this to ‘’2.8’‘. If you are always using 2.9 or newer then just leave this at the default setting, which is ’’2.9+’’ . Do not set this to 2.10, 3.0, etc.
Controls aspects of PCAP file import.
|LoopCount||1||Used for testing. Runs the same capture file/directory this many time past Trisul. Each run is appended time-wise to the end of the previous run. This is used internally by us to generate months of data from a few days of capture by repeating them over and over.|
|AppendMode||TRUE||Appends the run to the previous runs time-wise. The packet time stamps in the capture file are offset by the last time of the previous run.|
|InterfileGapSecs||60||When importing multiple files, this option puts a gap of this many seconds between each file. There is no purpose of this option other than to view a gap in the charts representing the capture files.|
|AutoSortByCaptime||TRUE||When TRUE, the candidate capture files are sorted by time order (earliest to latest), and then imported into Trisul. When FALSE, the files and subdirectories are processed in alphabetical order.|
|ResumeStalledImport||FALSE||Dependency:AutoSortByCaptime must be TRUE
Treats the import as a resumption of a previously stalled or aborted offline import. When TRUE, Trisul will first determine what timestamp was last flushed. Then it will skip all packets earlier than that timestamp and continue importing when newer timestamps are seen.
This feature is used to resume a stopped import without reprocessing everything again.
Use this feature with the following caution :
# Due to the discontinuous nature, some packets may be missed or double counted around the timestamp where the earlier import was aborted
# Flows may be duplicated around the time
|AddEthernetFCS||FALSE||If set to true, will add 12 bytes to every ethernet packet to account for FCS|
Fine tune the packet processing pipeline for peak performance.
|AnalysisQueueCapacity||200000||Queue for database update messages.|
|PcapQueuCapacity||500||Queue for disk packet storage.|
|PcapRAIDStripeSize||1048576||Sequential writes of this size.|
|GrainSize||64||Number of packets to process in a batch. You can increase this value if you have a CPU with a large L1/L2 cache. If the entire batch fits in cache memory – it can increase concurrency – and decrease drops.|
|SpongeWindow||1||A key internal data structure parameter to help with multicore.
Number of seconds a single core must accumulate before synchronizing. In most cases, leave this alone.
|InflightTokens||2||Number of work items in parallel. Maps to number of hardware threads you want to give to trisul.|
|TCPReassFilters||2||Number of TCP Filters – Trisul will hash and load share. Typically matches the number of InflightTokens|
|CoreAffinityNet||CPU cores you want you pin the packet processing threads to. Use “1,2,4” to pin to CPU Cores 1,2,4|
|CoreAffinityRAID||CPU cores allowed to do disk writes for packet storage|
|FBQDrainChunkSize||-1||Controls how fast an internal data structure called the Feedback Queue is drained|