a

\quit

selsta, new host my system auto blocked 100.19.74.83

auto block can have many reasons, I would prefer to only add IPs that are confirmed to do the +2 attack

gotcha

Kronovestan: when was this ban?

also which version are you running?

selsta, the ban here i.imgur.com/FI92PGS.png

is there a way to just restart the rpc server?

Send it signal 15, start it again.

lulz. naw, i mean within monerod itself. I see during monerod boot up it says" rpc server initialized OK". I'd like to maintain my p2p connections etc, but just restart rpc.

It us unclear what that means. Closing the port and reopening it maybe ?

i dunno. all i know is after a while, my high load public remote node can't get more wallet connections. restarting monerod "fixes" it. just wondering if there's an even hackier solution.

Do you have error messages ? If so, which ones ? Do you have loads of entries in /proc/`pidof monerod`/fd ?

v0.17.1.7 binaries are now available at getmonero.org/downloads

cheers

1

Running 0.17.1.7 without block list and out-peers=64, let's see how it goes

sech1, what's the command you do to start it with out-peers

Kronovestan --out-peers 64

or just type out_peers 64 at the monerod command prompt

the 0.17.1.7 release notes should have mentioned that the upgrade of OpenSSL to 1.1.1i was because of their latest security advisory openssl.org/news/secadv/20201208.txt

since monerod can optionally use TLS on a various connections, it was vulnerable to DoS attack thru this vector

the release notes currently just mention the upgrade as if it was a routine change or just did it for no reason

which is rather misleading...

I can update them

"Update OpenSSL to 1.1.1i to fix its recent [openssl.org/news/secadv/20201208.txt](vulnerability)" ?

sounds good

once I incrase to outpeers 64 then the "bug" happens again where I'm off by 2 blocks ... (this is WITHOUT the ban list for testing purps and .7 release)

Kronovestan: it takes a couple seconds to get the peer kicked

stay at 12 out peers so that you connect to attacker nodes less often

if you don't want to use the ban list

hyc, binaryFate: Will update the Reddit thread too

cool

dEBRUYNE you can use same phrasing as in getmonero.org/2020/12/13/monero-0.17.1.7-released.html

ok I'm getting differing hashes now, this is weird.

is dlsrc.getmonero.org/cli/monero-linux-x64-v0.17.1.7.tar.bz2 the same file as downloads.getmonero.org/gui/linux64 ?

binaryFate: ty

Inge-: Should be, yes

used to be

the former comes in at ~80MB, the latter at ~121MB

the latter has the correct sha256sum

caching

try a private browser window

this should get fixed at some point

this was wget and curl from the command line

wait hang on... could be me being an idiot

Mixed in CLI and GUI here, I think all is well. Still a bit twitchy since that time...

Kronovestan: can you post a level 2 log of when that happens ? Ideally from a couple of minutes before it happens.

v0.17.1.7 definitely works for me, +2 nodes get kicked after ~10 seconds

luigi1111w: please upload binaries to github releases

and also update hashes.txt.sig

plz check

moneromooo, of course I'd be happy to... let me make it write the log to a file first. then restart the daemon

set_log 2

Kronovestan: are you sure the +2 peers stay connected?

luigi1111w: looks good