At home node not always discoverable.

[MoreBloodWine]

Ok, so when using this to check my home node: https://getaddr.bitnodes.io/nodes/

Sometimes I get this: <IP>:8333 is unreachable.

While others I get this: <IP>:8333 /Satoshi:0.10.0/

Any ideas why, I do have a static IP. Could it be a propagation thing with my ISP since I did just "order" the static IP I think it was Monday morning 2/16/15 ?

Edit: I know all my ports are open and working being forwarded to the right system since I can check it with the portforward.com port checking program and it always says open.

Edit 2: It is also a new setup and the client is about 41 weeks behind still downloading the chain if that makes a diff with the connection issues or w/e you wana call it. When checking the node it does seem like it hangs a while before coming back with found / unreachable.

Edit 3: The home node in question is also in a switch connected to the router if that makes a diff. I can put it on the router and move some cables around but would need to go out and get a ~6ft ethernet cable.

Or just turn on the laptops wifi but I would rather it be wired.

[1714979404]

1714979404

[shorena]

I get the same message form time to time even though I know my node is up. I suspect that either the node is not answering fast enough or that you are at the maximum number of allowed connections.

[MoreBloodWine]

I get the same message form time to time even though I know my node is up. I suspect that either the node is not answering fast enough or that you are at the maximum number of allowed connections.

As far as max connections go I see it at 11, even 14 sometimes. Not sure what max is tbh but I know my current node running out of disk on my hosted server has seem 80 cons plus before.

[shorena]

I get the same message form time to time even though I know my node is up. I suspect that either the node is not answering fast enough or that you are at the maximum number of allowed connections.

As far as max connections go I see it at 11, even 14 sometimes. Not sure what max is tbh but I know my current node running out of disk on my hosted server has seem 80 cons plus before.

The default setting is 125. If you have not set it to anything lower in the config file, its not the connection limit. Not sure if they have any other criteria. Maybe the details for your node are helpful.

link https://getaddr.bitnodes.io/api/v1/nodes/IP-PORT
e.g. https://getaddr.bitnodes.io/api/v1/nodes/213.165.91.169-8333

or https://getaddr.bitnodes.io/nodes/IP-PORT/
e.g. https://getaddr.bitnodes.io/nodes/213.165.91.169-8333/

[MoreBloodWine]

I get the same message form time to time even though I know my node is up. I suspect that either the node is not answering fast enough or that you are at the maximum number of allowed connections.

As far as max connections go I see it at 11, even 14 sometimes. Not sure what max is tbh but I know my current node running out of disk on my hosted server has seem 80 cons plus before.

The default setting is 125. If you have not set it to anything lower in the config file, its not the connection limit. Not sure if they have any other criteria. Maybe the details for your node are helpful.

link https://getaddr.bitnodes.io/api/v1/nodes/IP-PORT
e.g. https://getaddr.bitnodes.io/api/v1/nodes/213.165.91.169-8333

or https://getaddr.bitnodes.io/nodes/IP-PORT/
e.g. https://getaddr.bitnodes.io/nodes/213.165.91.169-8333/

My at home nodes address is 24.154.55.93:8333

Like I believe I asked in the main post, can new static ip's have propagation delays n for how long usually ?

I'm at a motel in va right now for a funeral tomorrow so won't be infront of the nodes laptop til Sunday night sometime.

[shorena]

-snip-
My at home nodes address is 24.154.55.93:8333

Looks like you have some latency spikes at least to them.
https://getaddr.bitnodes.io/nodes/24.154.55.93-8333/

Like I believe I asked in the main post, can new static ip's have propagation delays n for how long usually ?

Its certain possible, but I would assume that your ISP allready has the routes set up correctly.

I'm at a motel in va right now for a funeral tomorrow so won't be infront of the nodes laptop til Sunday night sometime.

My sympathies.

[MoreBloodWine]

The static ip is assigned through my router otherwise its always dynamic. That being said, the reason I'm keen on an isp thing is because my routers remote management address doesn't even work and I have remote management turned on... so who knows wtf is going on but I knows its irkin me bec my current node that will need to be shut down less I buy more disk will be full on probably 2"months, longer if I'm lucky.

[shorena]

