Author

Topic: No inbound connections (Read 834 times)

legendary
Activity: 3416
Merit: 4658
January 26, 2016, 10:03:47 PM
#7
I suspect if you get yourself a VPN service and set up port forwarding properly, you could probably get through the McD firewall to receive connections
staff
Activity: 3374
Merit: 6530
Just writing some code
January 26, 2016, 04:27:27 PM
#6
Its still a full node and its still fully operational. Sounds like the port is block by a firewall.

It's at McD ( again Smiley ), so it is almost certainly that.

As I see it, the sequence is this.

Start the core
Load the block index
Verify the blockchain on disk
Start looking for peers, and stop when you have found eight.
Synchronise with the public blockchain
Sit there doing its thing.

Looking at the network traffic analyser, there is loads of green, and a very small amount of red. Isn't the green downloaded packets, and the red uploads? That seems to indicate bidirectional traffic. So does the fact that inbound connections are blocked mean that I can go looking for peers, but nobody can try to find me? ( I'm guessing here. ).
Yes. An outbound connection means that you initiated the connection and then the downloaded data is all technically replies to your requests. Any connection which is initiated by someone else is not allowed by firewalls unless port forwarding is enabled.
legendary
Activity: 2688
Merit: 2444
https://JetCash.com
January 26, 2016, 01:33:07 PM
#5
Its still a full node and its still fully operational. Sounds like the port is block by a firewall.

It's at McD ( again Smiley ), so it is almost certainly that.

As I see it, the sequence is this.

Start the core
Load the block index
Verify the blockchain on disk
Start looking for peers, and stop when you have found eight.
Synchronise with the public blockchain
Sit there doing its thing.

Looking at the network traffic analyser, there is loads of green, and a very small amount of red. Isn't the green downloaded packets, and the red uploads? That seems to indicate bidirectional traffic. So does the fact that inbound connections are blocked mean that I can go looking for peers, but nobody can try to find me? ( I'm guessing here. ).
member
Activity: 74
Merit: 10
January 26, 2016, 01:07:03 PM
#4
Port forward 8333 in your router.
legendary
Activity: 2954
Merit: 4158
January 26, 2016, 11:19:39 AM
#3
Inbound connections allow for more peers to connect to your node to get more information and that's it. Your connected peers will still receive blocks and transactions from you, just like how they relay to you.
copper member
Activity: 1498
Merit: 1499
No I dont escrow anymore.
January 26, 2016, 11:13:28 AM
#2
Its still a full node and its still fully operational. Sounds like the port is block by a firewall.
legendary
Activity: 2688
Merit: 2444
https://JetCash.com
January 26, 2016, 10:56:21 AM
#1
I wondered why I was only getting 8 connections, and all of them are outbound. I ran a port scanner, and this is what I got.

Checked port 8333 on Host/IP 46.233.116.169...

 The checked port (8333, service unknown) is offline/unreachable

Reason: Connection refused (111)

Portscan ran for 0.0152 seconds

So I guess that with no inbound connections, I'm not running a full node. Will this be a problem for me, and what are the ramifications?
Jump to: