mirror of https://framagit.org/bortzmeyer/echoping
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 lines
1.4 KiB
Plaintext
53 lines
1.4 KiB
Plaintext
Actual bugs are registered at SourceForge:
|
|
|
|
http://sourceforge.net/bugs/?group_id=4581
|
|
|
|
To see a given bug (say #132001):
|
|
|
|
http://sourceforge.net/bugs/?group_id=4581&func=detailbug&bug_id=132001
|
|
|
|
Wishes:
|
|
|
|
Display other calculations such as standard deviation.
|
|
|
|
Check the TCP timeout with T/TCP. Difficult to test, few T/TCP
|
|
machines exist.
|
|
|
|
TCP timeout with long packets seem to confuse Cisco routers. Does
|
|
someone can reproduce it and perform tests? It seems to work now.
|
|
|
|
Do not display the end-of-line after the HTTP reply, for instance when
|
|
a page is moved.
|
|
|
|
UDP isn't really useable with large packets because of sockets
|
|
limitations and the lack of workaround code.
|
|
|
|
If a Web page is empty, echoping
|
|
will display meaningless messages.
|
|
|
|
Timeouts on T/TCP connections are a bit experimental.
|
|
|
|
Since echoping writes everything to the server, then begins to read
|
|
the reply, some echo servers will timeout if you send very long
|
|
messages, because they expect you to start to read right now.
|
|
|
|
gcc's warnings:
|
|
|
|
1) Free/NetBSD
|
|
|
|
gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -Wall -c echoping.c
|
|
echoping.c: In function `main':
|
|
echoping.c:540: warning: passing arg 5 of `sendto' from incompatible pointer type
|
|
|
|
if (icp)
|
|
{
|
|
if (sendto (sockfd, sendline, length, 0,
|
|
&serv_addr, sizeof (serv_addr)) != length)
|
|
err_sys ("sendto error on socket");
|
|
}
|
|
|
|
|
|
|
|
$Id$
|
|
|