[Thomas_Shelby]

I'm trying to code an ARP cache poisoning program in Python (for learning purposes), using Scapy.

My program does the following steps:

• scans all of the devices on the LAN (using ARP Ping packets).
  


• Lets the user to choose an IP to attack, and then poisoning the ARP cache of the router and the victim, using fake ARP packets in Scapy.
  

In addition, I've enabled IP Forwarding in order to keep, the connection between the victim and the router, working properly.

My program works, but:
My problem is whenever I use this code on a victim in my LAN, it really slows down the victim's internet connection and sometimes even stops his internet connection.
I've been trying to google it a lot and didn't find any reason for the slow down and the loss of connection. I'll be glad to have some help!🕵️

[linkinpork]

I'm trying to code an ARP cache poisoning program in Python (for learning purposes), using Scapy.

My program does the following steps:

• scans all of the devices on the LAN (using ARP Ping packets).
  


• Lets the user to choose an IP to attack, and then poisoning the ARP cache of the router and the victim, using fake ARP packets in Scapy.
  

In addition, I've enabled IP Forwarding in order to keep, the connection between the victim and the router, working properly.

My program works, but:
My problem is whenever I use this code on a victim in my LAN, it really slows down the victim's internet connection and sometimes even stops his internet connection.
I've been trying to google it a lot and didn't find any reason for the slow down and the loss of connection. I'll be glad to have some help!🕵️

Correct me if I'm wrong, but here's how I understand the concept.

When you do ARP poisoning, you have to process each packet that goes back and forth. Every packet needs to be accessed, re-written, then re-sent.

The problem there is that the attacker machine's processing power might not be as powerful as that of the router bandwidth. Even worse when the packet is encrypted (as is the case with SSL/TLS/HTTPS).

Fix: Get a faster rig, from network card to RAM to CPU.

[Thomas_Shelby]

Correct me if I'm wrong, but here's how I understand the concept.

When you do ARP poisoning, you have to process each packet that goes back and forth. Every packet needs to be accessed, re-written, then re-sent.

The problem there is that the attacker machine's processing power might not be as powerful as that of the router bandwidth. Even worse when the packet is encrypted (as is the case with SSL/TLS/HTTPS).

Fix: Get a faster rig, from network card to RAM to CPU.

It really makes sense when I think about it in that way. I wanted to make sure that the problem isn't in my implementation. Thanks!!!