Simply go to Policies &Objects-> Addresses and create an address of type Device/Mac there. Then use this object in a policy.
Alt, you can go to Dashboard -> Users and Devices -> Device Inventory, find the device in the list and right-click, create firewall address.
Today, I had to configure access to a certain Vlan for a few clients. The challenge was only that the systems could connect by ethernet or by Wi-Fi. To avoid the reservation for IP addresses it looked for a different solution. If it was possible to do this based on Mac Address. I created a new policy for the incoming interface and outgoing
interface. The source addresses will be the new mac addresses of the devices. Click on OK and add the system to the policy Ensure where to the system can connect to and if all services are allowed or not. NAT should be disabled, and you enable the policy. When enabled you see the devices to the destination. scheduled when or always. If the actions are allowed and if NAT is enabled or disabled.
Inspection can be turned on and logging settings. A return policy is not possible to go to the mac address so this will be a regular source all to destination all. [Source lan address group] to [destination lan address group] Probably but not tested it. You can add systems based on mac
addresses and when you use the FortiGate connector to the Active Directory combined with a username. This could be the case if the computer is used by multiple users.
This way you can secure the network bit more. I might give some more administration tasks especially if there a a continuously flow of personnel and change of systems who receives it.
Note
This module is part of the fortinet.fortios collection [version 2.2.1].
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
. You need further requirements to be able to use this module, see Requirements for details.
To use it in a
playbook, specify: fortinet.fortios.fortios_firewall_ipmacbinding_setting
.
New in fortinet.fortios 2.0.0
Synopsis
This module is able to configure a FortiGate or FortiOS [FOS] device by allowing the user to set and modify firewall_ipmacbinding feature and setting 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
Parameters
access_token string | Token-based authentication. Generated from GUI of Fortigate. |
enable_log boolean | Enable/Disable logging for task. Choices:
|
firewall_ipmacbinding_setting dictionary | Configure IP to MAC binding settings. |
bindthroughfw string | Enable/disable use of IP/MAC binding to filter packets that would normally go through the firewall. Choices:
|
bindtofw string | Enable/disable use of IP/MAC binding to filter packets that would normally go to the firewall. Choices:
|
undefinedhost string | Select action to take on packets with IP/MAC addresses not in the binding list . Choices:
|
member_path string | 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. |
member_state string | Add or delete a member under specified attribute path. When member_state is specified, the state option is ignored. Choices:
|
vdom string | 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: |
Notes
Note
Legacy fortiosapi has been deprecated, httpapi is the preferred way to run playbooks
Examples
- hosts: fortigates collections: - fortinet.fortios connection: httpapi vars: vdom: "root" ansible_httpapi_use_ssl: yes ansible_httpapi_validate_certs: no ansible_httpapi_port: 443 tasks: - name: Configure IP to MAC binding settings. fortios_firewall_ipmacbinding_setting: vdom: "{{ vdom }}" firewall_ipmacbinding_setting: bindthroughfw: "enable" bindtofw: "enable" undefinedhost: "allow"
Return Values
Common return values are documented here, the following are the fields unique to this module:
build string | Build number of the fortigate image Returned: always Sample: |
http_method string | Last method used to provision the content into FortiGate Returned: always Sample: |
http_status string | Last result given by FortiGate on last operation applied Returned: always Sample: |
mkey string | Master key [id] used in the last call to FortiGate Returned: success Sample: |
name string | Name of the table used to fulfill the request Returned: always Sample: |
path string | Path of the table used to fulfill the request Returned: always Sample: |
revision string | Internal revision number Returned: always Sample: |
serial string | Serial number of the unit Returned: always Sample: |
status string | Indication of the operation’s result Returned: always Sample: |
vdom string | Virtual domain used Returned: always Sample: |
version string | Version of the FortiGate Returned: always Sample: |
Authors
Link Zheng [@chillancezen]
Jie Xue [@JieX19]
Hongbin Lu [@fgtdev-hblu]
Frank Shen [@frankshen01]
Miguel Angel Munoz [@mamunozgonzalez]
Nicolas Thomas [@thomnico]
Collection links
Issue Tracker Homepage Repository [Sources]