Sponsored Content
Full Discussion: Writing a Packet sniffer
Top Forums Programming Writing a Packet sniffer Post 302313052 by nefarious_genus on Monday 4th of May 2009 01:34:43 PM
Old 05-04-2009
Writing a Packet sniffer

Hi,
I want to write a packet sniffer in C without using libpcap. Can anyone suggest me how to begin writing it? Any tutorials or books?

Thanks in advance!
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

key sniffer

Hi everybody, I'll like to know how I can add in my script a key sniffer. In fact, I'll like to detect a "Ctrl + C" command... How can do that and is it possible in shell script under AIX ? Thanks !!! Dimitri (1 Reply)
Discussion started by: dfrangidis
1 Replies

2. IP Networking

Seeing IP packet

Hi, Is there any way that i can directly take out the IP packet and see its contents. Waiting for your answer .............. Bye (4 Replies)
Discussion started by: manjunath
4 Replies

3. IP Networking

regarding sniffer

hi this is munna. am doing a program about sniffer. if the user can delete the file from /root/.mozilla/firefox/27a5g6oo.default history.dat or he/she can do in browser window edit->preferences->privacy->history as "0"(zero). (remember visted pages for the last 0 days). ... (3 Replies)
Discussion started by: munna_dude
3 Replies

4. Programming

packet capture

can anyone tell me how can i capture the packets. i have tried ethernet software to capture them but its not doing what i want it to do it (1 Reply)
Discussion started by: dazdseg
1 Replies

5. IP Networking

Packet decoding

Hi, wondering if anyone can suggest a tool to me that will let me either cut & paste hex or type it in for packet decoding. I want to be able to decode a packet as done with tcpdump or wireshark, but I want to be able to manually input the hex myself. (2 Replies)
Discussion started by: Breakology
2 Replies

6. Cybersecurity

filter packet

Exercise: Protection of WEB and DNS servers using the context-free rules for packet filtering: - Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns. - Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies

7. Homework & Coursework Questions

filter packet

Exercise: Protection of WEB and DNS servers using the context-free rules for packet filtering: - Protect your WEB-server, so that would be for him can be accessed by browsers, and could go to dns. - Protect your primary DNS-server so that it could be to contact clients and secondary servers.... (1 Reply)
Discussion started by: numeracy
1 Replies

8. Programming

Raw Socket Programming - Efficient Packet Sniffer

Hi, I have the requirement to sniff packets from the Ethernet card on my Linux machine and process it and feed it to a RANAP protocol stack. So far I have written the raw packet sniffer and successfully sniffing packets and do little processing. However, for huge number of packets ... (9 Replies)
Discussion started by: rstnsrr
9 Replies

9. AIX

Packet loss coming with big packet size ping

(5 Replies)
Discussion started by: Vishal_dba
5 Replies
PCAP-SAVEFILE(5@)														 PCAP-SAVEFILE(5@)

NAME
pcap-savefile - libpcap savefile format DESCRIPTION
NOTE: applications and libraries should, if possible, use libpcap to read savefiles, rather than having their own code to read savefiles. If, in the future, a new file format is supported by libpcap, applications and libraries using libpcap to read savefiles will be able to read the new format of savefiles, but applications and libraries using their own code to read savefiles will have to be changed to support the new file format. ``Savefiles'' read and written by libpcap and applications using libpcap start with a per-file header. The format of the per-file header is: +------------------------------+ | Magic number | +--------------+---------------+ |Major version | Minor version | +--------------+---------------+ | Time zone offset | +------------------------------+ | Time stamp accuracy | +------------------------------+ | Snapshot length | +------------------------------+ | Link-layer header type | +------------------------------+ All fields in the per-file header are in the byte order of the host writing the file. The first field in the per-file header is a 4-byte magic number, with the value 0xa1b2c3d4. The magic number, when read by a host with the same byte order as the host that wrote the file, will have the value 0xa1b2c3d4, and, when read by a host with the opposite byte order as the host that wrote the file, will have the value 0xd4c3b2a1. That allows software reading the file to determine whether the byte order of the host that wrote the file is the same as the byte order of the host on which the file is being read, and thus whether the values in the per-file and per-packet headers need to be byte- swapped. Following this are: A 2-byte file format major version number; the current version number is 2. A 2-byte file format minor version number; the current version number is 4. A 4-byte time zone offset; this is always 0. A 4-byte number giving the accuracy of time stamps in the file; this is always 0. A 4-byte number giving the "snapshot length" of the capture; packets longer than the snapshot length are truncated to the snapshot length, so that, if the snapshot length is N, only the first N bytes of a packet longer than N bytes will be saved in the capture. a 4-byte number giving the link-layer header type for packets in the capture; see pcap-linktype(7) for the LINKTYPE_ values that can appear in this field. Following the per-file header are zero or more packets; each packet begins with a per-packet header, which is immediately followed by the raw packet data. The format of the per-packet header is: +---------------------------------------+ | Time stamp, seconds value | +---------------------------------------+ | Time stamp, microseconds value | +---------------------------------------+ | Length of captured packet data | +---------------------------------------+ |Un-truncated length of the packet data | +---------------------------------------+ All fields in the per-packet header are in the byte order of the host writing the file. The per-packet header begins with a time stamp giving the approximate time the packet was captured; the time stamp consists of a 4-byte value, giving the time in seconds since January 1, 1970, 00:00:00 UTC, followed by a 4-byte value, giving the time in microseconds since that second. Following that are a 4-byte value giv- ing the number of bytes of captured data that follow the per-packet header and a 4-byte value giving the number of bytes that would have been present had the packet not been truncated by the snapshot length. The two lengths will be equal if the number of bytes of packet data are less than or equal to the snapshot length. SEE ALSO
pcap(3PCAP), pcap-linktype(7) 21 October 2008 PCAP-SAVEFILE(5@)
All times are GMT -4. The time now is 06:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy