I've seen it get down to 8 incoming before I have bumped the router. I would assume that even those would eventually drop off as well given time.
The NAT table filling up is kinda what I suspect as well. I'm going to check with Asus to see if there is a way to timeout the connections.
Topic: Bitcoin full node connections dropping (Read 2388 times)
I am running a full node with Bitcoin-qt on an ubuntu server (ARM based). The node seems to spin up fine and will start receiving incoming connections. I believe I have seen upwards to about 60 incoming connections. The problem is that after a couple of days the incoming connections will start to drop off. If I reboot my router (Asus RT-AC66U) then it will begin to receive incoming connections, yet after another couple of days they start to drop once again.
If I check the status of my node at https://getaddr.bitnodes.io/#join-the-network, initially it will say that my node is up. When the connections begin to drop then that site will report that it can no longer connect to my node. Rebooting the router and it can connect once more.
Can anyone give me some insight on what is happening and perhaps a way to correct this problem? I would like to continue running a full node but don't feel like bumping my router ever few days to do so.
Thanks.
If I check the status of my node at https://getaddr.bitnodes.io/#join-the-network, initially it will say that my node is up. When the connections begin to drop then that site will report that it can no longer connect to my node. Rebooting the router and it can connect once more.
Can anyone give me some insight on what is happening and perhaps a way to correct this problem? I would like to continue running a full node but don't feel like bumping my router ever few days to do so.
Thanks.
Interesting problem. When you say the connections start to drop off, how low does the connection count go?
I suspect that your router is not dropping TCP connections*, thus clogging up the NAT table. Do you have a way to lower TCP timeout?
* Note: connections as in TCP connections, not the number of peers you have a connection to
i think thats about psu he used before timeout makesure you put in right place. * Note: connections as in TCP connections, not the number of peers you have a connection to
I suspect that your router is not dropping TCP connections*, thus clogging up the NAT table. Do you have a way to lower TCP timeout?
* Note: connections as in TCP connections, not the number of peers you have a connection to
* Note: connections as in TCP connections, not the number of peers you have a connection to
I am running a full node with Bitcoin-qt on an ubuntu server (ARM based). The node seems to spin up fine and will start receiving incoming connections. I believe I have seen upwards to about 60 incoming connections. The problem is that after a couple of days the incoming connections will start to drop off. If I reboot my router (Asus RT-AC66U) then it will begin to receive incoming connections, yet after another couple of days they start to drop once again.
If I check the status of my node at https://getaddr.bitnodes.io/#join-the-network, initially it will say that my node is up. When the connections begin to drop then that site will report that it can no longer connect to my node. Rebooting the router and it can connect once more.
Can anyone give me some insight on what is happening and perhaps a way to correct this problem? I would like to continue running a full node but don't feel like bumping my router ever few days to do so.
Thanks.
If I check the status of my node at https://getaddr.bitnodes.io/#join-the-network, initially it will say that my node is up. When the connections begin to drop then that site will report that it can no longer connect to my node. Rebooting the router and it can connect once more.
Can anyone give me some insight on what is happening and perhaps a way to correct this problem? I would like to continue running a full node but don't feel like bumping my router ever few days to do so.
Thanks.
Jump to: