Changes

Jump to: navigation, search

Ops535-online-lab-routing

31 bytes added, 13:36, 18 March 2021
On your gateway VM (VM1)
: There are more than thirty virtual LAN segments (VLS) in the OPS535 Virtual Lab, each Virtual LAN segment should use the private network address space 192.168.x.0/24 for local traffic. VMs in each local LAN segment should be reachable via the gateway (your VM1) with the IP address 172.20.x.1 from VMs in other VLSs in the lab. The value of x is also ranging from 1 to 43.
* On each VM in your VLS, you can either add a custom route for each other VLS in the lab using your VM1's private IP (192.168.x.1) as the gateway. In this case, you need to add a maximum of 42 routes in order to reach all the VMs in the other 42 VLS. You <b>DO NOT</b> need a custom route to your own VLS. You can also simply add a single route to 192.168.0.0/16 using your VM1's private IP as the gateway.
* You can either use the nmtui utility to add a static custom route for each VLS y that you want to reach or use the nmcli command as given in [[VLS2VLS-Routing| herethe wiki page on VLS to VLS routing]]
* Before moving on to the next step, use the "ip route" command to confirm your current kernel routing table on your VM1.
1,760
edits

Navigation menu