Creating a Custom Network Topology

 Today, we will create a topology such that there will be 3 systems 

System A <-----------------> System B <-----------------> System C

But System A and C can't connect.

This can be done by assigning A and C different networks and B will have networks containing both networks of A and C. 

The generation of packets depends upon the rules written in the routing table. 

Lets assign Ip 192.168.1.1 to B with netmask of 255.255.0.0, It will conatain ips from 192.168.0.0 - 192.168.255.255

and System A will get ip 192.168.1.5 with netmask 255.255.255.252 and System C will get ip 192.168.2.5 with netmask 255.255.255.252.

Both will contain only 4ips. 

Ip can be set by commands 

For B

ifconfig enp0s3 192.168.1.1/16

For A

ifconfig enp0s3 192.168.1.5/30

For C

ifconfig enp0s3 192.168.2.5/30


Rules can be added by commands 

For B

route add -net 192.168.0.0/16 enp0s3

For A

route add -net 192.168.1.0/30 enp0s3

For C

route add -net 192.168.1.0/30 enp0s3


Lets See the routing tables of all systems

B

A

C

Now, lets ping 

B to A

B to C

A to B

C to B

Here, C is of different network that's why it is not able to ping as we need router in between them.

A to C

C to A




Our topology is created.

Thank You for reading.

I would like to thanks Vimal Daga Sir.

My Email — ayanchawlae@gmail.com















Comments

Post a Comment

Popular posts from this blog

Key Announcements at Microsoft Ignite

Image
World is going to be an Agentic World  Universal Interface + Reasoning Planning + Memory & Context = Agentic World Copilots are the way in future -  First -> Security -  Secure Future Initiative -  Security Updates url -  aka.ms/Ignite2024Security 1. Purview -  This new hacking event will be the largest of its kind, with an additional $4 million in potential awards for research into high-impact areas, specifically cloud and AI. Zero Day Quest will provide new opportunities for the security community to work hand in hand with Microsoft engineers and security researchers – bringing together the best minds in security to share, learn, and build community as we work to keep everyone safe.   aka.ms/ZeroDayQuest Second -> Copilot 3 Fold method for Copilot -  Adoption - More people should use copilot Extensibility - More extensions for the copilot ROI - How to measure the Roi for copilot Adoption -  2. Copilot Pages - Copilot is UI fo...
Read more

Ansible Handlers

Image
 In this post, you will learn about ansible handlers. Handlers are like if and else in ansible, suppose you have a configuration file in httpd server, and you want whenever you change something in configuration file, the httpd service must restart. In this case we will use handlers.  Components-: Controller node(192.168.1.7), Target node(192.168.1.8) The ansible-playbook looks like  It will only run the handlers portion only when notify will be changed. Target Node-  httpd is running on 8081. Playbook running when conf file is changed Playbook running second time You can view the webpage running on port 8081 Thank You  for reading. I would like to thanks  Vimal Daga  Sir. ( https://www.linkedin.com/in/vimaldaga/ ) My Email — ayanchawlae@gmail.com My LinkedIn —   https://www.linkedin.com/in/ayanchawlae/
Read more

Ansible Roles (Httpd + Haproxy)

Image
 Today we will create 2 ansible roles and then will run them combined to create a load balancer setup with 2 nodes connected to it. Lets first init the roles by ansibe galaxy After these commads t15.yml is the main file in which we have combined both the codes Lets create tasks in both the roles httpdserver -> tasks -> main.yml The main.yml file in httpdserver Similarly for loadbalancer role loadbalancer  -> tasks -> main.yml The main.yml for loadbalancer The config file of haproxy looks like We can see the working of loadbalancer Thank You  for reading. I would like to thanks  Vimal Daga  Sir. ( https://www.linkedin.com/in/vimaldaga/ ) My Email — ayanchawlae@gmail.com My LinkedIn —   https://www.linkedin.com/in/ayanchawlae/
Read more