Fun with networking concepts!!

Shubhambhalala
3 min readMar 7, 2021

--

https://www.pinterest.com/pin/222928250282097915/

Today we will be exploring some concepts of subnetting and routing table in a playful manner. When it comes to networking people think of complex calculations and Linux commands to set it up. Usually, they avoid such topics because they feel it’s very tedious and disinterested work but it’s very interesting to know how actually our systems are connected and communicate. If we know the right concepts, we can enjoy playing with them. So, let’s start with today's fun activity. In this article, you will come to know about how can we set up a network topology where system A can ping to system B & C but B & C cannot ping to each other despite being in the same network range. Isn’t this fun!! Let’s begin.

Step1: Configuring system A

To make all three systems in one network we need to make their IP belong to the same network range. To do so we will change the IP and subnet mask using the ifconfig command in Linux. Then we have to change the route in the routing table for configuring system A to connect to B & C, for doing so we will use the route command in Linux.

Our by default IP address and route entries
changing the IP address to 192.168.0.1/24 using the ifconfig command
Adding a route entry that will only allow connecting to the IP range of /30

Here, we need to focus on the range we provide. It’s /30 which means only 4 IP in the range. This range covers 192.168.0.2 and 192.168.0.3, hence we will use this IP for systems B and C.

Step2: Configuring system B

Changing the IP and the route entry that will have the range /31

Here, we have the range /31 because this range is used for point-to-point communication. This was the game-changer for this fun activity. Now, this range means we can only communicate to one system in the network range. This system will be a 192.168.0.1 system. We need to do this same setup with system C. Hence, systems B and C won’t be able to communicate even tho they are on the same network but they are communicating with system A.

Step3: Configuring system C

Changing the IP and the route entry that will have the range /31

Step4: Check our architecture

System A can ping to systems B & C.
System B can ping to A but not C, even after being in the same network
System C can ping to A but not B, even after being in the same network

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

Shubhambhalala
Shubhambhalala

Written by Shubhambhalala

C|EH | Cybersecurity researcher | MLOps | Hybrid Multi Cloud | Devops assembly line | Openshift | AWS EKS | Docker

No responses yet

Write a response