<synopsis>
serverinfo {
name = "<replaceable>text</replaceable>";
- use_ts6 = <replaceable>boolean</replaceable>;
sid = "<replaceable>text</replaceable>";
description = "<replaceable>text</replaceable>";
network_name = "<replaceable>text</replaceable>";
</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term>use_ts6</term>
- <listitem>
- <para>
- A boolean which defines whether or not you want to use the new TS6 protocol, which provides
- many improvements over the old protocol, TS5, which is used in Hyperion.
- </para>
- </listitem>
- </varlistentry>
<varlistentry>
<term>sid</term>
<listitem>
<para>
- A unique ID which describes the server. This is required regardless of whether you are using
- TS6 or not.
+ A unique ID which describes the server.
This consists of one digit and two characters which can be
digits or letters.
</para>
<varlistentry>
<term>user</term>
<listitem>
- <para>A hostmask (user@host) that the auth{} block is matched against. You can have multiple user entries.</para>
+ <para>
+ A hostmask (user@host) that the auth {} block applies to.
+ It is matched against the hostname and IP address (using ::
+ shortening for IPv6 and prepending a 0 if it starts with
+ a colon) and can also use CIDR masks.
+ You can have multiple user entries.
+ </para>
</listitem>
</varlistentry>
<varlistentry>
Furthermore, if a hostname is used, it must have an A or AAAA
record (no CNAME) and it must be the primary
hostname for inbound connections to work.
+ </para><para>
+ IPv6 addresses must be in :: shortened form; addresses which
+ then start with a colon must be prepended with a zero,
+ for example 0::1.
</para></note>
</listitem>
</varlistentry>