bin/82625: [PATCH] Enhancement to ping to ping through

Chris Hellberg chellberg at juniper.net
Fri Jun 24 23:00:29 GMT 2005


>Number:         82625
>Category:       bin
>Synopsis:       [PATCH] Enhancement to ping to ping through
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 24 23:00:26 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Chris Hellberg <chellberg at juniper.net>
>Release:        FreeBSD 5.3-STABLE i386
>Organization:
Juniper Networks
>Environment:
System: FreeBSD  5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov
5 04:19:18 UTC 2004   chellberg at localhost:/usr/obj/usr/src/sys/GENERIC  i386


	
>Description:
	A useful function to test MTU issues and traffic
policing functions in networks is to gradually increment
packet sizes in pings in a sweeping fashion.
	
>How-To-Repeat:
	
>Fix:

The diffs implment the changes needed to ping.c and updates
the ping manpage. To get the ping sweep working, you need to
specify pingsweepmax as a minimum. This is the maximum data
size that will be sent.

If pingsweepmin is set, the data size will start from the
specified value. The default data size is 0.

If pingsweepincr is set, after each _count_ number of packets
has been sent, the data size is increased by the current
data size + pingsweepincr. This cycle repeated until the
current data size is equal or less to pingsweepmax. If 
pingsweepincr doesn't divide evenly in to pingsweepmax, the
sweep will stop before it would exceed pingsweepmax.

If "-s count" is included, each sweep of a particular data size
will consist of "count" bytes.

>Release-Note:
>Audit-Trail:
>Unformatted:
 a range of data sizes


More information about the freebsd-bugs mailing list