-
m-relay<r4v3r23:monero.social> are the monerodevs.org nodes rate-limited?
-
m-relay<ofrnxmr:xmr.mx> Yes
-
m-relay<ofrnxmr:xmr.mx> Technically, they are "# of connections" limited
-
m-relay<r4v3r23:monero.social> meaning
-
m-relay<r4v3r23:monero.social> # of users limited or # of connection trie
-
m-relay<r4v3r23:monero.social> whoa
-
m-relay<ofrnxmr:xmr.mx> The max number of connections per ip is limited
-
m-relay<r4v3r23:monero.social> but it resets fast?
-
m-relay<r4v3r23:monero.social> testing something on a monerodevs node and want to make sure that the issue is node related
-
m-relay<ofrnxmr:xmr.mx> 18.4.0 enforces this for everyone
-
m-relay<r4v3r23:monero.social> im opening/closing app in rapid succession
-
m-relay<ofrnxmr:xmr.mx> The problem with monerodevs nodes, is that they are popular and public. So they are being attacked
-
m-relay<r4v3r23:monero.social> eventually it stops connecting to node. but if i wait a minute or 2 itll then connect
-
m-relay<ofrnxmr:xmr.mx> If using tor exit nodes, its probably 3 max connections per exit node. If using onion (which accesses via 127.0.0.1) the number is higher, but its easier to attack 127.0.0.1/onion
-
m-relay<r4v3r23:monero.social> makes sense. but how quick does it reset?
-
m-relay<ofrnxmr:xmr.mx> As soon as one of the connections disconnects
-
m-relay<r4v3r23:monero.social> must be that then. changed nodes and the issue is gone
-
m-relay<ofrnxmr:xmr.mx> But if someone is constantly attacking it, you need to get lucky to get connected
-
m-relay<ofrnxmr:xmr.mx> Default limits are 3 per public ip, 25 per private ip, 100 total
-
selstaif the connection closes on app close then it should not be an issue with the new limits
-
selstathe new limits are only relevant for simultaneous connections
-
m-relay<r4v3r23:monero.social> it does, but i was doing multiple rapidfire connections per minute