diff --git a/docs/Reticulum Manual.pdf b/docs/Reticulum Manual.pdf
index 3eb489e..7894a69 100644
Binary files a/docs/Reticulum Manual.pdf and b/docs/Reticulum Manual.pdf differ
diff --git a/docs/manual/_sources/interfaces.rst.txt b/docs/manual/_sources/interfaces.rst.txt
index 60ee150..c4d73de 100644
--- a/docs/manual/_sources/interfaces.rst.txt
+++ b/docs/manual/_sources/interfaces.rst.txt
@@ -110,6 +110,7 @@ an I2P interface to reticulum:
   [[I2P]]
     type = I2PInterface
     interface_enabled = yes
+    connectable = yes
 
 On the first start, Reticulum will generate a new I2P address for the
 interface and start listening for inbound traffic on it. This can take
@@ -126,6 +127,7 @@ list of I2P base32 addresses to the ``peers`` option of the interface:
   [[I2P]]
     type = I2PInterface
     interface_enabled = yes
+    connectable = yes
     peers = 5urvjicpzi7q3ybztsef4i5ow2aq4soktfj7zedz53s47r54jnqq.b32.i2p
 
 It can take anywhere from a few seconds to a few minutes to establish
diff --git a/docs/manual/interfaces.html b/docs/manual/interfaces.html
index eb7acce..e1319d8 100644
--- a/docs/manual/interfaces.html
+++ b/docs/manual/interfaces.html
@@ -128,6 +128,7 @@ an I2P interface to reticulum:</p>
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[[</span><span class="n">I2P</span><span class="p">]]</span>
   <span class="nb">type</span> <span class="o">=</span> <span class="n">I2PInterface</span>
   <span class="n">interface_enabled</span> <span class="o">=</span> <span class="n">yes</span>
+  <span class="n">connectable</span> <span class="o">=</span> <span class="n">yes</span>
 </pre></div>
 </div>
 <p>On the first start, Reticulum will generate a new I2P address for the
@@ -141,6 +142,7 @@ list of I2P base32 addresses to the <code class="docutils literal notranslate"><
 <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="p">[[</span><span class="n">I2P</span><span class="p">]]</span>
   <span class="nb">type</span> <span class="o">=</span> <span class="n">I2PInterface</span>
   <span class="n">interface_enabled</span> <span class="o">=</span> <span class="n">yes</span>
+  <span class="n">connectable</span> <span class="o">=</span> <span class="n">yes</span>
   <span class="n">peers</span> <span class="o">=</span> <span class="mi">5</span><span class="n">urvjicpzi7q3ybztsef4i5ow2aq4soktfj7zedz53s47r54jnqq</span><span class="o">.</span><span class="n">b32</span><span class="o">.</span><span class="n">i2p</span>
 </pre></div>
 </div>
diff --git a/docs/source/interfaces.rst b/docs/source/interfaces.rst
index 60ee150..c4d73de 100644
--- a/docs/source/interfaces.rst
+++ b/docs/source/interfaces.rst
@@ -110,6 +110,7 @@ an I2P interface to reticulum:
   [[I2P]]
     type = I2PInterface
     interface_enabled = yes
+    connectable = yes
 
 On the first start, Reticulum will generate a new I2P address for the
 interface and start listening for inbound traffic on it. This can take
@@ -126,6 +127,7 @@ list of I2P base32 addresses to the ``peers`` option of the interface:
   [[I2P]]
     type = I2PInterface
     interface_enabled = yes
+    connectable = yes
     peers = 5urvjicpzi7q3ybztsef4i5ow2aq4soktfj7zedz53s47r54jnqq.b32.i2p
 
 It can take anywhere from a few seconds to a few minutes to establish