RattleSploitable

Preface      So a few days ago I was there on my computer scrolling through twitter and saw this tweet that was particularly interesting to me. The Linux filesystem and directory structure explained (detailed thread)🐧↓ — Linuxopsys (@linuxopsys) February 15, 2023     Not really because of its contents, but rather because of memories . I remember stepping into Linux for the first time in my life and being slapped in the face by an operating that had nothing to do with, despite appearances, anything I experimented with before. Admittedly only Windows XP and 7.     The fact that the terminal is actually more powerful and faster than the desktop environment is more than enough to deal with as a newcomer to the Linux world. Trying to also understand the directory hierarchy and figuring out what goes where is a steep learning curve that not everyone overcome.     Because I'm a firm believer that any Linux Distribution is a far more solid choice than Windows or Mac as a daily

Introduction      This post aims to discuss how to configure Cisco switches to split connections into VLANs in such a way where you can interconnect devices that are in the same network but are geographically distant, meaning that it is impossible to connect them through the same switch.       Step by step. First of all, a VLAN stands for Virtual Local Area Network , and the idea consists on "splitting" the physical switch into various different "virtual switches" so that the traffic of one network comes and goes through the assigned ports. This way, no device will be able to sniff packets from another network.     For this configuration we need to use the terminal provided by CPT in each switch and router. In a real environment we would have to connect to each device through the console port and a physical cable, or access remotely if every switch is configured with an IP to do so. Layout     Let's start with the schema we need. A very basic example to see how