fortinet.fortios.fortios_firewall_sniffer – Configure sniffer in Fortinet’s FortiOS and FortiGate.
Note
This plugin is part of the fortinet.fortios collection (version 2.1.3).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install fortinet.fortios
.
To use it in a playbook, specify: fortinet.fortios.fortios_firewall_sniffer
.
New in version 2.10: of fortinet.fortios
Synopsis
This module is able to configure a FortiGate or FortiOS (FOS) device by allowing the user to set and modify firewall feature and sniffer category. Examples include all parameters and values need to be adjusted to datasources before usage. Tested with FOS v6.0.0
Requirements
The below requirements are needed on the host that executes this module.
ansible>=2.9.0
Parameters
Parameter |
Comments |
---|---|
Token-based authentication. Generated from GUI of Fortigate. |
|
Enable/Disable logging for task. Choices:
|
|
Configure sniffer. |
|
Configuration method to edit Denial of Service (DoS) anomaly settings. |
|
Action taken when the threshold is reached. Choices:
|
|
Enable/disable anomaly logging. Choices:
|
|
Anomaly name. |
|
Quarantine method. Choices:
|
|
Duration of quarantine. (Format |
|
Enable/disable quarantine logging. Choices:
|
|
Enable/disable this anomaly. Choices:
|
|
Anomaly threshold. Number of detected instances per minute that triggers the anomaly action. |
|
Number of detected instances per minute which triggers action (1 - 2147483647). Note that each anomaly has a different threshold value assigned to it. |
|
Name of an existing application list. Source application.list.name. |
|
Enable/disable application control profile. Choices:
|
|
Name of an existing antivirus profile. Source antivirus.profile.name. |
|
Enable/disable antivirus profile. Choices:
|
|
Name of an existing DLP sensor. Source dlp.sensor.name. |
|
Enable/disable DLP sensor. Choices:
|
|
Enable/disable DSRI. Choices:
|
|
Name of an existing email filter profile. Source emailfilter.profile.name. |
|
Enable/disable emailfilter. Choices:
|
|
Name of an existing file-filter profile. Source file-filter.profile.name. |
|
Enable/disable file filter. Choices:
|
|
Hosts to filter for in sniffer traffic (Format examples: 1.1.1.1, 2.2.2.0/24, 3.3.3.3/255.255.255.0, 4.4.4.0-4.4.4.240). |
|
Sniffer ID. |
|
Interface name that traffic sniffing will take place on. Source system.interface.name. |
|
Name of an existing IP threat feed. |
|
Threat feed name. Source system.external-resource.name. |
|
Enable/disable IP threat feed. Choices:
|
|
Enable/disable IPS DoS anomaly detection. Choices:
|
|
Name of an existing IPS sensor. Source ips.sensor.name. |
|
Enable/disable IPS sensor. Choices:
|
|
Enable/disable sniffing IPv6 packets. Choices:
|
|
Either log all sessions, only sessions that have a security profile applied, or disable all logging for this policy. Choices:
|
|
Maximum packet count (1 - 1000000). |
|
Enable/disable sniffing non-IP packets. Choices:
|
|
Ports to sniff (Format examples: 10, :20, 30:40, 50-, 100-200). |
|
Integer value for the protocol type as defined by IANA (0 - 255). |
|
Enable/disable scanning of connections to Botnet servers. Choices:
|
|
Name of an existing spam filter profile. Source spamfilter.profile.name. |
|
Enable/disable spam filter. Choices:
|
|
Enable/disable the active status of the sniffer. Choices:
|
|
List of VLANs to sniff. |
|
Name of an existing web filter profile. Source webfilter.profile.name. |
|
Enable/disable web filter profile. Choices:
|
|
Member attribute path to operate on. Delimited by a slash character if there are more than one attribute. Parameter marked with member_path is legitimate for doing member operation. |
|
Add or delete a member under specified attribute path. When member_state is specified, the state option is ignored. Choices:
|
|
Indicates whether to create or remove the object. Choices:
|
|
Virtual domain, among those defined previously. A vdom is a virtual instance of the FortiGate that can be configured and used as a different unit. Default: “root” |
Examples
- collections:
- fortinet.fortios
connection: httpapi
hosts: fortigate01
vars:
ansible_httpapi_port: 443
ansible_httpapi_use_ssl: true
ansible_httpapi_validate_certs: false
vdom: root
tasks:
- name: fortios_firewall_sniffer
fortios_firewall_sniffer:
vdom: root
state: present
firewall_sniffer:
application_list_status: disable
av_profile_status: disable
dlp_sensor_status: disable
dsri: disable
emailfilter_profile_status: disable
id: 1
interface: port4
ips_dos_status: disable
ips_sensor_status: disable
ipv6: disable
logtraffic: utm
max_packet_count: 4000
non_ip: enable
status: enable
webfilter_profile_status: disable
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Build number of the fortigate image Returned: always Sample: “1547” |
|
Last method used to provision the content into FortiGate Returned: always Sample: “PUT” |
|
Last result given by FortiGate on last operation applied Returned: always Sample: “200” |
|
Master key (id) used in the last call to FortiGate Returned: success Sample: “id” |
|
Name of the table used to fulfill the request Returned: always Sample: “urlfilter” |
|
Path of the table used to fulfill the request Returned: always Sample: “webfilter” |
|
Internal revision number Returned: always Sample: “17.0.2.10658” |
|
Serial number of the unit Returned: always Sample: “FGVMEVYYQT3AB5352” |
|
Indication of the operation’s result Returned: always Sample: “success” |
|
Virtual domain used Returned: always Sample: “root” |
|
Version of the FortiGate Returned: always Sample: “v5.6.3” |
Authors
Link Zheng (@chillancezen)
Jie Xue (@JieX19)
Hongbin Lu (@fgtdev-hblu)
Frank Shen (@frankshen01)
Miguel Angel Munoz (@mamunozgonzalez)
Nicolas Thomas (@thomnico)