Skip to main content
tonylin1
Staff
Staff
November 25, 2025

Troubleshooting Tip: Unused IP Pools can blackhole and disrupt traffic

  • November 25, 2025
  • 0 replies
  • 670 views
Description This article describes the possible reason for service disruption after adding an IP Pools object, even though the object is not applied to any firewall policy.
Scope FortiGate.
Solution

Consider the Network topology:

 

Internet <---> [WAN] FortiGate [LAN] 14.14.14.17 <---> Client 14.14.14.100

 

FortiGate IP Pools configuration:

 

config firewall ippool

    edit "test"

        set startip 14.14.14.100

        set endip 14.14.14.100

    next

end

 

Scenario:

  • A new IP Pool 'test' was created on 'FortiGate', but it was not applied to any firewall policy.
  • Client IP address is 14.14.14.100, and the gateway is 14.14.14.17.
  • LAN interface of 'FortiGate' is 14.14.14.17.
  • Client is not able to access the Internet nor PING to LAN 14.14.14.17.
  • After removing the 'test' object from FortiGate, the Client can access the Internet again.

 

Analysis:

  • By default, arp-reply is enabled for the IP Pool object.
  • From FortiOS v6.4.17, v7.0.13, v7.2.6, and v7.4.1 versions and onwards, IP pools and VIPs are considered as local IP addresses. This means that even unused objects will intercept traffic.
  • After the IP Pool object has been set, 'FortiGate' will take all the IP addresses (from startip to endip) as its own IP address.
  • When trying to ping from the Client to FortiGate LAN interface, FortiGate will accept the ICMP echo request from the Client but send the ICMP echo reply to the root interface.

 

diagnose sniffer packet any 'icmp and host 14.14.14.100' 4 0 l

interfaces=[any]

filters=[icmp and host 14.14.14.100]

2025-11-19 14:39:58.714801 LAN in 14.14.14.100 -> 14.14.14.17: icmp: echo request

2025-11-19 14:39:58.714853 root out 14.14.14.17 -> 14.14.14.100: icmp: echo reply

2025-11-19 14:39:58.714861 root in 14.14.14.17 -> 14.14.14.100: icmp: echo reply

 

  • To fix the issue, remove the unused IPPool object or disable the arp-reply of the IP Pool object.

 

config firewall ippool
    edit "test"
        set startip 14.14.14.100
        set endip 14.14.14.100
        set arp-reply disable
    next
end

 

  • The below command helps in identifying IP pools configured on FortiGate.

 

diagnose system cmdb refcnt show firewall.ippool

 

If the IP pool has a reference count of 0, it should be removed/deleted or have arp-reply disabled. Failure to do so may cause unexpected traffic interruption, VPN failure, or routing blackholes.

 

Fortinet strongly recommends auditing and removing unused IP pools & VIPs before upgrading.

 

Related articles:

Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!