Skip to main content
jba
New Member
October 29, 2025
Solved

IKeV2 VPN Tunnel for Windows Native Client and DHCP from internal Tunnel Interface - DHCP

  • October 29, 2025
  • 3 replies
  • 697 views

Hello,

 

i have a working VPN Device Tunnel (named FG-VPN-Device) for my Windows 11 Clients. These clients can connect on a certificate based authentication with the fortigate firewall.

The Tunnel is configured with Mode Config enabled and a the IP is assigned with a Client IP Range (10.58.58.50-10.58.58.99).

 

But i can´t route any traffic over SD-WAN with this config, as the IP Range has no gateway.

After some more reading, i think, that i need to set a IP and DHCP Server for this Interface (named FG-VPN-Device).

 

I followed this article 

 

DHCP IP address reservation with Dial up ... - Fortinet Community

 

But after settings these options, the Windows 11 Client can´t connect anymore.

There is no DHPC assignment to the client.

 

any idea what is missing?

Best answer by AEK

Hi JBA

Why do you need a gateway for the tunnel? The default gateway interface for the client is simply the tunnel (without IP).

3 replies

AEK
SuperUser
AEKAnswer
SuperUser
October 29, 2025

Hi JBA

Why do you need a gateway for the tunnel? The default gateway interface for the client is simply the tunnel (without IP).

AEK
jba
jbaAuthor
New Member
October 29, 2025

Thanks, i tried to get from the VPN Client from Headoffice to the Branchoffice.

I tried a few settings, but finally i had a missing BGP entry for the VPN Subnet...

Thanks

ElwinBERRAR
Explorer III
October 29, 2025

That makes sense, glad you figured it out

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.