The static ip is assigned through my router otherwise its always dynamic. That being said, the reason I'm keen on an isp thing is because my routers remote management address doesn't even work and I have remote management turned on... so who knows wtf is going on but I knows its irkin me bec my current node that will need to be shut down less I buy more disk will be full on probably 2"months, longer if I'm lucky.

Strange ISP you got there. Not sure, but that might be an issue you have to iron out with them.

[Newar]

The static ip is assigned through my router otherwise its always dynamic. [...]

The external IP is static now (24.154.55.93)?  Or internal? (192.x) Just to clarify... It doesn't make sense to me that your home router would assign an external static IP.


I wouldn't rely on bitnodes for that sort of info too much. The next time you have a chance, start your home node with the GUI (v10.0.0) and go to Help -> Debug window and the peers tab. This will show you how you are connected and the last time (usually a few seconds) you had contact with your peers. If a peer is down for a while (90 seconds, I think?) it will be dropped. So anything you see over that time means your connection is good. If you don't want to start with the GUI you can use the RPC bitcoin-cli to see info about your peers.

[zvs]

Ok, so when using this to check my home node: https://getaddr.bitnodes.io/nodes/

Sometimes I get this: <IP>:8333 is unreachable.

While others I get this: <IP>:8333 /Satoshi:0.10.0/

Any ideas why, I do have a static IP. Could it be a propagation thing with my ISP since I did just "order" the static IP I think it was Monday morning 2/16/15 ?

Edit: I know all my ports are open and working being forwarded to the right system since I can check it with the portforward.com port checking program and it always says open.

Edit 2: It is also a new setup and the client is about 41 weeks behind still downloading the chain if that makes a diff with the connection issues or w/e you wana call it. When checking the node it does seem like it hangs a while before coming back with found / unreachable.

Edit 3: The home node in question is also in a switch connected to the router if that makes a diff. I can put it on the router and move some cables around but would need to go out and get a ~6ft ethernet cable.

Or just turn on the laptops wifi but I would rather it be wired.

if it's still syncing it could be timing out then, so bitnodes would say 'unreachable'

[MoreBloodWine]

I got a synced with consensus block message from the site so time will tell if it holds since its not dl the chain ne more. As for the static thing, my router assigns 192 internals but to use the main static ip. It has to be assigned in the router if that makes sense. Ill do a screenie when I'm home sometime Sunday.

Edit: I'm on the 10.0 client now.

Edit 2: As of 3:18pm EST/EDT, the uptime has creeped up like1.5% or so, last I looked its 29.90%. That being said, when I do the "test" thing. I still get the not found / innaccessable thing so not sure what to think. Will have to check everything out when I'm home but with the chain being done dl'ing, I should be seeing constant up time / found messages so only thing I can think of atm is a propagation thing with the static...

[MoreBloodWine]

https://getaddr.bitnodes.io/nodes/24.154.55.93-8333/

down now, was at 29.90%, now at 26.80% uptime.

Even if I was home I don't know if id be able to solve this but less I can get it figured out ill never have my damn home node at 100% so I can use it. If I can't figure it out I may as well cancel the static ip which is costing $5 additional a month to our cable bill.

[Newar]

Using the addnode command you could connect to one of their nodes if you want to use the tool a bit more reliably:

Code:

54.67.102.19
54.152.68.195
54.94.223.66
54.194.231.211
54.153.147.74

[MoreBloodWine]

Using the addnode command you could connect to one of their nodes if you want to use the tool a bit more reliably:

Code:

54.67.102.19
54.152.68.195
54.94.223.66
54.194.231.211
54.153.147.74

so that just like a hard / always connect when add noding ?

[Newar]

so that just like a hard / always connect when add noding ?

Yes:

-addnode=<ip>          Add a node to connect to and attempt to keep the connection open

You can put it in your config file, so it will try to add the nodes at start up. Or you submit the command whilst it's running.

https://en.bitcoin.it/wiki/Running_bitcoind#Sample_Bitcoin.conf


Addnode will allow other nodes to connect to your node. Alternatively you also could use the connect command which will connect only to the nodes specified. Might even work better in your case.

With both commands you can enter as many as you like. How many it will actually connect to depends on other factors as well though.

[MoreBloodWine]

Ill check it all out when I'm back home sometime Sunday night but ill probably do addnode for atleast 5 constants. Id rather not restrict connections if possible.