84 Million podcast with Loshan - Full Nodes for MWEB incoming port 9333 VS. Leechers / bandwidth consideration

I listened to the Podcast with Loshan @losh11 (the cute little boy with the big eyes) and enjoyed it very much
https://www.youtube.com/watch?v=GxDefPtLj80

In the podcast Loshan calls us LTC friends to run a full node of Litecoin core - for Chickun :chicken: to arise - especially after the recent update of Litecoin to support light MWEB clients that will rely on people running public full nodes.
And he especially asked to open up incoming port 9333, because otherwise the node seems to be “leech-only”, providing transaction verification only for own transactions.

Question:
1.

  • what Internet bandwidth (uplink/downlink) will be needed for this public mode with open port 9333?
    Because at the moment, I only have a tiny internet connection (ADSL2+ with 2 MBit Uplink/ 16 MBit Downlink). I am looking for a big upgrade (fibre) this year, but until then…

For testing purposes I also ran a Monero full node. This node clogged my 2 MBit Uplink entirely, so I had to retire it again.

  • How come the monero node seemed to work as a public node without opening incoming ports for Monero? Is it because Monero is using Tor/Onion routing and therefor doesn’t need an incoming open port (e.g. when you have an onion-webserver on a Raspberry Pi, you are also able to reach it from the Internet, even with no incoming ports opened within the router)??
3 Likes

Hey, happy to see that you’re considering running a node.

  1. It’s pretty hard to estimate how much bandwidth you’d need, as it depends on blocks and peers. If your internet is only 2mbps, I’d consider just waiting imo.

  2. I’m really unfamiliar with the Monero full node client and how peering work. Open to learning how they do things.

3 Likes

Hi Chikun friends,
is there a posibility to configure Litecoin core to listen to an incoming port other than 9333, e.g. a port that you obtained from your VPN provider?

2 Likes

Yes. Write -port= when launching it from the command line. For more information, type litecoin-core -h

2 Likes

In Litecoin Core’s net.cpp there is some code concerning non-9333 port

// Do not allow non-default ports, unless after 50 invalid
// addresses selected already. This is to prevent malicious peers
// from advertising themselves as a service on another host and
// port, causing a DoS attack as nodes around the network attempt
// to connect to it fruitlessly.
if (addr.GetPort() != Params().GetDefaultPort() && nTries < 50)
    continue;

So, if I operate with @Caballa suggestion to use the switch -port=, will my node still be mostly a leeching node, not providing service for others most of the time?

So, am I right with the following assumption:

  • No port open : only leecher / only verifying own transactions according to @losh11 in the podcast
  • non-default port : mostly leecher, only when other nodes can’t find port 9333 nodes, my node will be used by them
  • default port 9333 : full participant
  • running behind Tor Proxy : ??? will my node be leecher except providing service for other Tor users ???

It seems that non-default ports aren’t the norm, but also not that uncommon…
grafik

I have got a full node now with port 9333 open and running.

  • is there a suggestion which MWEB-enabled light wallet (android or Windows/Linux PC) I can connect to that node to do some MWEB transactions?
  • how to connect a MWEB light client (like “Newborn” ?! ) to your own node?