From c00ff34e1876c6ab990ca72fc156f453a5f20051 Mon Sep 17 00:00:00 2001
From: do6uk <33249819+do6uk@users.noreply.github.com>
Date: Sat, 20 Dec 2025 15:56:27 +0100
Subject: [PATCH] Update README.md for v1.1

---
 README.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.md b/README.md
index e50f809..fae08ad 100644
--- a/README.md
+++ b/README.md
@@ -25,8 +25,21 @@ python3 meshcore_multitcp.py -d Device-IP:PORT -s Server-IP:PORT [-q|-v]
 
 -v maximizes CLI-output
 
+-f sets secondary IP & port for listening to clients using message-storage (see S&F)
+
+-sql activates message-storage for clients which connect at second ip/port given by -f (see S&F)
+
+
 After meshcore_multitcp is running you can connect your clients to IP/port set with -s
 
+## S&F - store & forward messages
+
+Using option -sql meshcore-multitcp will store all incomming private & channel messages in local sqlite3-database. 
+If client connects at secondary ip/port given by -f meshcore-multitcp will forward all stored messages since last message exchange.
+Dumping large number of messages can cause hung up clients and messages could be lost.
+
+WARNING: Actually theres no database-clean-up - so if you connect a new client first time, meshcore-multitcp will try to forward all known messages.
+
 ## what you should know before you start
 
 This software comes as it is without any guarantee to work stable and secure.