samv3 typos

ports additions
This commit is contained in:
zzz
2018-03-01 14:44:11 +00:00
parent 6080600997
commit 40f3a7a6ad
2 changed files with 11 additions and 8 deletions

View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %} {% extends "global/layout.html" %}
{% block title %}SAM V3{% endblock %} {% block title %}SAM V3{% endblock %}
{% block lastupdated %}April 2017{% endblock %} {% block lastupdated %}March 2018{% endblock %}
{% block accuratefor %}0.9.29{% endblock %} {% block accuratefor %}0.9.34{% endblock %}
{% block content %} {% block content %}
<p>Specified below is a simple client protocol for interacting with I2P. <p>Specified below is a simple client protocol for interacting with I2P.
</p> </p>
@@ -125,7 +125,7 @@ By default, the client&lt;--&gt;SAM bridge communication is unencrypted and unau
The SAM bridge may support SSL/TLS connections; The SAM bridge may support SSL/TLS connections;
configuration and implementation details are outside the scope of this specification. configuration and implementation details are outside the scope of this specification.
As of SAM 3.2, optional authentication user/password parameters are supported in the initial handshake As of SAM 3.2, optional authentication user/password parameters are supported in the initial handshake
and may be required by the bridge.. and may be required by the bridge.
</p><p> </p><p>
I2P communications can take three distinct forms: I2P communications can take three distinct forms:
@@ -358,7 +358,7 @@ $nickname is the choice of the client. No whitespace is allowed.
</p><p> </p><p>
Additional options given are passed to the I2P session Additional options given are passed to the I2P session
configuration if not interpreted by the SAM bridge (e.g. configuration if not interpreted by the SAM bridge (e.g.
outbound.length=0). These options <a href="#options">are documented below</a>.. outbound.length=0). These options <a href="#options">are documented below</a>.
</p><p> </p><p>
The SAM bridge itself should already be configured with what router The SAM bridge itself should already be configured with what router
@@ -843,7 +843,7 @@ CREATE command with PORT and HOST options:
</p><p> </p><p>
Additional options given are passed to the I2P session Additional options given are passed to the I2P session
configuration if not interpreted by the SAM bridge (e.g. configuration if not interpreted by the SAM bridge (e.g.
outbound.length=0). These options <a href="#options">are documented below</a>.. outbound.length=0). These options <a href="#options">are documented below</a>.
</p><p> </p><p>
Forwarded repliable datagrams are always prefixed with the destination. Forwarded repliable datagrams are always prefixed with the destination.

View File

@@ -1,6 +1,6 @@
{% extends "global/layout.html" %} {% extends "global/layout.html" %}
{% block title %}{% trans %}Ports Used by I2P{% endtrans %}{% endblock %} {% block title %}{% trans %}Ports Used by I2P{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}February 2018{% endtrans %}{% endblock %} {% block lastupdated %}{% trans %}March 2018{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.34{% endblock %} {% block accuratefor %}0.9.34{% endblock %}
{% block content %} {% block content %}
@@ -22,6 +22,7 @@ in the 766x range.
<table> <table>
<tr><th>Port</th><th>Usage</th></tr> <tr><th>Port</th><th>Usage</th></tr>
<tr><td>123</td><td>SNTP</td></tr> <tr><td>123</td><td>SNTP</td></tr>
<tr><td>1488</td><td>XD client web UI</td>
<tr><td>1900</td><td>UPnP SSDP UDP multicast listener</td> <tr><td>1900</td><td>UPnP SSDP UDP multicast listener</td>
<tr><td>2827</td><td>BOB Bridge</td></tr> <tr><td>2827</td><td>BOB Bridge</td></tr>
<tr><td>3456</td><td>Tahoe-LAFS-Controller Plugin</td></tr> <tr><td>3456</td><td>Tahoe-LAFS-Controller Plugin</td></tr>
@@ -53,9 +54,11 @@ in the 766x range.
<tr><td>7667</td><td>Router Console SSL</td></tr> <tr><td>7667</td><td>Router Console SSL</td></tr>
<tr><td>7668</td><td>Eepsite SSL</td></tr> <tr><td>7668</td><td>Eepsite SSL</td></tr>
<tr><td></td><td><i>{% trans %}recommended spot for new plugins/applications{% endtrans %}</i></td></tr> <tr><td></td><td><i>{% trans %}recommended spot for new plugins/applications{% endtrans %}</i></td></tr>
<tr><td>8002</td><td>I2PSnark (standalone install only)</td></tr>
<tr><td>8003</td><td>I2PSnark SSL (standalone install only)</td></tr>
<tr><td>8118</td><td>Privoxy (reserve)</td></tr> <tr><td>8118</td><td>Privoxy (reserve)</td></tr>
<tr><td>8123</td><td>Tor Polipo (reserve)</td></tr> <tr><td>8123</td><td>Tor Polipo (reserve)</td></tr>
<tr><td>8887</td><td>Old default network port</td></tr> <tr><td>8887</td><td>Old default router network port</td></tr>
<tr><td>8888</td><td>Freenet (reserve)</td></tr> <tr><td>8888</td><td>Freenet (reserve)</td></tr>
<tr><td>8997</td><td>Monotone Proxy (alt)</td></tr> <tr><td>8997</td><td>Monotone Proxy (alt)</td></tr>
<tr><td>8998</td><td>Monotone Proxy</td></tr> <tr><td>8998</td><td>Monotone Proxy</td></tr>
@@ -64,7 +67,7 @@ in the 766x range.
<tr><td>9051-9053</td><td>SOCKS Proxy (typ)</td></tr> <tr><td>9051-9053</td><td>SOCKS Proxy (typ)</td></tr>
<tr><td>9150</td><td>Tor Browser SOCKS Proxy (reserve)</td></tr> <tr><td>9150</td><td>Tor Browser SOCKS Proxy (reserve)</td></tr>
<tr><td>9152-9153</td><td>Tor Messenger Socks and Control ports (reserve)</td></tr> <tr><td>9152-9153</td><td>Tor Messenger Socks and Control ports (reserve)</td></tr>
<tr><td>9111-30777</td><td>Network (random)</td></tr> <tr><td>9111-30777</td><td>Router network port (random, selected at install time)</td></tr>
<tr><td>11371</td><td>SKS/GPG Key Server (reserve)</td></tr> <tr><td>11371</td><td>SKS/GPG Key Server (reserve)</td></tr>
<tr><td>31000</td><td>Wrapper</td></tr> <tr><td>31000</td><td>Wrapper</td></tr>
<tr><td>31001-31999</td><td>Wrapper (alt - retries going up)</td> <tr><td>31001-31999</td><td>Wrapper (alt - retries going up)</td>