How to set portforwarding

Hello. I am a SPO and I need to add one relay node using a private PC.
I am confusing to set portforwarding…

  1. The port of Relay node automatically set in 6000 when the node is installed in Ubuntu?
  2. If public IP is XX.XX.XX.XX, XX.XX.XX.XX:6000 (external port)
    It means that XX.XX.XX.XX:6000 should be written in BP node mainnet-topology.json?
  3. DDNS is not needed???

Hi,

  • The port of Relay node automatically set in 6000 when the node is installed in Ubuntu?

6000 is the default port but it can be changed inside env file (cntools users) or inside start script (coincashew users)

  • If public IP is XX.XX.XX.XX, XX.XX.XX.XX:6000 (external port)
    It means that XX.XX.XX.XX:6000 should be written in BP node mainnet-topology.json?

Exactly, inside topology file u will set the cnode port of the Relay

  • DDNS is not needed???

Not necessarly

PS: being a Relay node inside PF configuration u will need to allow all IPs (0.0.0.0/0 port 6000 to 192.168.45.243 port 6000) otherwise other nodes can’t connect to Relay (only ur BP)

Cheers,

Always thanks. Alex.
PS: being a Relay node inside PF configuration u will need to allow all IPs (0.0.0.0/0 port 6000 to 192.168.45.243 port 6000) - How to set it? :slight_smile:

U have a picture above with PF configuration… instead the BP IP set 0.0.0.0/0 which should means from any

Maybe allowing all IPs 0.0.0.0/0 indicates

Not here… on PF configuration section… check ur router modem PF on google/youtube and u will find how to…

Hello. My BP does not operates well after trying leadership-schedule…
Due to low Swap memory, learship-schedule is not matched in my system.
BP was restarted but in gLiveView.sh BP does not operate even though 11 min`s uptime.
It is the first time to wait it.
BP is used to operate within 5 min after restarting.

Try this

sometimes, when you stop/start/restart the node often you will hit this issue and you will need to perform the steps

  • stop the node
sudo systemctl stop cnode
  • rename ledger, immutable and volatile folders
cd $CNODE_HOME/db
ls -l
mv immutable imm
mv ledger led
mv volatile vol
ls -l
  • start/stop the node
sudo systemctl start cnode
stop the node after 10 sec
sudo systemctl stop cnode
  • you should also see now the new folders ledger, immutable and volatile
    delete the new folders created (not the old one renamed)
ls -l
rm -R ledger
rm -R immutable
rm -R volatile
ls -l
  • rename back the original folders
mv imm immutable
mv led ledger
mv vol volatile
ls -l
  • start the node and check glive (you should see now Mem RSS slowly increasing)
sudo systemctl start cnode
cd ..
cd scripts
./gLiveView.sh

Many thanks. it works well.
Thanks again…

1 Like

If u want to run the leaderslots try to increase the memory swap file

the total available MEM should be over 22G (physical + SWAP)

Hello. I tried to change a PC for one more relay node.
In gLiveView.sh of BP, the number of outgoing is less than incoming. in 1.
Many due to problem in setting portforwarding.
Unequality of the number of outgoing and incoming… Blocks are minted??

Yes, should not be a problem as long u see your relays as IN &. OUT peers

I had the same behavior but it is related to another service which run as systemd