diff options
Diffstat (limited to 'jni/iodine/doc')
-rw-r--r-- | jni/iodine/doc/iodine-server.service | 11 | ||||
-rw-r--r-- | jni/iodine/doc/iodine-server.socket | 8 | ||||
-rw-r--r-- | jni/iodine/doc/proto_00000502.txt | 7 |
3 files changed, 23 insertions, 3 deletions
diff --git a/jni/iodine/doc/iodine-server.service b/jni/iodine/doc/iodine-server.service new file mode 100644 index 0000000..64d2ecc --- /dev/null +++ b/jni/iodine/doc/iodine-server.service @@ -0,0 +1,11 @@ +[Unit] +Description=Iodine Server +After=local-fs.target network.target + +[Service] +EnvironmentFile=-/etc/sysconfig/iodine-server +ExecStart=/usr/local/bin/iodined -i 30 -f $OPTIONS +StandardOutput=syslog + +[Install] +WantedBy=multi-user.target diff --git a/jni/iodine/doc/iodine-server.socket b/jni/iodine/doc/iodine-server.socket new file mode 100644 index 0000000..d6c57b8 --- /dev/null +++ b/jni/iodine/doc/iodine-server.socket @@ -0,0 +1,8 @@ +[Unit] +Description=Iodine socket + +[Socket] +ListenDatagram=53 + +[Install] +WantedBy=sockets.target diff --git a/jni/iodine/doc/proto_00000502.txt b/jni/iodine/doc/proto_00000502.txt index 46cf2de..831824d 100644 --- a/jni/iodine/doc/proto_00000502.txt +++ b/jni/iodine/doc/proto_00000502.txt @@ -122,7 +122,8 @@ Server sends: s or S: Downstream encoding Base64, for TXT/CNAME/A/MX u or U: Downstream encoding Base64u, for TXT/CNAME/A/MX v or V: Downstream encoding Base128, for TXT/CNAME/A/MX - r or R: Downstream encoding Raw, for TXT/NULL (default for NULL) + r or R: Downstream encoding Raw, for PRIVATE/TXT/NULL (default for + PRIVATE and NULL) If codec unsupported for request type, server will use Base32; note that server will answer any mix of request types that a client sends. Server may disregard this option; client must always use the downstream @@ -188,8 +189,8 @@ encoded with the chosen upstream codec. Downstream data starts with 2 byte header. Then payload data, which may be compressed. -In NULL responses, downstream data is always raw. In all other response types, -downstream data is encoded (see Options above). +In NULL and PRIVATE responses, downstream data is always raw. In all other +response types, downstream data is encoded (see Options above). Encoding type is indicated by 1 prefix char: TXT: End result is always DNS-chopped (series of len-prefixed strings |