Bitcoin Core Inbound connection

[erictan90]

Hi,



Please refer to image link above, is that mean I have 0 Inbound connection?

I noticed that I need Inbound connection to support Bitcoin Network.

Please help.

[1714079963]

1714079963

[1714079963]

1714079963

[mocacinno]

Check the link, it shows:

That page doesn't exist

I do see the screenshot.... 10 outbound connections, 0 inbound... looks ok to me.

Is this a wallet, or do you want to run a full node 24/7?

[erictan90]

yup, 0 inbound connection. yes, I want to run full node to support the Bitcoin network.

[mocacinno]

yup, 0 inbound connection.

The thing is: if you only want to use bitcoin core as a wallet, you don't actually NEED inbound connections... You made outbound connections, so you can download blocks and transactions. You only need inbound connections if you want your bitcoin core to run as a full node to support the network.

I assume you're working on a pc in your lan? In that case, it's probably upnp, firewall, port forewarding,... related.

[mocacinno]

I googled for a port forewarding tutorial for luci (which i can deduct from your screenshot)

https://www.cfos.de/en-us/cfos-personal-net/port-forwarding/openwrt.htm

the machine running your node will need to have a fixed ip.

For the rest, it might be a good thing to read this:
https://bitcoin.org/en/full-node

[NeuroticFish]

Please refer to image link above, is that mean I have 0 Inbound connection?

I noticed that I need Inbound connection to support Bitcoin Network.

1. The image link works for me too. I didn't embed it here because it's too big and it actually doesn't help that much.
2. Yes, you have 0 inbound connections. You still somewhat help the network though with the outbound connections.
3. If you want to allow inbound connections too, then you will have to do settings in your router (port forwarding) and probably in your firewall too (allow inbound connections, see firewall configuration). You may want to read the whole network configuration section in the Bitcoin help page.

[NeuroticFish]

okay, I try to forward port first

https://ibb.co/cQfqQPQ

like this, right?

I am noob in technical 

1. I have a feeling that posting this kind of pictures is not OK for your network's security.
2. The internal IP address may have to be different (not 192.168.169.1). It has to be the IP of the computer having Bitcoin Core on it. You can find that out (on that PC) with

Code:

hostname -I

[erictan90]

Please refer to image link above, is that mean I have 0 Inbound connection?

I noticed that I need Inbound connection to support Bitcoin Network.

1. The image link works for me too. I didn't embed it here because it's too big and it actually doesn't help that much.
2. Yes, you have 0 inbound connections. You still somewhat help the network though with the outbound connections.
3. If you want to allow inbound connections too, then you will have to do settings in your router (port forwarding) and probably in your firewall too (allow inbound connections, see firewall configuration). You may want to read the whole network configuration section in the Bitcoin help page.

"You still somewhat help the network though with the outbound connections."

could you describe more about this?

"Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin?s port, port 8333. Unfortunately many routers don?t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details. "

It is too hard for me. If I change my internet provider (router), maybe my new router will automatically configure itself to allow inbound connections to Bitcoin?

[ABCbits]

"You still somewhat help the network though with the outbound connections."

could you describe more about this?

Basically it means you still relay block and transaction with another Bitcoin node (where you connect to them as part of outbound connection).

"Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin?s port, port 8333. Unfortunately many routers don?t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details. "

It is too hard for me. If I change my internet provider (router), maybe my new router will automatically configure itself to allow inbound connections to Bitcoin?

No matter ISP/router you use, usually you need to configure it by yourself. But if you're looking for easier way, enable UPnP (Universal Plug and Play) on your router and configure Bitcoin Core to use UPnP (should be availbale on Bitcoin Core setting).

[NeuroticFish]

"You still somewhat help the network though with the outbound connections."

could you describe more about this?

Even if it doesn't accept inbound connections (others connecting to you), your node initiates outbound connections (to other nodes), hence it does participate to the network. Just it will connect to a much smaller overall number of nodes.

"Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin?s port, port 8333. Unfortunately many routers don?t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details. "

It is too hard for me. If I change my internet provider (router), maybe my new router will automatically configure itself to allow inbound connections to Bitcoin?

You may already be on the right track based on the PM you've sent. You seem to have figured out the correct IP to forward to. As I said in PM, you may have to also look into the DHCP settings to make sure your computer will get the same IP at next reboot/startup.

I don't think that you have to buy new modem.

----
Of course, another solution can be what @ETFbitcoin has been writing (UPnP), but I'm not familiar with those settings.

[erictan90]

"You still somewhat help the network though with the outbound connections."

could you describe more about this?

Basically it means you still relay block and transaction with another Bitcoin node (where you connect to them as part of outbound connection).

"Home connections are usually filtered by a router or modem. Bitcoin Core will request your router automatically configure itself to allow inbound connections to Bitcoin?s port, port 8333. Unfortunately many routers don?t allow automatic configuration, so you must manually configure your router. You may also need to configure your firewall to allow inbound connections to port 8333. Please see the following subsections for details. "

It is too hard for me. If I change my internet provider (router), maybe my new router will automatically configure itself to allow inbound connections to Bitcoin?

No matter ISP/router you use, usually you need to configure it by yourself. But if you're looking for easier way, enable UPnP (Universal Plug and Play) on your router and configure Bitcoin Core to use UPnP (should be availbale on Bitcoin Core setting).

Hi, how to enable UPnP (Universal Plug and Play) on my router?

[erictan90]

Check the link, it shows:

That page doesn't exist

I do see the screenshot.... 10 outbound connections, 0 inbound... looks ok to me.

Is this a wallet, or do you want to run a full node 24/7?

Hi, is that only receiving inbound connections after it is fully synced?
I think I should check  again after it is fully synced (100%).

[mocacinno]

To be honest, my node has been online for many, many years... So it has been a long, long time ago since i last synced a node.
But, if i remember correctly, you should be able to get inbound connections while syncing... Not 100% sure tough, but if memory serves me correct, it should.

What you could potentially do is telnet to port 8333 from either your node or another pc in your network.
IF you see an output like the following, you're listening on port 8333

Code:

telnet localhost 8333
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Now, do the same from OUTSIDE your LAN... Use a telnet app on your phone while connected to 3G/4G/5G (not your wifi) and try to telnet to port 8333 on your WAN ip. You can find your WAN ip by surfing to a site like https://whatismyipaddress.com/ (no affiliation) from a device connected to your wifi (or physically connected with an utp cable...

[erictan90]

To be honest, my node has been online for many, many years... So it has been a long, long time ago since i last synced a node.
But, if i remember correctly, you should be able to get inbound connections while syncing... Not 100% sure tough, but if memory serves me correct, it should.

What you could potentially do is telnet to port 8333 from either your node or another pc in your network.
IF you see an output like the following, you're listening on port 8333

Code:

telnet localhost 8333
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

https://i.imgur.com/B29qvg6.png

Now, do the same from OUTSIDE your LAN... Use a telnet app on your phone while connected to 3G/4G/5G (not your wifi) and try to telnet to port 8333 on your WAN ip. You can find your WAN ip by surfing to a site like https://whatismyipaddress.com/ (no affiliation) from a device connected to your wifi (or physically connected with an utp cable...

how to telnet to port 8333 from my Macbook?  any youtube videos to show the steps? 

[mocacinno]

--snip--

how to telnet to port 8333 from my Macbook?   any youtube videos to show the steps?  

I don't have a macbook, but i can find some threads complaining that telnet was removed from their image in a certain version of the OS.

You could always just install a telnet app on your phone and firstly connect trough your home wifi and telnet to port 8333 on your lan ip. If it works switch to 3G/4G/5G and try the same app, the same port but your WAN ip.

