http://qs321.pair.com?node_id=1155187


in reply to Re^3: ARP poisoning and redirection
in thread ARP poisoning and redirection

I will quote my first post and explain it since it seems it was not clear enough:
First, in bold:

I do not intend to use on any network that is not mine to own and rule other as I see fit meaning made of machines I own as in paid for.
Since the networking workshop is not made of machines that I own as stated in the first post I fail to see where I implied I would use my script in that setting.

Next thing, if you had taken the time to read the code in said first post as well as that sentence:
The idea came to me after other students told me that during the networking workshops at uni great pranks were to be played on unsuspecting marks : since all computers shared the same login and password one could decide to log into someone else's computer and either eject the legitimate user or reboot the machine.
You would have understood that I am not trying either a DoS or an ARP hijacking (which is quite obvious if you just read the arp part of my code) but hey lets clarify that too.
I am trying to tell a potential attacker that my machine has someone else's mac address. It is the opposite of an arp hijacking. The goal is to have their frames sent somewhere else in such a way that they will not be able to cause harm.

Now onto the next thing, I would be most grateful if you were to explain to me in what way this is <q>script-kiddie code</q>. I am only a neophyte when it comes to network protocols or perl and I know I have a lot of things to learn but I fail to see where this code could be used to either DOS or arp hijack without so much of rewriting it would be equivalent to start from scratch. But do enlighten me so I do not make the same mistake again.