Hi, everyone.
I'm trying to set up RADIUS authentication for FortiClient VPN connections towards two windows domain controllers. I have two of them - the BDC is on premise and the PDC is in AWS (connected through a VPN tunnel).
The connection towards the BDC is fine. This is the primary authentication server.
When trying to test the connection from the Fortigate towards the AWS instance, I see that the connection is made from the tunnel interface IP. The connection fails, because I have not created any routing and security group inbound rules for the interface IPs in AWS. Is there any way to make the Fortigate make the RADIUS request from the LAN interface IP? That would make the rules much simpler.
Regards,
Chocolate Eater
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello
Try with 'nas-ip' and/or 'source ip' depending upon your needs.
I mean, with CLI:
config user radius
set nas-ip <ip_used_to_connect_to radius server , and Caller-Station_ID attribute>
....
set source ip <ip_used_to_connect_to radius server>
...
end
regards
/ Abel
Hello
Try with 'nas-ip' and/or 'source ip' depending upon your needs.
I mean, with CLI:
config user radius
set nas-ip <ip_used_to_connect_to radius server , and Caller-Station_ID attribute>
....
set source ip <ip_used_to_connect_to radius server>
...
end
regards
/ Abel
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1690 | |
1087 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.