If I understood OP correctly thats not helping. The goal is to have 30 ipv4 connections (max) and 70 tor connections. Same client. Afaik this isnt possible currently. Can probably be coded though.
Yes. That's what I want.
I'm pretty sure you can use onlynet=Tor with some addnode IPv4 addresses.... dunno, been a while
Didnt think about it this way, should work. Afaik addnode just adds a node without further checking the network. IIRC I had some nodes in a local testnet I added via ipv4 but they would show as ipv6 which confused me at first.
So with a good list of static ipv4 nodes this would indeed speed up an otherwise tor only node.
I see. The problem here is I have to maintain a good list of static ipv4 nodes and from time to time I still have to restart the client to make a changed config file with updated addnoses affect the client. Even if a connection dropps for some reason what always can happen, in the long term the ipv4 connected nodes will become 0 and I still have to restart the client over time?
Seems like a "setup and forget"-solution is not possible (yet)? In this case the current status where I just retart the client when I don't like the amounts of different connection types is still the easiest solution?
with addnode, if a connection drops, it'll retry it every x seconds. I think the base retry is every 120 seconds.
There are some ipv4 nodes that have been up 95%+ for years. try http://bitcoin.sipa.be/seeds.txt ... I'd say that's pretty long term
