summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSam Roberts <sroberts@sroberts-desktop.(none)>2009-02-23 12:49:52 -0800
committerSam Roberts <sroberts@sroberts-desktop.(none)>2009-02-23 12:49:52 -0800
commitdb45548b76ab85dfa4c41f60a233581c62698456 (patch)
tree5e28a3b3ecc3ad673bf61886ac426a3152afa70f
parentc9b3d5477131b6adbe8480fa8077186c4632d2a6 (diff)
downloadlibnet-db45548b76ab85dfa4c41f60a233581c62698456.tar.gz
01-fix_libnet-functions.h.3.patch from debian source package
See http://packages.debian.org/source/sid/libnet
-rw-r--r--libnet/doc/man/man3/libnet-functions.h.3189
1 files changed, 95 insertions, 94 deletions
diff --git a/libnet/doc/man/man3/libnet-functions.h.3 b/libnet/doc/man/man3/libnet-functions.h.3
index 6ebbfad..5b821d0 100644
--- a/libnet/doc/man/man3/libnet-functions.h.3
+++ b/libnet/doc/man/man3/libnet-functions.h.3
@@ -485,7 +485,7 @@ Should document this baby right here.
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -504,7 +504,7 @@ Should document this baby right here.
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -535,7 +535,7 @@ Should document this baby right here.
.PP
\fBReturns:\fP
.RS 4
-the number of bytes written, or -1 on failure
+the number of bytes written, or \-1 on failure
.RE
.PP
@@ -560,7 +560,7 @@ Autouilds an Address Resolution Protocol (ARP) header. Depending on the op value
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -579,7 +579,7 @@ Autobuilds an Ethernet header. The RFC 894 Ethernet II header is almost identica
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -606,7 +606,7 @@ Autobuilds a Fiber Distributed Data Interface (FDDI) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -627,7 +627,7 @@ Autobuilds a version 4 Internet Protocol (IP) header. The function is useful * t
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -654,7 +654,7 @@ This function is not yet implement and is a NONOP.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -675,7 +675,7 @@ Automatically builds a link layer header for an initialized l. The function dete
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -706,7 +706,7 @@ Auto-builds a token ring header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -741,7 +741,7 @@ Builds an IEEE 802.1q VLAN tagging header. Depending on the value of len_proto,
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -768,7 +768,7 @@ Builds an IEEE 802.1x extended authentication protocol header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -795,7 +795,7 @@ Builds an IEEE 802.2 LLC header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -826,7 +826,7 @@ Builds an IEEE 802.2 LLC SNAP header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -853,7 +853,7 @@ Builds an IEEE 802.3 header. The 802.3 header is almost identical to the RFC 894
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -892,13 +892,14 @@ Builds an Address Resolution Protocol (ARP) header. Depending on the op value, t
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
.SS "libnet_ptag_t libnet_build_bgp4_header (u_int8_t marker[LIBNET_BGP4_MARKER_SIZE], u_int16_t len, u_int8_t type, u_int8_t * payload, u_int32_t payload_s, libnet_t * l, libnet_ptag_t ptag)"
.PP
-Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) header. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASs) that reachability information traverses. This information is sufficient to construct a graph of AS connectivity from which routing loops may be pruned and some policy decisions at the AS level may be enforced. This function builds the base BGP header which is used as a preamble before any other BGP header. For example, a BGP KEEPALIVE message may be built with only this function, while an error notification requires a subsequent call to libnet_build_bgp4_notification.
+Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) header. The primary function of a BGP speaking system is to exchange network reachability
+information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASs) that reachability information traverses. This information is sufficient to construct a graph of AS connectivity from which routing loops may be pruned and some policy decisions at the AS level may be enforced. This function builds the base BGP header which is used as a preamble before any other BGP header. For example, a BGP KEEPALIVE message may be built with only this function, while an error notification requires a subsequent call to libnet_build_bgp4_notification.
.PP
\fBParameters:\fP
.RS 4
@@ -919,7 +920,7 @@ Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) header. The primary functio
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -944,7 +945,7 @@ Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) notification header. A NOTI
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -975,7 +976,7 @@ Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) OPEN header. This is the fi
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1008,7 +1009,7 @@ Builds an RFC 1771 Border Gateway Protocol 4 (BGP-4) update header. Update messa
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1027,7 +1028,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1060,7 +1061,7 @@ Builds a Cisco Discovery Protocol (CDP) header. Cisco Systems designed CDP to ai
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1081,7 +1082,7 @@ Builds a generic libnet protocol header. This is useful for including an optiona
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1100,7 +1101,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1133,13 +1134,13 @@ Builds an RFC 1035 version 4 DNS header. Additional DNS payload information shou
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
.SS "libnet_ptag_t libnet_build_egre (u_int16_t fv, u_int16_t type, u_int16_t sum, u_int16_t offset, u_int32_t key, u_int32_t seq, u_int16_t len, u_int8_t * payload, u_int32_t payload_s, libnet_t * l, libnet_ptag_t ptag)"
.PP
-Generic Routing Encapsulation (GRE - RFC 1701) is used to encapsulate any protocol. Hence, the IP part of the packet is usually referred as 'delivery header'. It is then followed by the GRE header and finally the encapsulated packet (IP or whatever). As GRE is very modular, the first GRE header describes the structure of the header, using bits and flag to specify which fields will be present in the header.
+Generic Routing Encapsulation (GRE \- RFC 1701) is used to encapsulate any protocol. Hence, the IP part of the packet is usually referred as 'delivery header'. It is then followed by the GRE header and finally the encapsulated packet (IP or whatever). As GRE is very modular, the first GRE header describes the structure of the header, using bits and flag to specify which fields will be present in the header.
.PP
\fBParameters:\fP
.RS 4
@@ -1168,7 +1169,7 @@ Generic Routing Encapsulation (GRE - RFC 1701) is used to encapsulate any protoc
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1195,7 +1196,7 @@ Builds an Ethernet header. The RFC 894 Ethernet II header is almost identical to
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1228,13 +1229,13 @@ Builds a Fiber Distributed Data Interface (FDDI) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
.SS "libnet_ptag_t libnet_build_gre (u_int16_t fv, u_int16_t type, u_int16_t sum, u_int16_t offset, u_int32_t key, u_int32_t seq, u_int16_t len, u_int8_t * payload, u_int32_t payload_s, libnet_t * l, libnet_ptag_t ptag)"
.PP
-Generic Routing Encapsulation (GRE - RFC 1701) is used to encapsulate any protocol. Hence, the IP part of the packet is usually referred as 'delivery header'. It is then followed by the GRE header and finally the encapsulated packet (IP or whatever). As GRE is very modular, the first GRE header describes the structure of the header, using bits and flag to specify which fields will be present in the header.
+Generic Routing Encapsulation (GRE \- RFC 1701) is used to encapsulate any protocol. Hence, the IP part of the packet is usually referred as 'delivery header'. It is then followed by the GRE header and finally the encapsulated packet (IP or whatever). As GRE is very modular, the first GRE header describes the structure of the header, using bits and flag to specify which fields will be present in the header.
.PP
\fBParameters:\fP
.RS 4
@@ -1263,7 +1264,7 @@ Generic Routing Encapsulation (GRE - RFC 1701) is used to encapsulate any protoc
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1282,7 +1283,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1301,7 +1302,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1332,7 +1333,7 @@ Builds an IP version 4 RFC 792 Internet Control Message Protocol (ICMP) echo req
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1365,7 +1366,7 @@ Builds an IP version 4 RFC 792 Internet Control Message Protocol (ICMP) IP netma
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1406,7 +1407,7 @@ Builds an IP version 4 RFC 792 Internet Message Control Protocol (ICMP) redirect
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1449,7 +1450,7 @@ Builds an IP version 4 RFC 792 Internet Control Message Protocol (ICMP) time exc
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1486,7 +1487,7 @@ Builds an IP version 4 RFC 792 Internet Control Message Protocol (ICMP) timestam
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1527,7 +1528,7 @@ Builds an IP version 4 RFC 792 Internet Control Message Protocol (ICMP) unreacha
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1556,7 +1557,7 @@ Builds an RFC 1112 Internet Group Memebership Protocol (IGMP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1589,7 +1590,7 @@ Builds an Internet Protocol Security Authentication header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1616,7 +1617,7 @@ Builds an Internet Protocol Security Encapsulating Security Payload footer.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1643,7 +1644,7 @@ Builds an Internet Protocol Security Encapsulating Security Payload header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1682,7 +1683,7 @@ Builds a version 4 RFC 791 Internet Protocol (IP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1703,7 +1704,7 @@ Builds an version 4 Internet Protocol (IP) options header. The function expects
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1738,7 +1739,7 @@ Builds a version 6 RFC 2460 Internet Protocol (IP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1763,7 +1764,7 @@ Builds a version 6 RFC 2460 Internet Protocol (IP) destination options header. T
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1792,7 +1793,7 @@ Builds a version 6 RFC 2460 Internet Protocol (IP) fragmentation header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1817,7 +1818,7 @@ Builds a version 6 RFC 2460 Internet Protocol (IP) hop by hop options header. Th
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1844,7 +1845,7 @@ Builds a version 6 RFC 2460 Internet Protocol (IP) routing header. This function
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1883,7 +1884,7 @@ Builds a Cisco Inter-Switch Link (ISL) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1912,7 +1913,7 @@ Builds a link layer header for an initialized l. The function determines the pro
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -1941,7 +1942,7 @@ Builds an RFC 3032 Multi-Protocol Label Switching (MPLS) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2000,7 +2001,7 @@ Builds an RFC 958 Network Time Protocol (NTP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2019,7 +2020,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2038,7 +2039,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2057,7 +2058,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2076,7 +2077,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2095,7 +2096,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2114,7 +2115,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2133,7 +2134,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2152,7 +2153,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2171,7 +2172,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2190,7 +2191,7 @@ protocol tag value on success, -1 on error
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2229,7 +2230,7 @@ Builds a Routing Information Protocol header (RFCs 1058 and 2453).
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2243,7 +2244,7 @@ Builds an Remote Procedure Call (Version 2) Call message header as specified in
.br
\fIxid\fP transaction identifier used to link calls and replies
.br
-\fIprog_num\fP remote program specification typically between 0 - 1fffffff
+\fIprog_num\fP remote program specification typically between 0 \- 1fffffff
.br
\fIprog_vers\fP remote program version specification
.br
@@ -2272,7 +2273,7 @@ Builds an Remote Procedure Call (Version 2) Call message header as specified in
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2315,7 +2316,7 @@ Builds a Sebek header. The Sebek protocol was designed by the Honeynet Project a
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2360,7 +2361,7 @@ Builds an IEEE 802.1d Spanning Tree Protocol (STP) configuration header. STP fra
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2387,7 +2388,7 @@ Builds an IEEE 802.1d Spanning Tree Protocol (STP) topology change notification
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2422,7 +2423,7 @@ Builds an RFC 793 Transmission Control Protocol (TCP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2443,7 +2444,7 @@ Builds an RFC 793 Transmission Control Protocol (TCP) options header. The functi
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2482,7 +2483,7 @@ Builds a token ring header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2511,7 +2512,7 @@ Builds an RFC 768 User Datagram Protocol (UDP) header.
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2523,7 +2524,7 @@ Builds an RFC 2338 Virtual Router Redundacy Protool (VRRP) header. Use the paylo
.RS 4
\fIversion\fP VRRP version (should be 2)
.br
-\fItype\fP VRRP packet type (should be 1 -- ADVERTISEMENT)
+\fItype\fP VRRP packet type (should be 1 \-\- ADVERTISEMENT)
.br
\fIvrouter_id\fP virtual router identification
.br
@@ -2531,7 +2532,7 @@ Builds an RFC 2338 Virtual Router Redundacy Protool (VRRP) header. Use the paylo
.br
\fIip_count\fP number of IPv4 addresses contained in this advertisement
.br
-\fIauth_type\fP type of authentication (0, 1, 2 -- see RFC)
+\fIauth_type\fP type of authentication (0, 1, 2 \-\- see RFC)
.br
\fIadvert_int\fP interval between advertisements
.br
@@ -2548,7 +2549,7 @@ Builds an RFC 2338 Virtual Router Redundacy Protool (VRRP) header. Use the paylo
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2575,7 +2576,7 @@ Clears the current packet referenced and frees all pblocks. Should be called whe
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -2757,7 +2758,7 @@ a pointer to the MAC address or NULL
.SS "u_int32_t libnet_get_ipaddr4 (libnet_t * l)"
.PP
-Returns the IP address for the device libnet was initialized with. If libnet was initialized without a device (in raw socket mode) the function will attempt to find one. If the function fails and returns -1 a call to libnet_geterrror() will tell you why.
+Returns the IP address for the device libnet was initialized with. If libnet was initialized without a device (in raw socket mode) the function will attempt to find one. If the function fails and returns \-1 a call to libnet_geterrror() will tell you why.
.PP
\fBParameters:\fP
.RS 4
@@ -2766,7 +2767,7 @@ Returns the IP address for the device libnet was initialized with. If libnet was
.PP
\fBReturns:\fP
.RS 4
-a big endian IP address suitable for use in a libnet_build function or -1
+a big endian IP address suitable for use in a libnet_build function or \-1
.RE
.PP
@@ -2787,7 +2788,7 @@ well, nothing yet
.SS "u_int32_t libnet_get_prand (int mod)"
.PP
-Generates an unsigned psuedo-random value within the range specified by mod. LIBNET_PR2 0 - 1 LIBNET_PR8 0 - 255 LIBNET_PR16 0 - 32767 LIBNET_PRu16 0 - 65535 LIBNET_PR32 0 - 2147483647 LIBNET_PRu32 0 - 4294967295
+Generates an unsigned psuedo-random value within the range specified by mod. LIBNET_PR2 0 \- 1 LIBNET_PR8 0 \- 255 LIBNET_PR16 0 \- 32767 LIBNET_PRu16 0 \- 65535 LIBNET_PR32 0 \- 2147483647 LIBNET_PRu32 0 \- 4294967295
.PP
\fBParameters:\fP
.RS 4
@@ -2796,7 +2797,7 @@ Generates an unsigned psuedo-random value within the range specified by mod. LIB
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -2860,7 +2861,7 @@ the file number of the file descriptor used for packet injection
.PP
\fBReturns:\fP
.RS 4
-protocol tag value on success, -1 on error
+protocol tag value on success, \-1 on error
.RE
.PP
@@ -2964,7 +2965,7 @@ Takes a dotted decimal string or a canonical DNS name and returns a network byte
.PP
\fBReturns:\fP
.RS 4
-network byte ordered IPv4 address or -1 (2^32 - 1) on error
+network byte ordered IPv4 address or \-1 (2^32 \- 1) on error
.RE
.PP
@@ -2998,7 +2999,7 @@ Runs through the port list and prints the contents of the port list chain list t
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -3028,13 +3029,13 @@ Frees all memory associated with port list chain.
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
.SS "int libnet_plist_chain_new (libnet_t * l, libnet_plist_t ** plist, char * token_list)"
.PP
-Creates a new port list. Port list chains are useful for TCP and UDP-based applications that need to send packets to a range of ports (contiguous or otherwise). The port list chain, which token_list points to, should contain a series of int8_tacters from the following list: '0123456789,-' of the general format 'x - y, z', where 'xyz' are port numbers between 0 and 65,535. plist points to the front of the port list chain list for use in further libnet_plist_chain() functions. Upon success, the function returns 1. Upon failure, the function returns -1 and \fBlibnet_geterror()\fP can tell you why.
+Creates a new port list. Port list chains are useful for TCP and UDP-based applications that need to send packets to a range of ports (contiguous or otherwise). The port list chain, which token_list points to, should contain a series of int8_tacters from the following list: '0123456789,\-' of the general format 'x \- y, z', where 'xyz' are port numbers between 0 and 65,535. plist points to the front of the port list chain list for use in further libnet_plist_chain() functions. Upon success, the function returns 1. Upon failure, the function returns \-1 and \fBlibnet_geterror()\fP can tell you why.
.PP
\fBParameters:\fP
.RS 4
@@ -3047,13 +3048,13 @@ Creates a new port list. Port list chains are useful for TCP and UDP-based appli
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
.SS "int libnet_plist_chain_next_pair (libnet_plist_t * plist, u_int16_t * bport, u_int16_t * eport)"
.PP
-Returns the next port list chain pair from the port list chain plist. bport and eport contain the starting port number and ending port number, respectively. Upon success, the function returns 1 and fills in the port variables; however, if the list is empty, the function returns 0 and sets both port variables to 0. Upon failure, the function returns -1.
+Returns the next port list chain pair from the port list chain plist. bport and eport contain the starting port number and ending port number, respectively. Upon success, the function returns 1 and fills in the port variables; however, if the list is empty, the function returns 0 and sets both port variables to 0. Upon failure, the function returns \-1.
.PP
\fBParameters:\fP
.RS 4
@@ -3066,7 +3067,7 @@ Returns the next port list chain pair from the port list chain plist. bport and
.PP
\fBReturns:\fP
.RS 4
-1 on success, 0 if empty, -1 on failure
+1 on success, 0 if empty, \-1 on failure
.RE
.PP
@@ -3081,7 +3082,7 @@ Seeds the psuedo-random number generator.
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -3112,7 +3113,7 @@ If a given protocol header is built with the checksum field set to '0', by defau
.PP
\fBReturns:\fP
.RS 4
-1 on success, -1 on failure
+1 on success, \-1 on failure
.RE
.PP
@@ -3127,7 +3128,7 @@ Writes a prebuilt packet to the network. The function assumes that l was previou
.PP
\fBReturns:\fP
.RS 4
-the number of bytes written, -1 on error
+the number of bytes written, \-1 on error
.RE
.PP