From 05b5066e80e8fb072859f8a3e7a0034b80c2ed25 Mon Sep 17 00:00:00 2001
From: Maxim Konovalov <maxim@FreeBSD.org>
Date: Sat, 9 Apr 2005 08:44:57 +0000
Subject: [PATCH] o Document net.inet.ip.maxfragpackets and maxfragsperpacket
 sysctls.

Reviewed by:	ru, silby
MFC after:	1 week
---
 share/man/man4/inet.4 | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/share/man/man4/inet.4 b/share/man/man4/inet.4
index 388af7c5848..92190d1d915 100644
--- a/share/man/man4/inet.4
+++ b/share/man/man4/inet.4
@@ -32,7 +32,7 @@
 .\"     From: @(#)inet.4	8.1 (Berkeley) 6/5/93
 .\" $FreeBSD$
 .\"
-.Dd October 23, 2004
+.Dd April 9, 2005
 .Dt INET 4
 .Os
 .Sh NAME
@@ -248,6 +248,15 @@ In the same time, on high-speed links, it can decrease the ID reuse
 cycle greatly.
 Default is 0 (sequential IP IDs).
 IPv6 flow IDs and fragment IDs are always random.
+.It Va ip.maxfragpackets
+Integer: maximum number of fragmented packets the host will accept and hold
+in the reassembling queue simultaneously.
+0 means that the host will not accept any fragmented packets.
+\-1 means that the host will accept as many fragmented packets as it receives.
+.It Va ip.maxfragsperpacket
+Integer: maximum number of fragments the host will accept and hold
+in the reassembling queue for a packet.
+0 means that the host will not accept any fragmented packets.
 .El
 .Sh SEE ALSO
 .Xr ioctl 2 ,