aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkaotisk <kaotisk@arching-kaos.com>2021-09-24 11:44:18 +0300
committerkaotisk <kaotisk@arching-kaos.com>2021-09-24 11:44:18 +0300
commit8db1a71fe8f97f3e9a5153a075f9640d04f62cec (patch)
treeaf2656c9fc29a0a8b7f56db565e6a3c6dcac4815
parentb4662a1107880f4038be32fe83484f614afb68c0 (diff)
download01-NEWS-8db1a71fe8f97f3e9a5153a075f9640d04f62cec.tar.gz
01-NEWS-8db1a71fe8f97f3e9a5153a075f9640d04f62cec.tar.bz2
01-NEWS-8db1a71fe8f97f3e9a5153a075f9640d04f62cec.zip
Migration to Fedora Linux - update a bit
-rw-r--r--20210923_21062311
1 files changed, 11 insertions, 0 deletions
diff --git a/20210923_210623 b/20210923_210623
index 74a602b..8a2ae32 100644
--- a/20210923_210623
+++ b/20210923_210623
@@ -35,3 +35,14 @@ $ peerStats | grep EST | awk '{print $1}' | sed -e 's/\:[0-9]*$//g'
This is outputing the thing. The current connected peers. We will just ask them from a port that we are listening to as a tool that could be running along, or it could be another command whatever, no idea... actually this is started to interconnect other instances and exchange of credentials to put autopeering on ArchingKaos network backend.
In the end, I think it more like, insert some more code on CJDNS to do this, or use a library that already exists. I know it's not NEWS is my latest thoughs. Maybe not even well written for the moment.
+
+Clean up:
+
+1) We have stored a CJDNS peer for IPv4 connection:
+"192.168.20.5:43231"{...}
+
+But 192.168.20.5 is not appearing as ESTABLISHED connection. We try the same credentials over to 192.168.20.1-254 range. Succeed or fail, we stop until the next scan.
+
+2) We have incoming connection to "alice" and "bob".
+
+We convert their publickeys to IPs, search for them, and if we have new IPv4/6 we are available from, we announce it to them. This means that they should already been connected through another node into the network.