GNS3 Talks: Ostinato Packet Generator - Craft packets to hack network devices (Ostinato Part 5)

Key Takeaways

this is one of multiple videos explaining and demonstrating the package generation tool Austrian Otto [Music] in this example I have a network consisting of a switch there's an i/o 8v layer to switch with two routers connected to the switch as well as to Ostia Nardo devices in this video I'm going to demonstrate how you can poison the MAC address table of a switch by generating traffic from an osteon or a node in this topology router 1 is configured with an IP address of 10111 [Music] brought a to has an IP address of ten one one two and write a one can ping routed to show up shows us that the local router writer one has this IP address and this MAC address right at 2 has this IP address and this MAC address we can verify that by looking at the running config this is the IP address and MAC address of Radha 1 and this is the IP address and MAC address of routed to so at the moment Radha too is able to ping Radha 1 so the pings are succeeding and if we look at the MAC address table of the switch we can see that Radha 1 is connected to gigabit 2 0 2 which is correct per our genus 3 topology and Radha 2 is connected to gigabit 0 3 which is true again per our topology so the MAC address table has been populated with dynamic MAC addresses versa layer 2 switch has learnt where router 1 and write a 2 are in the topology and the MAC address table is populated accordingly with those MAC addresses now however we're going to mess with the network Czestochowa loud so what I'll do here and start a Faustian order and on the first interface of the port group I'm going to create a new stream and I'm going to call this genus 3 hack hack 1 double click on the COG and let's forge a packet so it's going to be Ethernet - in this case it's going to be IP version 4 I'm going to create an ICMP packet the destination MAC address is going to be routed to the source MAC address is going to be writer 1 so I'm going to be using the writers MAC addresses as the source and destination of this packet it'll beneath in at - frame source IP address is going to be 10111 destination is going to be 10 1 1 2 so I'm forging a packet from router 1 that's an ICMP packet so the source IP address is a Rotter 1 it's an ICMP echo will leave the payload at the default value this is what the package looks like source destination it's IP version 4 its ICMP which we can see over here type is 8 in other words ICMP echo request so router to you we can ping writer 1 but notice what happens when we change the packet stream to let's say a hundred thousand packets sent at 0.0001 seconds click OK we have to apply this configuration click port 1 click play notice what happens now when rider two tries to ping brighter one but things are failing [Music] so show MAC address table notice it looks like writer one is connected to gigabit zero zero when actual fact it's connected to gigabit zero to Rada one is connected to gigabit - zero - but we have now missed with the MAC address table of the switch to make it believe that Rada one is connected to gigabit zero zero now because this is running engine is three the number of packets sent in a second may be limited but notice now router 2 is not able to ping router one is rather one able to ping rotted - yes it can but when we go back to the MAC address table it's now been updated that has changed back to give it a zero zero if you had a hardware device sending the number of packets that I've specified here at the load delay that we specified this would update a lot quicker but it's limited in our gns3 topology notice that - the pings succeed and then they stop succeeding because the MAC address table of the switch has been poisoned again if you had a hardware device generating a huge number of frames you would very quickly poison the network and stop devices sending traffic to one another but the result here is the same MAC address table is poisoned router to is no longer able to ping router 1 so that's an example of how to use Asti annatto to poison the MAC address tables of switches and affect how traffic is sent through the network address table share have been poisoned effectively by the traffic sent by Ostia natto we can see the traffic sent on that link so you can see all of these echo requests sent by the Ostia node a node causing trouble on the network I hope you enjoyed the video if it's been a benefit to you please like it and please subscribe to my youtube channel I wish you all the very best