Troubleshooting Tip: IPv4-split-include setting disappears when editing Address Group in IPsec VPN
| Description | This article describes an issue observed on FortiGate, where the IPv4-split-include setting in an IPsec Phase1-interface configuration disappears after modifying the associated address group. Although the configuration appears intact via CLI, the setting is lost after a system reboot, causing potential disruption to split tunneling functionality. |
| Scope | FortiGate. |
| Solution | When an address group is assigned to the IPv4-split-include setting in an IPsec Phase1-interface, adding a new address object to the group causes the setting to vanish from the GUI.
In the IPsec Phase1-interface configuration, split tunneling is implemented by defining the address group 'VPN_SplitGrp' in the ipv4-split-include parameter:
config vpn ipsec phase1-interface 5H2aCe2KdoXiEVJdsxXeFrPOvHEKbTveD8uln3oyyyhXYhvVioWxdCmZwyyjgNv7tlZaON7X9rZJXMA44lKRC+recez QPE7SbinhORb7hc8VDrtm/3E77S84yz+F6VsllmMjY3dkVA
Firewall address group:
When the address object 'servers' is added to the 'VPN_SplitGrp' address group, the associated address group configured in the accessible network section of the GUI disappears.
config firewall addrgrp
Upon checking through the CLI, the 'VPN_SplitGrp' address group remains listed under ipv4-split-include. However, after a system reboot, the IPv4-split-include configuration is cleared, as illustrated below:
config vpn ipsec phase1-interface piBuSf/G7mnpceqT1S/qn6EtosqXAVQEeJhdFp9qF8szO6pXgQeZXKMWZmRoFbvTZBzqAiY+rLOTwU9llX0SGUxe6 aXLXmFuoNTUN2yqxSFaA87xuyUFlmMjY3dkVA This issue is triggered only when an FQDN-type address object is added to the address group defined in the IPv4-split-include configuration. If the address or address group contains an FQDN entry, it will not be able to add under IPv4-split-include, as it does not support an FQDN address object. |

