Update changelog and readme

This commit is contained in:
frekky 2015-11-11 20:25:48 +08:00
parent 4f470e4756
commit 35a0f8279d
2 changed files with 18 additions and 10 deletions

View File

@ -6,6 +6,11 @@ iodine - http://code.kryo.se/iodine
CHANGES: CHANGES:
master: master:
- Multiple fragments can be in transit at one time to improve
throughput on high-latency connections
Server can now store multiple pending queries per user.
- Added bidirectional compression flags
- Added statistics report every few seconds in iodine (-V)
- Mac OS X: Support native utun VPN devices. Patch by - Mac OS X: Support native utun VPN devices. Patch by
Peter Sagerson, ported from OpenVPN by Catalin Patulea. Peter Sagerson, ported from OpenVPN by Catalin Patulea.
- Fix compilation failure on kFreeBSD and Hurd, by Gregor Herrmann - Fix compilation failure on kFreeBSD and Hurd, by Gregor Herrmann

View File

@ -292,8 +292,12 @@ undefine it to save a few more kilobytes.
PERFORMANCE PERFORMANCE
----------- -----------
This section tabulates some performance measurements. To view properly, use **Please note:** The following performance is outdated and does not apply to
a fixed-width font like Courier. the current version of iodine. Since the protocol was updated to use a sliding
window for sending fragments, the throughput was greatly increased and should
be much higher even on high-latency connections.
This section tabulates some performance measurements.
Measurements were done in protocol 00000502 in lazy mode; upstream encoding Measurements were done in protocol 00000502 in lazy mode; upstream encoding
always Base128; `iodine -M255`; `iodined -m1130`. Network conditions were not always Base128; `iodine -M255`; `iodined -m1130`. Network conditions were not
@ -353,12 +357,11 @@ and mean deviation (indicating spread around the average), in milliseconds.
### Notes ### Notes
Performance is strongly coupled to low ping times, as iodine requires Multiple fragments in-flight like TCP is allowed in iodine, which does increase
confirmation for every data fragment before moving on to the next. Allowing performance, but it may overload some low-bandwidth intermediary DNS servers.
multiple fragments in-flight like TCP could possibly increase performance, Using carrier-grade DNS servers such as those provided by your ISP should be able
but it would likely cause serious overload for the intermediary DNS servers. to handle a high volume of DNS queries, and it is recommended to use as many DNS
The current protocol scales performance with DNS responsivity, since the nameservers as possible to balance the load.
DNS servers are on average handling at most one DNS request per client.
PORTABILITY PORTABILITY
@ -389,8 +392,8 @@ THANKS
AUTHORS & LICENSE AUTHORS & LICENSE
----------------- -----------------
Copyright (c) 2006-2014 Erik Ekman <yarrick@kryo.se>, 2015 Frekky, 2006-2009 Bjorn Copyright (c) 2006-2014 Erik Ekman <yarrick@kryo.se>, 2015 Frekk van Blagh,
Andersson <flex@kryo.se>. Also major contributions by Anne Bezemer. 2006-2009 Bjorn Andersson <flex@kryo.se>. Also major contributions by Anne Bezemer.
Permission to use, copy, modify, and/or distribute this software for any purpose Permission to use, copy, modify, and/or distribute this software for any purpose
with or without fee is hereby granted, provided that the above copyright notice with or without fee is hereby granted, provided that the above copyright notice