Ever worried about these disgusting packets leaving your network interface!? Why not creating your own packets?
Of course it’s more than nonsense creating all packets on your own, but sometimes there might be a reason making you wish you could..
For ex. for my last article I searched for a possibility to modify some contents of a packet. First I thought about using
iptables , but than I found a nice tool: scapy!
To open the interface just run
scapy . You can easily create an IP packet by typing something like this:
So an IP packet is stored in the variable
ippacket . This packet will be send to
binfalse.de and has a
12 (if there are more than 12 network nodes between your machine and the target it will disappear and never arrive at the target).
Let’s create some TCP stuff:
We stored some TCP information in
tcpcrap . This packet will be send through your port
1337 and hopefully arrive at port
80 (in general a webserver is listening on port
That’s it for the networking part. Last but not least we will create some data to send:
Combining all parts we’ll get a very nice packet, sending it will trigger my webserver to send the main page of my website (Sending exactly this packet won’t ever result in any website from my webserver. Why? Just think about…):
Well done! Ok, that’s very much to do. But fortunately it’s just that much code for explanation, you can send the same packet in a single line:
Very smart, isn’t it? You can also sniff whooshing packets! But something like this I won’t explain, find out by yourself ;-)
- analyzed (14) ,
- aptitude (12) ,
- crazy (8) ,
- debian (35) ,
- explained (36) ,
- hacked (25) ,
- network (73) ,
- remote (17) ,
- trick (55)