Troubleshooting Tip: Hostname is missing for devices connected via IPsec VPN

[Ylli_Seitaj]

Description	This article describes an issue related to the hostname, which is missing on the logs of the DHCP server, when users connect via IPsec VPN using IKEv2 and SAML, and FortiGate is configured as a DHCP relay.
Scope	FortiGate.
Solution	The devices are connected as follows: Client (FortiClient) --- (connected via IPsec VPN to FortiGate) --- FortiGate (DHCP relay) - DHCP server. The FortiGate configuration used for this issue is: config vpn ipsec phase2-interface     edit "toclient"        set dhcp-ipsec enable        next     end config sys interface     edit "toclient"        set dhcp-relay-service enable        set dhcp-relay-type ipsec        set dhcp-relay-ip x.x.x.x <<<<External dhcp server     end config system settings     set dhcp-proxy enable     set dhcp-server-ip "x.x.x.x"     set dhcp6-server-ip <ipv6>     set gui-sslvpn enable     set gui-advanced-policy enable end When the clients connect trough IPsec VPN using IKEv2 and SAML, the connection is successful. However, the hostname is not shown on the DHCP server logs as shown in the image below.   The hostname is sent using Option 12, as defined in RFC 2132 (screenshot below is taken from) RFC 2132: https://www.ietf.org/rfc/rfc2132.txt. This behavior is noticed in environments with IPsec VPN using IKEv2 and SAML. This is currently not supported on FortiClient, and it is addressed to the engineering team through NFR: 1151961.