Bash scripts for managing safe nodes on Linux

I had the wrong version of the proto files. Everything work now, such a game changer.

In addition to installing grpcurl, the proto files below are needed to make grpcurl happy when you make a call.

From maidsafe/safe_network Main branch:


The node needs to be started with this added: --rpc<some_port>

The call will then become:
grpcurl -plaintext -proto safenode.proto<some_port> safenode_proto.SafeNode/KBuckets

You can use: NodeInfo, NetworkInfo, NodeEvents, RecordAddresses, KBuckets, Stop, Restart, Update, UpdateZLogLevel. as described in the safenode_proto file.


I just set the rpc port in safenode-manager when starting. Does the node need the loopback address as well?

Good to see it working.

Can you link the actual link to the github page with the current versions of the files for others.

Done! Plus more: snnm v0.2.0, a.k.a the “neo edition” in your honor, is in my repo now.
As usual it is experimental, use-at-your-own-risk, and takes some effort to get setup but it works great for me.

It’s able to:
-e: flag to enable rpc on nodes when starting, restarting, or exchanging node processes
-L: the rpc enabled but slower cousin of -l to list all nodes incl. actual peer count and uptime

The rpc port number is derived from the node port: node_port - NODE_BASE_PORT + RPC_BASE_PORT.

sample output:
| port 5xxxx | pid 271192 | peer-id 12D3xxxx | v."0.108.2", 29 peers, uptime "43483" s

Installation of grpcurl and friends (for installation into your $HOME directory):

cd $HOME
sudo rpm -i grpcurl_1.9.1_linux_386.rpm
sudo dnf -y install grpcurl jq
wget -O safenode.proto
wget -O req_resp_types.proto

We can clean up the snnm installation by moving the files into the same directory as used by the other safeup applications.

After moving snnm, and *.proto to $HOME/.local/bin/ I just type snnm without the preceding ./ This only works for version 0.2.9 and above.

  • Installation of snnm 0.2.9 and above into the $HOME/.local/bin/:
    Rocky Linux 9.4, bash
cd $HOME/.local/bin/
wget -O snnm
sudo chmod +x snnm
wget -O safenode.proto
wget -O req_resp_types.proto

cd $HOME
sudo rpm -i grpcurl_1.9.1_linux_386.rpm
sudo dnf -y install grpcurl jq

snnm -v

(edit: correction of wget URL of proto files.)

1 Like

Nah im convinced something is backwards here. How am I suppose to know an incoming port from another user when everyone is setting their own range? I only know what im setting. Not what incoming connections will be? What am I missing lol.

snnm version 0.2.9 has this kind of output. All you need to know. connected peers real-time, number of records, and forwarded earnings. Plus totals for each server.

snnm -a 53344 -b 53349 -L
| port  53344 | pid   312230 | peer-id 12D3KooW..1 | v."0.108.2"  |     33 peers |     99 records |    "18728"s uptime | 
| port  53345 | pid   315238 | peer-id 12D3KooW..2 | v."0.108.2"  |    258 peers |    100 records |    "18589"s uptime | 
| port  53346 | pid   299563 | peer-id 12D3KooW..3 | v."0.108.2"  |    247 peers |    131 records |    "19282"s uptime | fwd_nanos: 20
| port  53347 | pid   317531 | peer-id 12D3KooW..4 | v."0.108.2"  |     28 peers |    133 records |    "18477"s uptime | fwd_nanos: 10
| port  53348 | pid   307574 | peer-id 12D3KooW..5 | v."0.108.2"  |     58 peers |    106 records |    "18891"s uptime | fwd_nanos: 10
| port  53349 | pid   301291 | peer-id 12D3KooW..6 | v."0.108.2"  |     83 peers |    116 records |    "19200"s uptime | fwd_nanos: 10
Total connected peers (for nodes with rpc port only): 707
Total records (for nodes with rpc port only): 685
Total forwarded nanos: 50
snnm execution is done. In some cases you need to [Ctrl]+[c] to get back to your command prompt.

The node sets the port it will be listening on. Either a random one or the one you specify.

The process is

  • your node communicates with another node (or relay if home-network) and this causes
    • your node advertising to the router what port it is listening for a response (the listening port)
  • the router translates the addresses and sends the packet to the receiver
  • the receiver knows where to reply to from the packet’s header
  • the receiver builds response and sends back to the node using the info gained from the request packet
  • your router receives this packet and knows from the sender info that the packet is to be sent to your node on its listening port
    • the router keeps a table that allows it to match up sender/receiver addr&port
  • your node listening on that listening port is then able to receive the packet.

Now the listening port is either set to the port you specify or will pick a random port number to set it to.

So its not just you who knows what port number you are setting it to, but your node and your router are very talkative about the incoming ports


Ok I think im well confused. So ive reset everything. safenetnode-manager reset then I recreated my node list with safenode-manager add --owner .user --home-network --count 20 --node-port 21000-21019 --rpc-port 31000-31019 --peer /ip4/ - FYI ive tried this with and without the --home-network which should not be needed.

my current state of the ufw status is

21000:21150/udp            ALLOW       Anywhere                  
22/tcp (v6)                ALLOW       Anywhere (v6)             
21000:21150/udp (v6)       ALLOW       Anywhere (v6) 

my current state of the user ports and listeners is something like this;

Netid                   State                    Recv-Q                   Send-Q                                         Local Address:Port                                      Peer Address:Port                  Process
udp                     UNCONN                   0                        0                                                                          *                                               
udp                     UNCONN                   0                        0                                                                          *                                               
udp                     UNCONN                   0                        0                                                                          *                                               
udp                     UNCONN                   0                        0                                                                          *                                               
udp                     UNCONN                   0                        0                                                                       *                                               
udp                     UNCONN                   0                        0                                                                   *                                               
tcp                     LISTEN                   0                        4096                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                           *                                               
tcp                     LISTEN                   0                        4096                                                                    *                                               
tcp                     LISTEN                   0                        128                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                      *                                               
tcp                     LISTEN                   0                        128                                                                      *       

My router is setup exactly the same way to access other services… unsure best way to test each layer, but now im getting 0 connections on, anything at any point.

the fixes are supposed to remove the need for the peer option and that peer probably doesn’t exist anymore anyhow

And i hope that .user is changed to your discordID and not the user option

home-network doesn’t need the ports specified as they really are not listening anyhow. The connection is done via normal communications where the node communicates with relay first opening the connection pathway.

Only need the ports when not specifying home-network and port forwarding

The peer option is prob the biggest problem here, with the update those old peers will be gone

1 Like

Good lord split me. I had a inclination it was the peer not existing lol. Yeah I figured the other stuff was the case. And yes, That is the case. Thanks very much il wait for this update then. Excellent.

1 Like

update is here. Just don’t use the --peer

The launcher and manager will download the updated node s/w automatically