A whole day without a message in this topic so things must be running well! Or we’ve had to at least pretend to do our day jobs for a bit!
I’d like to run my nodes at home in the --node-port mode and not using --home-network so that rather than adding to the load of relays I’m being a relay to others. I’m doing that and it seems to work: I’m getting PUTs, GETs and occasional nanos. I think the port forwarding is working fine on the nodes at home or surely I wouldn’t be getting these and would have whole load of errors. There doesn’t seem to be any difference in the number of peers or amount of shunning for them.
However, I don’t think I’m being a relay. I see only messages like this that have ‘relay client event’ in them:-
[2024-06-21T04:44:56.014547Z INFO sn_networking::event::swarm] relay client event event=OutboundCircuitEstablished { relay_peer_id: PeerId("12D3KooWKMxudHDuoNybcxFKfqe4vp6KYeScshYLxi93GEAtNeUo"), limit: None }
whereas on the AWS Instance I have running in --node-port mode I see messages like this with ‘relay server event’ in them :-
[2024-06-20T19:53:14.453319Z INFO sn_networking::event::swarm] relay server event event=CircuitReqAccepted { src_peer_id: PeerId("12D3KooWGxUfJadxJaSczKEayjYHaEQAJf4SZ48TrAHT6eY5uDW7"), dst_peer_id: PeerId("12D3KooWBqpik2LeBiCWrdJk9x2uoAmP5L7nsyVmzS5BPbjYpF8Q") }
[2024-06-20T19:53:14.643699Z INFO sn_networking::event::swarm] relay server event event=CircuitClosed { src_peer_id: PeerId("12D3KooWGxUfJadxJaSczKEayjYHaEQAJf4SZ48TrAHT6eY5uDW7"), dst_peer_id: PeerId("12D3KooWBqpik2LeBiCWrdJk9x2uoAmP5L7nsyVmzS5BPbjYpF8Q"), error: None }
along with the occasional one like this:-
[2024-06-20T19:54:59.504950Z INFO sn_networking::event::swarm] relay client event event=OutboundCircuitEstablished { relay_peer_id: PeerId("12D3KooWDvVM5USnyPYb4NR2ihfDcZeawk11NPsKeibXaz8YGYaq"), limit: None }
I see this message in the first log on both which suggests the nodes are setup to not be relay clients:-
[2024-06-12T22:38:28.628980Z INFO sn_networking::relay_manager] Setting relay client mode to false
whereas when I was running nodes from home with the --home-network option I got this in the first logs:-
[2024-06-17T23:07:04.822169Z INFO sn_networking::relay_manager] Setting relay client mode to true
So am I being a relay on the home nodes? Doesn’t look like it.
I don’t see any harm in running in this way so I’ll continue just in case but it would be good to know.
Interestingly, the network activity looks slightly different. This is the graph for the last 24 hours on the interface the RPi4 is on with 10 nodes:-
cutover from 10 nodes in --home-network mode to 10 nodes in --node-port mode was at 1200.
So the bandwidth used looks slightly higher on average but with fewer peaks which is actually better because it’s the peaks which are the problem for other things on the network. I should be able to push to more nodes. Unless it is something on the network that changed around then.
But it would be good to know if they are working as relays and if not fix it.
Or is it that my home nodes are eligible to be peers but there is some kind of selection process and they are just not very attractive but the AWS Instance is?