mpac v1.01 README file
Byron Sonne (blsonne@home.com)

Legal shite:

    First off, I'm too lazy to plaster my copyrights all over each file...
    So mangle all mpac files all you want, but if you keep anything original,
    you must keep the original creds. If you make any interesting mods to it
    or come up with some new and useful datafiles, I'd be interested in
    getting a copy for my own edification and for the purposes of improving 
    the program. That, and I'd like to assemble a 'library' of packet data 
    files for inclusion in future releases.

    Secondly, I assume no responsibility whatsoever for whatever people choose
    to do with mpac. I wrote it as an exploratory program so I could learn 
    more about programming and networks, and 'cos I think you should be able
    to poke around wherever you want, in your own computers or networks.

    BTW, since I intended to make mpac a freely distributable program with no
    costs attached, you are now under the moral obligation to apply this same
    condition to any and all mods or hacks you make to or from the program.
    If you don't... well, it's your karma. 
    The only exception made in this case is for inclusion on a distro.

Note to the wary:

    This program is not written as efficiently as possible; I am only a
    novice programmer and thus am not always sure where my towel is.
    The next version should include a major rewrite of, oh, everything...
    as well as being able to mess with TCP and IP options. Freow!

    This was written under Linux kernel 2.2.11. I have not tested it on any
    other kernels, nor on any other OS (Sorry... I scavenged my FreeBSD
    box some time ago for parts and haven't got around to putting another
    one together). 

Use:     

    If unsure, you can always just type ./mpac and have it print out the
    usage. Otherwise, it is this:

        ./mpac -p <payload file> -t <tcp file> -i <ip file> -e <ethernet file>

    Each of the files that are read in have a specific format, I've included a
    couple of example files so you can see what it ought to look like. It is
    fairly straightforward. Please note that these datafiles do not
    necessarily contain valid packet data. Otherwise, check the source. It
    should be of help.
 
    It really pays to run a nice sniffer while first using this program, as
    it will help you see exactly what you are manipulating. This way, if
    can't get the answers from one of these files or out of a book, or
    wherever, you can deduce it.

Misc:

    Thanks to Mike D. Schiffman and route|daemon9 for the answers and 
    information.

eof
