From f13dc8b7ff7f31b92dac04cd72b126f34f8f3d2d Mon Sep 17 00:00:00 2001
From: zzz <zzz@i2pmail.org>
Date: Sat, 21 Oct 2023 09:43:28 -0400
Subject: [PATCH] SAM: More ports documentation

---
 i2p2www/pages/site/docs/api/samv3.html | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html
index f33e7aa1..35b967df 100644
--- a/i2p2www/pages/site/docs/api/samv3.html
+++ b/i2p2www/pages/site/docs/api/samv3.html
@@ -586,6 +586,10 @@ Clients send to port 0 by default, which means "any port".
 </li><li>
 Clients send from port 0 by default, which means "unspecified".
 </li><li>
+Servers may have a service listening on port 0 and other services listening on higher ports.
+If so, the port 0 service is the default, and will be connected to if the incoming
+socket or datagram port does not match another service.
+</li><li>
 Most I2P destinations only have one service running on them, so you may use the defaults, and ignore I2CP port configuration.
 </li><li>
 SAM 3.2 or 3.3 is required to specify I2CP ports.