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 PLAN9
snoopy
SNOOPY(8) System Manager's Manual SNOOPY(8)NAME
snoopy - spy on Ethernet packets
SYNOPSIS
snoopy [ -abceiltup9 ] [ -np ] [ -N count ]
DESCRIPTION
Snoopy displays the header and first 20 data bytes of packets received from the local Ethernet. The packets displayed depend on the
options chosen. The following options each select packets from a particular protocol. If more than one flag is given, packets from all
those protocols are displayed.
a ARP
b BOOTP
c ICMP
e all Ethernet packets
i IP
l IL
t TCP
u UDP
By default all addresses are translated into system names. The option n suppresses this.
Snoopy runs in promiscuous mode by default, displaying all packets it can capture from the Ethernet. The option p causes only packets sent
to or from the system snoopy is running on to be displayed.
Option 9 causes the data of TCP and IL messages to be interpreted and displayed as 9P messages. The N option sets the count (default 20)
of the number of bytes to dump in hexadecimal from each packet.
FILES
/net/ether
Ethernet device
SOURCE
/sys/src/cmd/ip/snoopy.c
BUGS
The CPU servers do not take well to running in promiscuous mode. If run on them, snoopy may kill their Ethernets.
SNOOPY(8)