I was hoping everyone would end up having the same router, or all be running custom firmware, same NIC, or some other easily identifiable culprit. No such luck. However, I have seen this exact same bahaviour in the client Deluge, which is also built upon libtorrent (their current version uses libtorrent v0.15.10). After running for a couple of hours, it loses connection to all DHT nodes. So I'm thinking this might be a libtorrent issue, and not something that is fixable by the qbt devs. I filed a bug report over at libtorrent.org, so hopefully they'll have some help. I will post anything I learn from them here.
I was hoping everyone would end up having the same router, or all be running custom firmware, same NIC, or some other easily identifiable culprit. No such luck. However, I have seen this exact same bahaviour in the client Deluge, which is also built upon libtorrent (their current version uses libtorrent v0.15.10). After running for a couple of hours, it loses connection to all DHT nodes. So I'm thinking this might be a libtorrent issue, and not something that is fixable by the qbt devs. I filed a bug report over at libtorrent.org, so hopefully they'll have some help. I will post anything I learn from them here.