mets634 / packet-crafting Goto Github PK

Currently, the library leaks many details about the API. For example, packet:show prints the inner representation of the packet. Also, there is no protection from the user. If the user decides to add arbitrary data to a packet, it will work. We should conceal and protect the internals of the library. This should be done on the library as a whole, and also between the packages.

When constructing network layers, there are some constraints that apply to some of the fields. For example, a field representing a checksum should be checked that its value is correct. We should support using constraints on BSL structures.

We should define and create tests for the library.

Many network packets have raw data. We should add a network layer that supports this.

We should also fill out the data in README.md

Currently, all of a packet's layers are looked upon as integers. We should add a method of pretty printing and reading of the layer's values. For example, IPs should be represented like so "127.0.0.1" instead of an integer.

We should have a method of creating new network layer structures, such that it will be very easy to add new layers. This means creating a mini-language (called BSL - Binary Structure Layer), that will allow expressing the network layers. BSL must support (in the meantime):

1. Specifying field names.
2. Specifying field sizes in bits.
3. Specifying default values for the fields (or not allowing default values).
4. Specifying constraints on the allowed values.

We should have a way to layer different network layers one on top of the other.

We need to be able to serialize and deserialize packet to binary data (raw files) as well as to libpcap files. The libpcap format is as specified here: https://wiki.wireshark.org/Development/LibpcapFileFormat with the current version being 2.4.

Some network packets have fields that aren't required (like IPv4's options). We should add a way to use this in BSL.