SUMMARY: simulate delayed signals

[Tobias Kaboth <tobias.kaboth@arcor.de>]

Hi,
sorry - i'm late with this summary.
Thanks to Denice, Quentina and Tom!

Tip 1:
For emulating slow/unreliable networks I have built Linux routers and
used the NISTNet kernel module (http://snad.ncsl.nist.gov/itg/nistnet/)
to inject delay, drop and dup packets, etc. It can create variable delay
(within parameters) which might be useful to you too.

(I don't try this one because i have no hardware for this test, but a nice 
feature!)

Tip 2:
The control program is called tc. It may be installed as /sbin/tc, 
depending on your distro. The following lines will limit traffic going 
from the machine they are run out the $DEV interface TO x.x.x.x to 56kbp

(This is a good idea - i have a bug in the syntax - but i find them - sure)

Tip 3:
you can find javascript examples at
http://www.csgnetwork.com/converters.html
for example:
http://www.csgnetwork.com/timeconverters.html

For my software problem i don't find any answer. I create an own algorithmus. 
It's very easy and if the network is fast enough it's ok (+/- 10%) for my 
tool. But long delays (more than some seconds) are very bad.

I know the total signaldelay. I devide this delay by two. I can't calculate 
the real delay of one way, so i have only this small correction.
Look to NTP - this protocol triggered the time very good for the OS but for an 
application with only one way (client - server - client) the idea is not good 
enough in worst case.
On the application layer ther's no chance for a better result.
I don't want program a HTML-based pingpong page to reduce the error :-)) 

The real hardware is the best one :-)
So i tested the program on our demosystem in addition with low and hard 
traffic on my 56k modem.

Thanks a lot and greetings,
Tobias
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers@linuxmanagers.org
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers