In the installation instructions for creating Layer 3 route scope interface eth1, it says to "Use a different IP for each route scope type you configure". Does that mean Isolation, Registration, Remediation interface addresses should have different IPs, but be in the same subnet? 192.168.10.23 /24, 192.168.10.24 /24, 192.168.10.25 /24
In the same section of the instructions, Figure 11 shows Interface IPv4 address: 192.168.10.23 mask:255.255.255.0 and optional gateway 172.16.39.1. Shouldn't the gateway be in the same subnet as the interface? I don't understand how this optional gateway is involved.
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.
I now think each Isolation Network has a different IP, but is in the same subnet, because, "eth1 is connected to a single VLAN." For example:
Remediation interface IP is 192.168.10.23 with subnetmask 255.255.255.0
Registration interface IP is 192.168.10.24 with subnetmask 255.255.255.0
DeadEnd interface IP is 192.168.10.25 with subnetmask 255.255.255.0
Is that correct?
I still don't know what goes in the optional gateway field for each Isolation Network. If eth1 on the FortiNAC is connected to eth1 on the router and it has an IP of 192.168.10.254, would that IP be used in the optional gateway field for each Isolation Network? Or, leave it blank?
I got a reply from support about Figure 11 in the setup instructions and they will be correcting them. For the gateway, it will use the interface's subnet, i.e. 192.168.10.1
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 |
---|---|
1634 | |
1063 | |
751 | |
443 | |
210 |
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.