Why am i getting these strange packets while running my packet capture module written in c.?
I have made an packet capture application running on intel machine, it is capturing packets with src address- 17.0.0.0 destination ip- 66.0.0.0, source port- 0, destination port- 0, and protocol- 0 what does these packets mean ?
The code written to interpreter captured bytes is given below. Which basically locate source address, destination address, source port, destination port, and protocol from various headers from packet captured. After it is done then only TCP and UDP packets are stored into a file. so it means only those packets having protocol number 6,17 should be saved but when i go through the file the packets with protocol 0,20,255,100,8,66 are also saved more over strange IP address are also seen like.2.8.2.8, 17.0.0.0, 66.0.0.0, 0.0.0.0 etc what are these packets, am i correct in my approach.
Hi,
I am using smitty to create and configure a print queue. I am giving a print of a text file to the print queue created. I am using this in network.
How to capture network packets of the print from AIX to the printer and printer to AIX.
I tried Wireshark to capture network packets.
I am... (16 Replies)
Hi,
I want to capture snmp packets in AIX.
When i give print from AIX6.1, Printer will give its response thru' snmp.
I used iptrace command like below, but it is not capturing snmp packets other packets are captured like udp, tcp..
1. iptrace command:
/usr/sbin/iptrace -a -i en0... (1 Reply)
Hi,
I want to capture a certain type of packets (selected according to the protocol) coming to my PC and then transmit them to another PC. I had the idea to use tcpdump to filter input packets and extract those chosen. Well my questions are:
1- after filtering input packets, those that have not... (1 Reply)
Hello
I try to send DHCP RENEW packets to the network and receive the responses. I broadcast the packet and I can see that it's successfully sent using Wireshark. But I have difficulties receiving the responses.I use packet sockets to catch the packets. I can see that there are responses to my... (0 Replies)
Hi, I have got sample linux driver written in C.
I got also some assembly code, compiled into .o file (using as compiler).
In my Makefile I got:
obj-m += someDriver.o
someDriver-objs := CFile1.o CFile2.o ASMFile.o
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modulesUnfortunatelly I cannot... (0 Replies)
Hi,
Its been a long time since i programmed a multithreaded application that can do Tx and Rx of datagrams over unix sockets.
I well remember that though the threads were efficiently designed to be independent of each other, and was writing to different sockets, there was a limitation ,... (0 Replies)
Discussion started by: binnyjeshan
0 Replies
LEARN ABOUT OPENSOLARIS
pflog
PFLOG(4) BSD Kernel Interfaces Manual PFLOG(4)NAME
pflog -- packet filter logging interface
SYNOPSIS
device pflog
DESCRIPTION
The pflog interface is a pseudo-device which makes visible all packets logged by the packet filter, pf(4). Logged packets can easily be mon-
itored in real time by invoking tcpdump(1) on the pflog interface, or stored to disk using pflogd(8).
The pflog0 interface is created automatically at boot if both pf(4) and pflogd(8) are enabled; further instances can be created using
ifconfig(8).
Each packet retrieved on this interface has a header associated with it of length PFLOG_HDRLEN. This header documents the address family,
interface name, rule number, reason, action, and direction of the packet that was logged. This structure, defined in <net/if_pflog.h> looks
like
struct pfloghdr {
u_int8_t length;
sa_family_t af;
u_int8_t action;
u_int8_t reason;
char ifname[IFNAMSIZ];
char ruleset[PF_RULESET_NAME_SIZE];
u_int32_t rulenr;
u_int32_t subrulenr;
uid_t uid;
pid_t pid;
uid_t rule_uid;
pid_t rule_pid;
u_int8_t dir;
u_int8_t pad[3];
};
EXAMPLES
Create a pflog interface and monitor all packets logged on it:
# ifconfig pflog1 up
# tcpdump -n -e -ttt -i pflog1
SEE ALSO tcpdump(1)inet(4), inet6(4), netintro(4), pf(4), ifconfig(8), pflogd(8)HISTORY
The pflog device first appeared in OpenBSD 3.0.
BSD December 10, 2001 BSD