IPv4-only networks via IPv6-only network
Guus Sliepen
guus at sliepen.eu.org
Wed Dec 3 16:09:29 CET 2003
On Wed, Dec 03, 2003 at 07:43:12PM +0900, Ichiro Okajima wrote:
> But, I run into another problem. The round trip time of tunneled IPv4
> packets between two tincnized Redhat9 PCs fluctuates on the order of
> 0.532 to 10.554 ms, although that of IPv6 packets between them are
> very stable. Because I am planning to use a VoIP application between
> the two IPv4 network, stable RTTs of IPv4 packets are necessary.
>
> Do you have any idea to improve the RTT?
Since tinc is a normal user-space program, it is subjected to the task
scheduler, which on i386 architectures normally switches tasks every 10
ms. So if there's another non-idle program running on those PCs, tinc
might not respond as quickly as when it's the only process running. You
can change this behaviour by giving it a higher priority with nice, or
you can let tinc run in realtime (use the chrt command from the
schedutils package for example).
> --- 192.168.20.2 ping statistics ---
> 100 packets transmitted, 100 received, 0% loss, time 99118ms
> rtt min/avg/max/mdev = 0.532/3.112/10.554/3.093 ms
On the other hand, it's only a 3 ms standard deviation, and a worst case
RTT of 10 ms. Doesn't seem that bad to me, even for VoIP!
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20031203/927e4cfa/attachment.pgp
More information about the Tinc
mailing list