1 .\" Copyright (c) 1994, 1996, 1997
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that: (1) source code distributions
6 .\" retain the above copyright notice and this paragraph in its entirety, (2)
7 .\" distributions including binary code include the above copyright notice and
8 .\" this paragraph in its entirety in the documentation or other materials
9 .\" provided with the distribution, and (3) all advertising materials mentioning
10 .\" features or use of this software display the following acknowledgement:
11 .\" ``This product includes software developed by the University of California,
12 .\" Lawrence Berkeley Laboratory and its contributors.'' Neither the name of
13 .\" the University nor the names of its contributors may be used to endorse
14 .\" or promote products derived from this software without specific prior
15 .\" written permission.
16 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
17 .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
18 .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
20 .TH PCAP_INJECT 3PCAP "23 November 2024"
22 pcap_inject, pcap_sendpacket \- transmit a packet
26 #include <pcap/pcap.h>
30 int pcap_inject(pcap_t *p, const void *buf, size_t size);
31 int pcap_sendpacket(pcap_t *p, const u_char *buf, int size);
36 sends a raw packet through the network interface;
38 points to the data of the packet, including the link-layer header, and
40 is the number of bytes in the packet.
42 Note that, even if you successfully open the network interface, you
43 might not have permission to send packets on it, or it might not support
45 .BR pcap_open_live (3PCAP)
46 doesn't have a flag to indicate whether to open for capturing, sending,
47 or capturing and sending, you cannot request an open that supports
48 sending and be notified at open time whether sending will be possible.
49 The same limitation applies to
50 .BR \%pcap_create (3PCAP)
52 .BR \%pcap_activate (3PCAP).
53 Note also that some devices might not support sending packets.
55 Note that, on some platforms, the link-layer header of the packet that's
56 sent might not be the same as the link-layer header of the packet
59 as the source link-layer address, if the header contains such an
60 address, might be changed to be the address assigned to the interface on
61 which the packet it sent, if the platform doesn't support sending
62 completely raw and unchanged packets. Even worse, some drivers on some
63 platforms might change the link-layer type field to whatever value
64 libpcap used when attaching to the device, even on platforms that
66 nominally support sending completely raw and unchanged packets.
68 .BR pcap_sendpacket ()
73 on success, rather than returning the number of bytes
77 .BR pcap_sendpacket ()
78 comes from WinPcap/Npcap. Both are provided for compatibility.)
81 returns the number of bytes written on success,
82 .B PCAP_ERROR_NOT_ACTIVATED
83 if called on a capture handle that has been created but not activated, and
87 .BR pcap_sendpacket ()
91 .B PCAP_ERROR_NOT_ACTIVATED
92 if called on a capture handle that has been created but not activated, and
99 .BR pcap_geterr (3PCAP)
101 .BR pcap_perror (3PCAP)
104 as an argument to fetch or display the error text.