I tried that a few weeks ago and got similar errors.
Try TC instead. It’s CLI is fiddly, but it works.
2 Likes
This may help
1 Like
When you run through vm you will get in trouble with the number of connections needed and won’t connect to all needed peers. What it seems like you need is a router which can handle larger amount of connections in the NAT table
Thanks for the suggestion. I run the VM in bridged mode, and it’s running with near native performance since it’s running on an intel chip with virtualisation support (so VM vs bare metal is likely not an issue). The main issues are internet bandwidth (when I was running testnets, the uploads were maxing out my upload pipe which effectively stops everything else from working including downloads), and I think the primary issue now is competiton from other nodes. i have a decent number of peers. I’m guessing when people start uploading more data, I should get at least some records.
I’m not really doing this to earn anything, just to be part of the network.
Using TC, you can limit upload bandwidth as follows. It sets a 20mbit limit, with some wiggle room to burst.
/usr/sbin/tc qdisc add dev <ethernet_device>} root tbf rate 20mbit burst 1mbit latency 100ms
(where ethernet device is your actual device name)
1 Like