Geth Node sync'ing even with closed ports

Before filing a new topic, please provide the following information.

Core DAppNode Packages versions

  • bind.dnp.dappnode.eth: 0.2.6
  • core.dnp.dappnode.eth: 0.2.47
  • dappmanager.dnp.dappnode.eth: 0.2.42, branch: v0.2.43, commit: ec541936
  • https.dnp.dappnode.eth: 0.1.1
  • ipfs.dnp.dappnode.eth: 0.2.14
  • vpn.dnp.dappnode.eth: 0.2.8, commit: f9a8743e
  • wifi.dnp.dappnode.eth: 0.2.7

System info

  • dockerComposeVersion: 1.25.5
  • dockerServerVersion: 20.10.2
  • dockerCliVersion: 20.10.2
  • os: ubuntu
  • versionCodename: focal
  • architecture: amd64
  • kernel: 5.11.0-25-generic
  • Disk usage: 87%

My Geth node is sync’ing just fine regardless of closed ports: 49155, 49154, 49156.

Questions:

  1. How is it possible for the Geth node to be in sync with closed ports?

  2. If it’s sync’ing just fine, do I still need to open those ports on my router? And why?

  3. Can I assume that the list of ports in [Dappnode | Support | Ports] is a full list of ports that must be opened for the correct functioning of dappnode and all it’s packages?

Please note: I was prevented from uploading a second picture since I am a new user. But I can send you a screenshot of the Dashboard which shows that the Geth node is fully sync’ed regardless of closed ports.

Hi there!

  1. Ports are not mandatory but make things more efficient in blockchain.
  2. Your node will be okey, just need them for performance but is not that critical. Ports are mandatory only for a few core services such as connect to your dappnode through VPN.
  3. You are right, but as I said not all of them are mandatory. Maybe this could be described in a new column saying “mandatory”

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.