Sponsored Content
Top Forums Programming Why am i getting these strange packets while running my packet capture module written in c.? Post 302769520 by DGPickett on Tuesday 12th of February 2013 02:04:22 PM
Old 02-12-2013
Oh, right. Protocol 0 is ipv6 except that is laid out differently, I expect: List of IP protocol numbers - Wikipedia, the free encyclopedia

Junk packets? Chase the source down!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to capture multicast packets using snoop

How do I use snoop command to capture multicast packets in the network? (1 Reply)
Discussion started by: caden312
1 Replies

2. AIX

Capture Network Packets from AIX

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)
Discussion started by: meeraramanathan
16 Replies

3. Infrastructure Monitoring

capture snmp packets in AIX

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)
Discussion started by: meeraramanathan
1 Replies

4. IP Networking

Capture packets (TcpDump) and forwarding them

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)
Discussion started by: ziedf
1 Replies

5. Programming

Receiving broadcast packets using packet socket

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)
Discussion started by: xyzt
0 Replies

6. 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

7. Programming

Linking Linux Driver written in C with ASM module

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)
Discussion started by: Chrisdot
0 Replies

8. UNIX for Advanced & Expert Users

How many packets can be written into Kernel sockets per second?

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
IPSEND(1)						      General Commands Manual							 IPSEND(1)

NAME
ipsend - sends IP packets SYNOPSIS
ipsend [ -dITUv ] [ -i <interface> ] [ -f <offset> ] [ -g <gateway> ] [ -m <MTU> ] [ -o <option> ] [ -P <protocol> ] [ -s <source> ] [ -t <dest. port> ] [ -w <window> ] <destination> [TCP-flags] DESCRIPTION
ipsend can be compiled in two ways. The first is used to send one-off packets to a destination host, using command line options to specify various attributes present in the headers. The destination must be given as the last command line option, except for when TCP flags are specified as a combination of A, S, F, U, P and R, last. The other way it may be compiled, with DOSOCKET defined, is to allow an attempt at making a TCP connection using a with ipsend resending the SYN packet as per the command line options. OPTIONS
-d enable debugging mode. -f <offset> The -f allows the IP offset field in the IP header to be set to an arbitrary value, which can be specified in decimal or hexadeci- mal. -g <gateway> Specify the hostname of the gateway through which to route packets. This is required whenever the destination host isn't directly attached to the same network as the host from which you're sending. -i <interface> Set the interface name to be the name supplied. -m <MTU> Specify the MTU to be used when sending out packets. This option allows you to set a fake MTU, allowing the simulation of network interfaces with small MTU's without setting them so. -o <option> Specify options to be included at the end of the IP header. An EOL option is automatically appended and need not be given. If an option would also have data associated with it (source as an IP# for a lsrr option), then this will not be initialised. -s <source> Set the source address in the packet to that provided - maybe either a hostname or IP#. -t <dest.port> Set the destination port for TCP/UDP packets. -w <window> Set the window size for TCP packets. -I Set the protocol to ICMP. -P <protocol> Set the protocol to the value given. If the parameter is a name, the name is looked up in the /etc/protocols file. -T Set the protocol to TCP. -U Set the protocol to UDP. -v enable verbose mode. SEE ALSO
ipresend(1), iptest(1), bpf(4), protocols(5), ipsend(5) DIAGNOSTICS
Needs to be run as root. BUGS
If you find any, please send email to me at darrenr@pobox.com IPSEND(1)
All times are GMT -4. The time now is 11:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy