Skip to main content
Umer221
Staff
Staff
May 19, 2025

Troubleshooting Tip: Error 'All addresses must have the same or no associated interface' when adding multiple addresses to an Address Group

  • May 19, 2025
  • 0 replies
  • 870 views
Description

This article describes how to handle the following error when creating an address group in Policy & Objects -> Addresses:

 

'One or more members are associated with an interface (interface name). Only addresses that are not associated with an interface, or are associated with "interface name" can be added.'
'All addresses must have the same or no associated interface.'

Scope FortiOS, FortiGate.
Solution

In this example, three address objects have been created, each associated with a different interface:

  • port1 address -> LAN Windows (port1).

  • port2 address -> LAN Linux (port2).

  • port3 address -> WAN (port3).

 

image - 2025-05-17T173819.892.png

 

When attempting to add the multiple address objects into a single address group, the following error appears due to conflicting interface associations assigned to the individual address objects:


image - 2025-05-17T174349.462.png

 

To resolve the error, ensure that all address objects within the group follow one of the two supported options:

 

Option 1: Use Interface = "any" for All Address Objects.

  1. Go to Policy & Objects -> Addresses.

  2. Edit each address object you plan to include in the group.

  3. In the Interface drop down, select any.

  4. Save the object.

This makes the object globally usable across any interface and avoids conflicts in grouping.

  

Option 2: Ensure all address objects use the same interface.

If interface-specific binding is required, make sure:

  1. All objects in the group are bound to the same interface.
  2. Interface-bound objects are not mixed with unbound ones.

Note: Disabling Create address object matching subnet on an interface removes the feature and deletes the related Interface Subnet address object. Any address groups or firewall policies referencing that object should be reviewed after interface role/setting changes to avoid empty groups or missing references.

 

Related article:

Interface subnet