Now that the lab is almost complete, we still need to add a wireless access point to the public network. To do this, we will use an OpenWrt router or any router you have on hand. The procedure for adding a physical device to GNS3 (in this case, a wireless router with OpenWrt) is described in the following video:

Following the previous post, we will now add Vlans and ACL’s to add an extra layer of security.

ACL’s

The Public, Administrative, and Development networks can communicate with each other. To avoid this, we will add ACL’s to R1. We create rules for each network:

Public Network

For this network, we need to deny routing to the Administrative and Development networks. We create an access-list 2:

1
2
3
4
5

R1(config)#access-list 2 deny 172.16.30.0 0.0.1.255
R1(config)#access-list 2 deny 172.16.32.0 0.0.7.255
R1(config)#access-list 2 deny 172.16.40.0 0.0.7.255
R1(config)#access-list 2 deny 172.16.48.0 0.0.1.255
R1(config)#access-list 2 permit any

Now, on the interface for this network on R1:

Overview

This document will guide you through the process of designing and implementing a pentesting laboratory using GNS3 as the primary tool.

Network Architecture

For the network design, we will consider a small organization that requires:

As seen, we have 4 groups or subnets. Some additional conditions are:

Introduction

After completing my CCNA1 course, I decided to set up my own Pentesting lab or controlled environment, but with the condition that it should be as realistic as possible. I still have a lot to l earn about the CCNA 200-301 certification, and what better way to practice what I’ve learned than by working on this project. Additionally, this will be my first official project in the field of cybersecurity.

I solved Jangow01 using only Bash!!!

In this series of posts, I try to use only Bash and some external tools only if extremely needed.

The past weekend, Synack Red Team was starting his invitational CTF