• If you can connect over LAN but not WAN, your node itself is listening, but there's something incorrectly set up with your firewall/port forewarding/upnp...
• If you can not connect over LAN, you don't even have to bother with the WAN connection, it's pretty obvious your node isn't listening (yet). Either your node's config needs to be modified, or i was wrong and the node only listens after the initial sync
• If you can connect over LAN and WAN, your node should be reachable from the outside over port 8333

I'm going on a ledge here and guess that the odds are big you have an iphone? I don't have one, but there are tools like this one: https://apps.apple.com/us/app/telnet-lite/id286893976 (never ever tested it, no idear if it even works).

For android, there are also telnet tools available like this one: https://play.google.com/store/apps/details?id=mobiletelnet.feng.gao&hl=nl&gl=US also, never tested by me (eventough i have an android device, i don't use it for telnetting).

[erictan90]

It is too complicated for me. Bitcoin Core should make it simple for noob like me to run bitcoin node. 😂
If anyone got any YouTube videos to set up，please share with me.
Probably, I have to give up for now.

[mocacinno]

It is too complicated for me. Bitcoin Core should make it simple for noob like me to run bitcoin node. 😂
If anyone got any YouTube videos to set up the port 8333, please share with me.
Probably, I have to give up for now.

I hear what you're saying, but eventough you haven't posted any output from the telnet commands, i think the problem lays in your network setup... And truth be told, the bitcoin core developers can't really do anything about this...

If you wanted to run a webserver on your LAN and make it available for the outside world, you'd be faced with exactly the same problems... Or if you wanted to access a network camera in your lan from the internet, you'd have exactly the same problems aswell.

The problem is that there isn't a "magic bullet" that completely solves this issue... There are dozens and dozens of active router manufacturers, there are hundreds of ISP's,... It's simply impossible to write a complete newbie-friendly walktrough for setting up your home network to run a bitcoin node on your lan wilst having it accessible from the WAN for every router/isp combination out there.

There's the upnp protocol that should make your life a bit easyer, but this protocol also makes sure that malware can abuse upnp so an intruder can access vulnerable device in your LAN pretty easily, that's why upnp is turned off quite often. And for example, it seems your router doesn't even include upnp in it's default feature set (it seems you have to download it seperately).

Now, don't get me wrong, i'm not blaming you for anything... Network setup is quite hard, that's why big company's have to hire network specialists . I do applaud you for trying tough!

[erictan90]

If I use the MyNode, do I need to manually configure my router to open port 8333?

Is it just a plug and play thing?

[mocacinno]

If I use the MyNode, do I need to manually configure my router to open port 8333?

Is it just a plug and play thing?

I had to lookup MyNode, it seems to be a prebuilt image that you can either download or purchase an rPi loaded with said image. This being said, odds are you'll run into exactly the same problems as you're having now: you need to foreward the correct port on your home router and configure the firewall... This is something no plug and play device can ever do, it's always up to you to setup your own router and firewall i'm afraid.

[mocacinno]

If I use the MyNode, do I need to manually configure my router to open port 8333?

Is it just a plug and play thing?

I had to lookup MyNode, it seems to be a prebuilt image that you can either download or purchase an rPi loaded with said image. This being said, odds are you'll run into exactly the same problems as you're having now: you need to foreward the correct port on your home router and configure the firewall... This is something no plug and play device can ever do, it's always up to you to setup your own router and firewall i'm afraid.

Intesting! They told me that no need port forwarding. https://ibb.co/VpFrqwj

However, I am moving to a new apartment soon with a new internet provider. I will try again (port 8333) with the new router.

The screenshot doesn't really show the original question, nor is their answer extensive. Odds are they mean that you can run their device, it'll open outbound connections, and that's enough for the device to function (since you don't really *need* inbound connections). The page he refers to doesn't really give any additional information either. But the thing is: no device will automagically initiate port forewarding and firewall rule creation... Unless it's using upnp (which we have already establed, is a protocol that isn't pre-installed on your device, nor do i find it wise to just rely on upnp).