The Networking Nomad

Vulnerability is when you are using unsecure methods in your organization that may open you up to attacks from hackers.This lab provides a simple inside look into why protocols like TELNET/HTTP are not used instead SSH/HTTPS is used. Router 1 Configs: Assign IP on port: Configs for enabling TELNET Enable HTTP R2 Configs: Just configure IP on the port. Now to show as to why using TELNET is a vulnerability we are going to access the R1 using telnet from R2. We will capture packet using Wireshark, and look for Telnet traffic. Go to Router 2 and TELNET into Router 1 and run some commands. Filter for telnet traffic. So I ran 2 commands "show ip interface br" & "show interface summary". Lets see the Wireshark capture. And here you can see if I am a malicious actor, I have gotten access to your account/password and I can also see the commands and configuration that you are making to the router. This is the prime reason why TELNET is discouraged. Now we go the kali linu...

  Lets consider a basic example of layer 2 VPN deployment  for customers that want to connect remote site that are in the same subnet. Let's divide it into 2 parts: 1- Setting up a basic ISP environment. Enabling an IGP (OSPF/ISIS) Enabling MPLS Enabling MPLS LDP / L2VPN Setting up LDP remote Peering  2- Connecting the customer side with the ISP Let's start by setting up the ISP environment. Configurations of Router (R5, R6, R7, R8): Assign a loopback ip, example R5 has 5.5.5.5. For Interface IPs the scheme is as follows:  The first two octets are constant : 10.1. 3rd Octet is the connecting Routers ascending order,e.g. (R5-R7) : 10.1.57. 4th Octet is the Router Number itself, e.g. (R5): 10.1.57.5  So this would be the interface IP on Router 5 - Gig 0/0/2 Run OSPF on each ISP router:   Run MPLS and MPLS LDP / L2VPN on all the routers. An example from Router 8 is given. Now enable MPLS LDP remote peering on both PEs and give the same VC-ID on both sides Now ...

So in this Lab we are going to implement basic VRFs on Cisco devices. We will handle the scenario as a real world implementation scenario. Problem statement: As a service provider we are tasked with handling 3 customer & their routes. Customer are using private IP addresses. You are to devise a solution so that the customer's routes don't inter-mingle with one another. Suggested Solution: • Globally define three VRFs  • Configure sub-interfaces for Gig 0/1 on the Common SP router(vIOS)  • Assign sub-interfaces to VLAN and VRF instances  • Associate an OSPF routing process with each VRF  • Customer A (vIOS4) must be assigned to VLAN 2  • Customer B (vIOS3) must be assigned to VLAN 3  • Customer C (vIOS2) must be assigned to VLAN 4  Consider you have the following topology: Let's begin by assigning basic configs on the devices: Common SP Router Configs: ==================================================================  !  ...

Ping of Death (PoD) Attack: The Ping of Death (PoD) is a specific type of DoS attack. In a PoD attack, an attacker sends a malformed or oversized packet to a targeted machine, causing the system to crash, freeze, or reboot. Here's how it works: A correct Internet Protocol version 4 (IPv4) packet comprises a maximum of 65,535 bytes, and most legacy computers cannot handle larger packets. Sending a ping larger than this violates the IP rules, so attackers send packets in fragments which, when the targeted system attempts to reassemble, results in an oversized payload that can cause the system to crash, freeze, or reboot. Routers with no security mechanism (like a Firewall) to protect them from this flood of packets are also vulnerable.  The vulnerability can be exploited by any source that sends IP datagrams, which include an ICMP echo. Let us see through a simple lab demonstration, how it might play out. Here we have Linux with Kali distribution on EVE-NG. Directly connected to a ro...