Route Scopes clarification

Author
CourtKPrin
New Member
  • Total Posts : 8
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/10/30 06:41:03
  • Status: offline
2019/10/30 06:59:39 (permalink)
0

Route Scopes clarification

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.
 
#1

2 Replies Related Threads

    CourtKPrin
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2019/10/30 06:41:03
    • Status: offline
    Re: Route Scopes clarification 2019/11/01 07:08:20 (permalink)
    0
    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?
    post edited by CourtKPrin - 2019/11/01 07:33:35
    #2
    CourtKPrin
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2019/10/30 06:41:03
    • Status: offline
    Re: Route Scopes clarification 2019/11/08 09:36:06 (permalink)
    0
    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
    #3
    Jump to:
    © 2019 APG vNext Commercial Version 5.5