Uses of Class com.voytechs.jnetstream.io.ProtocolDataInputStream

Overview

Package

Class

Use

Deprecated

Index

Home >> All >> com >> voytechs >> jnetstream >> [ io overview ]

PREV NEXT

Uses of Class
com.voytechs.jnetstream.io.ProtocolDataInputStream

Uses of ProtocolDataInputStream in com.voytechs.jnetstream.io

Subclasses of ProtocolDataInputStream in com.voytechs.jnetstream.io

class PacketInputStream
          Stream object that reads either an InputStream of bytes and allows access to the byte stream with the following features:
1) data can be read in either bytes or individual bits.
2) position within the stream can be pushed on to a stack
3) position can be poped off of the stack.
4) a packet structure is imposed on the stream so that you can query or be notified when the end of an individual packet byte stream is over and when the next packet byte stream is beginning.
5) data can be read in any binary format (Big Endian or Little Endian)
6) Packet capture information is accessable, such as:
a) IP address of the capture device.
b) interface or filename the packet was captured on.
c) capture time of the packet
d) length of the entire packet in bytes
e) OS name of the capture device
d) OS version of the capture device

class PcapInputStream
          Structure of TCPDump file.
struct pcap_file_header { bpf_u_int32 magic; u_short version_major; u_short version_minor; bpf_int32 thiszone; // gmt to local correction // bpf_u_int32 sigfigs; // accuracy of timestamps // bpf_u_int32 snaplen; // max length saved portion of each pkt // bpf_u_int32 linktype; // data link type (LINKTYPE_*) // };

Now per each packet:
struct pcap_pkthdr { struct timeval ts; // time stamp // bpf_u_int32 caplen; // length of portion present // bpf_u_int32 len; // length this packet (off wire) // };

class RawformatInputStream


class SnoopInputStream
          For structure of the Snoop file see RFC1761 http://www.faqs.org/rfcs/rfc1761.html