What makes scapy different from most other networking tools
First, with most other tools, you won’t build someting the author did not imagine. These tools have been built for a specific goal and can’t deviate much from it. For example, an ARP cache poisoning program won’t let you use double 802.1q encapsulation. Or try to find a program that can send, say, an ICMP packet with padding (I said padding, not payload, see?). In fact, each time you have a new need, you have to build a new tool. Second, they usually confuse decoding and interpreting. Machines are good at decoding and can help human beings with that. Interpretation is reserved to human beings. Some programs try to mimic this behaviour. For instance they say “this port is open” instead of “I received a SYN-ACK”. Sometimes they are right. Sometimes not. It’s easier for beginners, but when you know what you’re doing, you keep on trying to deduce what really happened from the program’s interpretation to make your own, which is hard because you lost a big amount of information. And you often end up using tcpdump -xX to decode and interpret what the tool missed.
Third, even programs which only decode do not give you all the information they received. The network’s vision they give you is the one their author thought was sufficient. But it is not complete, and you have a bias. For instance, do you know a tool that reports the padding ?
Scapy tries to overcome those problems. It enables you to build exactly the packets you want. Even if I think stacking a 802.1q layer on top of TCP has no sense, it may have some for somebody else working on some product I don’t know. Scapy has a flexible model that tries to avoid such arbitrary limits. You’re free to put any value you want in any field you want, and stack them like you want. You’re an adult after all.
In fact, it’s like building a new tool each time, but instead of dealing with a hundred line C program, you only write 2 lines of Scapy.
After a probe (scan, traceroute, etc.) Scapy always gives you the full decoded packets from the probe, before any interpretation. That means that you can probe once and interpret many times, ask for a traceroute and look at the padding for instance.
Scapy runs natively on Linux, and on most Unixes with libpcap, libdnet and their respective python wrapper (see scapy’s portability page). Scapy < 2.x needs Python 2.4 or upcomming versions.
Scapy ≥ 2.x needs Python 2.5 or upcomming versions.
- Scapy’s latest release (executable zip)
- Scapy’s latest release (tar.gz) (take this one if your system says the zip is corrupted)
- Scapy’s latest revision
- Scapy’s debian package (not always up to date)
- Scapy’s RPM package (not always up to date)
- Scapytain: a web application to store, organise and run test campaigns on top of Scapy
- UTscapy: Unit Testing with scapy (integrated with Scapy 2.x)
- WifiTap: Wi-Fi traffic injection
- local copy of Scapy OLSR add-on
Send questions, bug reports, suggestions, ideas, cool usages of Scapy, etc. To avoid spam, you must subscribe to the mailing list to post.
- To subscribe to the mailing-list, send a mail to scapy.ml-subscribe(at)secdev.org
- To send a mail to the mailing-list: scapy.ml(at)secdev.org
- Web archive : http://news.gmane.org/gmane.comp.security.scapy.general
- NNTP, RSS, etc : http://gmane.org/info.php?group=gmane.comp.security.scapy.general
- Official Online HTML documentation
- Security Power Tools where I wrote a complete chapter about Scapy.
- Quick demo: an interactive session
- Building your own tools with Scapy
- Scapy portability page
- You will also find an article in the French Linux Magazine #52
- Report bugs/wishes/patches here
- Active tickets here
- Scapy’s PacSec/core05 slides (printable version)
- Scapy’s Hack.lu 2005 slides
- Scapy’s Summerschool Applied IT Security 2005 slides
- Scapy’s T2’2005 slides
- Scapy’s CanSecWest/core05 slides
- Scapy’s LSM 2003 slides
Other documents on Scapy :
- A Scapy tutorial: Packet Wizardry: Ruling the Network with Python by Rob klein Gunnewiek.
- (now outdated) Scapy installation on OpenBSD 3.8 howto
Scapy development uses Mercurial version control system. Scapy reference repository is at http://hg.secdev.org/scapy/. Project management is done with Trac. Trac works on Scapy’s reference repository. It provides a freely editable wiki (please contribute!) that can reference tickets, changesets, files from the project. It also provides a ticket management service that I use to avoid forgetting patches or bugs. Mercurial distributed way of working enables me to provide two repositories where anybody can commit stuff: the Scapy community repository.
- Scapy’s Trac Freely editable wiki (submit stuff!), tickets, repository browsing and project timeline
- Scapy’s community repository. Anybody can commit patches here!
- Session management
- Link layer not well managed yet
- Does not give the right source IP for routes that use interface aliases (/proc/net/route reports only master interface)
- DNS packets not reassembled exactly as the original (no compression used)
- May miss packets under heavy load
- BPF filters do not work on PPP interfaces