🔰 14.1 Create a network Topology Setup in such a way so that System A can ping to two Systems System B and System C but both these systems should not be pinging each other without using any security rule
e.g firewall etc.

3 min readMar 28, 2021

In this Blog I am going to create the Topology that Master can be Ping to Node1 and Node2 , but Node1 and Node2 cannot Ping to each other.

Introduction :

Routing table :

Routing table is a data table and contains rules which determines whether to create a network packet to a particular destination. If the rule is there in the routing table that you can send packets, you can send. The routing table present in all devices. We can create routing table accordingly to whom we have to create and for whom we don’t have to create. After creating routing table, the OS can identify the rules. So, accordingly it will create.

Network Name :

Network Name is actually an IP and the first address of the Network which actually tells about the Network range with respect to Netmask. It is the reserved IP of the Network. We can able to send a packet within the Network name or Network range which we create in routing table. It is also called as Network ID.

Netmask :

Netmask actually tells the range of IPs in the network starting from Network name. Netmask can also be called as Subnet mask or Genmask (But there is a little difference betweeen Netmask and Subentmask but logic wise both are same). The Network name with Netmask is called as Subnet ID. The Subnet ID is represented as Network_name/Netmask. For ex: The IP address of the system is 192.43.56.180 . In this, the network name can be 192.43.56.0 and netmask is 255.255.255.0 and whole can be represented as 192.43.56.0/255.255.255.0 or 192.43.56.0/24 (24 is prefix) and this is called Subnet ID. The last ocatate which occupies in the Network range is called Host ID. In the example the 180 is called host ID of 192.43.56.0/24 network.