1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
|
Alaska Communications UDP Echo Tools
====================================
Copyright (C) 2020 Alaska Communications
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Contents
--------
* Overview
* Software Requirements
* Utilities
- akcom-udpecho
- akcom-udpechod
* Building Package
* Source Code
* Package Maintence Notes
Overview
==========
This package contains a UDP echo server and client. Both the client and the
server support RFC 862 (default) and support TR-143 UDPEchoPlus if passed the
`--echoplus` flag.
Software Requirements
=====================
* GNU GCC 4.2.1/Clang 13.0.0
* GNU Make 3.81
* GNU Libtool 2.4
* GNU Autoconf 2.69
* GNU Automake 1.16.5
* Git 1.7.2.3
Utilities
=========
akcom-udpecho
-------------
_akcom-udpecho_ is a shell utility for testing UDP echo servers. _akcom-udpecho_
supports for RFC 862 compliant servers and TR-143 UDPEchoPlus compliant
servers. If the UDP Echo variant is not specified, _akcom-udpecho_ will
attempt to determine the variant by examining the __TestRespSN__,
__TestRespRecvTimeStamp__, and __TestRespReplyTimeStamp__ fields of the
UDPEchoPlus packet for non-zero values.
_akcom-udpecho_ usage:
Usage: akcom-udpecho [options] host [port]
OPTIONS:
-4 connect via IPv4 only
-6 connect via IPv6 only
-c count stop after sending count packets
-d, --debug print packet debugging information
-e, --echoplus expect echo plus response (default: auto detect)
-h, --help print this help and exit
-i interval interval between packet (default: 1 sec)
-r, --rfc expect RFC compliant response (default: auto detect)
-q, --quiet, --silent do not print messages
-s packetsize size of data bytes to be sent. (default: 40 bytes)
-t sec response timeout (default: 5 sec)
-v, --verbose enable verbose output
-V, --version print version number and exit
Example usage (RFC 862 compliant):
$ akcom-udpecho -c 5 --rfc udpecho.example.com 30006
UDPECHO udpecho.example.com:30006 (209.112.131.108:30006): 40 bytes
udpecho_seq=1 time=17.3 ms
udpecho_seq=2 time=13.7 ms
udpecho_seq=3 time=19.0 ms
udpecho_seq=4 time=18.3 ms
udpecho_seq=5 time=12.6 ms
--- udpecho.example.com udpecho statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max = 12.6/16.1/19.0 ms
$
Example usage (TR-143 UDPEchoPlus compliant) using server with 100000 us
random delay:
$ akcom-udpecho -c 5 --echoplus udpecho.example.com 30006
UDPECHO udpecho.example.com:30006 (209.112.131.108:30006): 40 bytes
udpecho_seq=1 failures=0 time=158.0 ms delay=77.9 ms adj_time=80.1 ms
udpecho_seq=2 failures=0 time=109.1 ms delay=29.2 ms adj_time=79.9 ms
udpecho_seq=3 failures=0 time=136.1 ms delay=56.2 ms adj_time=79.9 ms
udpecho_seq=4 failures=0 time=83.1 ms delay=3.0 ms adj_time=80.0 ms
udpecho_seq=5 failures=0 time=133.2 ms delay=53.1 ms adj_time=80.0 ms
--- udpecho.example.com udpecho statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max = 83.1/123.9/158.0 ms
adjusted round-trip min/avg/max = 79.9/80.0/80.1 ms
$
akcom-udpechod
--------------
_akcom-udpechod_ is simple UDP echo server. The __drop__ and __delay__
features should not be used concurrently by multiple clients. Currently
_akcom-udpechod_ processes each packet sequentially which causes all packets
received before previous packets have been processed to be skewed when using
the __drop__ and __delay__ features.
_akcom-udpechod_ usage:
Usage: akcom-udpechod [options]
OPTIONS:
-d num, --drop=num set packet drop probability [0-99] (default: 0%)
-D usec, --delay=usec set echo delay range to microseconds (default: 0 us)
-e, --echoplus enable echo plus, not RFC compliant
-f str, --facility=str set syslog facility (default: daemon)
-g gid, --group=gid setgid to gid (default: none)
-h, --help print this help and exit
-l addr, --listen=addr bind to IP address (default: all)
-n, --foreground do not fork
-p port, --port=port list on port number (default: 30006)
-P file, --pidfile=file PID file (default: /var/run/akcom-udpechod.pid)
-r, --rfc RFC compliant echo protocol (default)
-u uid, --user=uid setuid to uid (default: none)
-v, --verbose enable verbose output
-V, --version print version number and exit
Example usage (RFC 862 compliant):
akcom-udpechod \
--port 30007 \
--pidfile /var/run/akcom-udpecho/akcom-udpecho.pid \
--user nobody \
--group nobody \
--delay=10000 \
--drop=10 \
--rfc
Example usage (TR-143 UDPEchoPlus compliant):
akcom-udpechod \
--port 30007 \
--pidfile /var/run/akcom-udpecho/akcom-udpecho.pid \
--echoplus \
--user nobody \
--group nobody \
--delay=10000 \
--drop=10 \
--echoplus
Building Package
================
To build the package using a source tarball, run the following:
tar -xvf akcom-udpecho-x.y.z.tar.xz
mkdir -p akcom-udpecho-x.y.z/build
cd akcom-udpecho-x.y.z/build
../configure
make
make install
For additional configuration options, run:
../configure --help
Source Code
===========
The source code for this project is maintained using git
(http://git-scm.com). The following contains information to checkout the
source code from the git repository.
Browse Source:
* https://github.com/alaskacommunications/akcom-udpecho/ (public repoisitory)
* https://scm.prv.acsalaska.net/pub/scm/ipeng/akcom-udpecho.git/ (internal repository)
Git URLs:
* https://github.com/alaskacommunications/akcom-udpecho.git (public repoisitory)
* https://scm.prv.acsalaska.net/pub/scm/ipeng/akcom-udpecho.git (internal repository)
* scm.prv.acsalaska.net:/pub/scm/ipeng/akcom-udpecho.git (internal repository)
Downloading Source:
$ git clone https://github.com/alaskacommunications/akcom-udpecho/
Preparing and compiling source using GNU autotools method:
$ cd akcom-udpecho/build
$ ../autogen.sh
$ ../configure
$ make && make install
Compiling source using basic method:
$ cd akcom-udpecho/src
$ make && make install
For more information on building and installing using configure, please
read the INSTALL file.
Git Branches:
* master - Current release of packages.
* next - changes staged for next release
* pu - proposed updates for next release
* xx/yy+ - branch for testing new changes before merging to 'pu' branch
Package Maintence Notes
=======================
This is a collection of notes for developers to use when maintaining this
package.
New Release Checklist:
- Switch to 'master' branch in Git repository.
- Update version in configure.ac.
- Update version in GNUmakefile.version.
- Update date and version in ChangeLog.
- Commit configure.ac and ChangeLog changes to repository.
- Create tag in git repository:
$ git tag -s v${MAJOR}.${MINOR}
- Push repository to publishing server:
$ git push --tags origin master:master next:next pu:pu
Creating Source Distribution Archives:
$ ./configure
$ make update
$ make distcheck
$ make dist-bzip2
$ make dist-xz
|