Node Discovery Issue | Bitcointalksearch.org

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: shorena on March 12, 2015, 05:46:40 AM

Quote from: Geremia on March 11, 2015, 11:41:02 AM

-snip-
P.S.: The author of Bitnodes thought my issue might be related to: https://github.com/bitcoin/bitcoin/issues/48

Which is why I was wondering whether you are connected through Tor to other nodes outside of Tor or if you are connected to nodes inside the Tor network. The later would not be a problem. Seeing that you have 8 outgoing connections but no incomming connections now, this might also be a firewall issue.

It's working now: 12 incoming, 8 outgoing connections. I think it took some time for my node to become established. My IPv6 address did change, although my IPv4 address was the same. Maybe that confused it.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: Geremia on March 11, 2015, 11:41:02 AM

-snip-
P.S.: The author of Bitnodes thought my issue might be related to: https://github.com/bitcoin/bitcoin/issues/48

Which is why I was wondering whether you are connected through Tor to other nodes outside of Tor or if you are connected to nodes inside the Tor network. The later would not be a problem. Seeing that you have 8 outgoing connections but no incomming connections now, this might also be a firewall issue.

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: shorena on March 10, 2015, 06:55:09 PM

Does getpeerinfo return .onion addresses or ipv4/6 addresses?

I am connected to Tor, and Tor works well for the outgoing connections.

Quote from: shorena on March 10, 2015, 06:55:09 PM

Are you restricted to using Tor or can you establish connections via ip4/6 at the same time?

I do accept both IPv4 and IPv6 addresses.

Well, today I have 8 incoming and 8 outgoing nodes! I think it just took my node a few days of using the same IPv6 and IPv4 addresses before the network considered it stable.

P.S.: The author of Bitnodes thought my issue might be related to: https://github.com/bitcoin/bitcoin/issues/48

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

I think what Geremia is refering to is that bitcoin core prefers to connect to nodes that are not part of the same subnet. IIRC 192.168.0.0/24 is not preferred as node to connect to if you have an IP in the same range.

I suspect this is related to Tor as it would look from the outside like you change your IP constantly. Nodes from within the Tor network would not be affected by this though.

Does getpeerinfo return .onion addresses or ipv4/6 addresses? Are you restricted to using Tor or can you establish connections via ip4/6 at the same time?

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: Newar on March 10, 2015, 01:32:13 AM

I don't see how that article explains your claim of:

Quote from: Geremia on March 08, 2015, 12:13:20 AM

It seems my node isn't really needed since I'm in a city with a large density of already-existent nodes.

Maybe I don't understand how node discovery works, then.

Newar

legendary

Activity: 1358

Merit: 1001

https://gliph.me/hUF

Quote from: Geremia on March 10, 2015, 01:04:15 AM

Quote from: Newar on March 09, 2015, 05:50:20 AM

Quote from: Geremia on March 09, 2015, 02:50:48 AM

[...]
The client wouldn't, but the network would.
[...]

Care to explain how?

https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery

I don't see how that article explains your claim of:

Quote from: Geremia on March 08, 2015, 12:13:20 AM

It seems my node isn't really needed since I'm in a city with a large density of already-existent nodes.

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: Newar on March 09, 2015, 05:50:20 AM

Quote from: Geremia on March 09, 2015, 02:50:48 AM

[...]
The client wouldn't, but the network would.
[...]

Care to explain how?

https://en.bitcoin.it/wiki/Satoshi_Client_Node_Discovery

Newar

legendary

Activity: 1358

Merit: 1001

https://gliph.me/hUF

Quote from: Geremia on March 09, 2015, 02:50:48 AM

[...]
The client wouldn't, but the network would.
[...]

Care to explain how?

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: Newar on March 08, 2015, 12:21:55 AM

Quote from: Geremia on March 08, 2015, 12:13:20 AM

[...]
It seems my node isn't really needed since I'm in a city with a large density of already-existent nodes.

How would the client know that?

The client wouldn't, but the network would.

Quote from: Newar on March 08, 2015, 12:21:55 AM

Have you tried adding nodes with the addnode command? Did you change anything in your conf file?

no

Newar

legendary

Activity: 1358

Merit: 1001

https://gliph.me/hUF

Quote from: Geremia on March 08, 2015, 12:13:20 AM

[...]
It seems my node isn't really needed since I'm in a city with a large density of already-existent nodes.

How would the client know that?

Have you tried adding nodes with the addnode command? Did you change anything in your conf file?

Geremia

sr. member

Activity: 507

Merit: 253

Quote from: Newar on March 07, 2015, 10:28:46 PM

Do you have a fixed IP from your provider? How many peers are connected to your node?

Currently, I have 2 connected to the IPv6 address of my node, but none connected to the IPv4 address.
It seems my node isn't really needed since I'm in a city with a large density of already-existent nodes.

Newar

legendary

Activity: 1358

Merit: 1001

https://gliph.me/hUF

Do you have a fixed IP from your provider? How many peers are connected to your node?

Geremia

sr. member

Activity: 507

Merit: 253

On my node's https://getaddr.bitnodes.io/ page, clicking the "Check Node" button on the bottom of the page reports that the node associated with this IP address is up; however, at the top of the page, "Node Status" says it isn't. It seems my node is having discoverability issues with the Bitcoin network, although https://getaddr.bitnodes.io/ can ping it just fine.

Why would this be?

I've even run the node on a different network (one even supporting IPv6), and I get the same issue.

I'm thinking it may have something to do with my running bitcoin-qt with a Tor proxy, although I am explicitly supplying the "--listen" flag to bitcoin-qt.

(I've asked on Github, but it doesn't seem to be a big but a configuration issue on my end; or perhaps the BTC network in my area just doesn't have need of more nodes?)

Topic: Node Discovery Issue (Read 1611 times)