00:05:08 <m-relay> <p​acksman:matrix.org> Hello everyone 
00:05:08 <m-relay> <p​acksman:matrix.org> I’m a Grower and supplier of quality cannabis and psychedelics products like shrooms, DMT, Lsd, Mdma, ketamine, chocolate bars,Meth, cart vapes, buds, wax, shatter, Edibles,distillates, chill pills and others like (bank notes) and cloned cards which have been tested to work perfectly💯.
00:05:09 <m-relay> <p​acksman:matrix.org> We do Prescription for patients. See products in channel below 👇👇👇👇👇
00:05:09 <m-relay> <p​acksman:matrix.org>  https://t.me/pacexoitic
00:39:10 <Cat9> I don't see catnip listed
02:24:23 <lza_menace> we don't do that in here
02:25:32 <lza_menace> observers, be mindful of strangers shilling products in chat...this is not the forum for that. fed shit
02:36:57 <m-relay> <p​lowsof:matrix.org> they where banned on Matrix side, this is not shown on IRC x
03:21:41 <lza_menace> Cool 
03:47:38 <m-relay> <1​23bob123:matrix.org> Do i notify cloudflare again?
11:40:03 <gingeropolous> hrm, i wonder if we can use the "backping failed" log entry to allow fail2ban to block malicious nodes
11:47:14 <gingeropolous> oh yeah. this could be a thing for sure.
11:47:22 <gingeropolous> grep "back ping" bitmonero.log*  | grep from | cut -f 6-7 | cut -f 9 -d " " | sort | uniq -c | sort
11:47:28 <gingeropolous> if anyone wants to see their list of repeat offenders
11:48:43 <gingeropolous> now how's this fail2ban syntax actually work... hrmmmmm
11:51:04 <gingeropolous> ugh. need to matrix regex into my brain. dangit
11:53:50 <gingeropolous> i know! chatgpt
11:54:35 <selsta> gingeropolous: not sure if back ping failed = malicious node
11:55:26 <selsta> fwiw my list is as complete as it gets
11:55:47 <gingeropolous> lol. when you ran that oneliner?
11:56:00 <gingeropolous> oh or your original banlist
11:56:20 <selsta> i've often updated the original ban list
11:56:33 <gingeropolous> gotcha
11:57:44 <gingeropolous> and that was created by probing an IP, not necessarily directly from the bitmonero logs?
12:01:29 <gingeropolous> well, probing all ip connections
12:03:04 <gingeropolous> holy shnikies. grep ERROR bitmonero.log* | grep "Error state" | cut -f 6 | cut -f 1 -d " " | cut -f 1 -d ":" | sort | uniq -c
12:03:19 <gingeropolous> that gives a lot too. 35536 on one IP
12:04:35 <gingeropolous> methinks that not a healthy node tryin to connect
12:06:45 <gingeropolous> but dude we can't rely on a centralized banlist!
12:07:36 <gingeropolous> and holy shit these 35k attempts were all in the span of hours
12:08:18 <gingeropolous> once every 2 seconds
12:09:35 <gingeropolous> my poor daemon. having to deal with this nonsense
12:10:36 <gingeropolous> just gotta be mindful of which log strings i pick in case they change over time...
13:22:57 <selsta> 12:57 <gingeropolous> and that was created by probing an IP, not necessarily directly from the bitmonero logs? <-- mainly from monerod logs
13:31:23 <selsta> for example nodes that run monerod < v0.18.2.0 can show back ping failed, but they are not malicious
13:41:28 <gingeropolous> roight
15:19:28 <lza_menace> I’d be down with a fail2ban config if it cut down on bandwidth usage
15:24:36 <plowsof> if bandwidth increases are gained, please enable your tor seed node to balance it out xD
15:24:50 <plowsof> bandwidth reductions obtained*
17:00:08 <lza_menace> why is monerod trying to bind a port twice here?  https://irc.cloud.lzahq.tech/uploads/ffaeb2050589be29/image.png 
17:01:12 <lza_menace> args https://irc.cloud.lzahq.tech/uploads/a23e072f828cd880/image.png 
17:38:23 <m-relay> <p​lowsof:matrix.org> fixed^ 🚀
20:47:34 <gingeropolous> i gotta figure out this tor / i2p thing with monerod
21:00:54 <m-relay> <1​23bob123:matrix.org> Ask in #monero-support:monero.social
21:02:13 <m-relay> <1​23bob123:matrix.org> Create a ticket and leave your number and level 2 support will call you
21:04:12 <m-relay> <p​lowsof:matrix.org> wownero can help you https://forum.wownero.com/index.php?topic=588.0 (just change the ports accordingly)
21:37:46 <thanksgiver> HELO WE'VE BEEN HACKED FOR 2k XMR BUT DON T WORRI WE'LL FORENSIC OUR BACKDOORED DEV MACHINES AFTER "THANKS"_GIVING      X---------_DDDDD 
21:37:46 <thanksgiver> it's not a time-sensitive issue after all... always yours, Luigi1111111
21:37:47 <thanksgiver>  
21:50:36 <atip> luigi1111w: Please don't investigate anything at all. After thanksgiving, before thanksgiving - it doesn't matter after all, right? You aren't able to anyway, since MSWIN noobs like you are only capable of restarting their router to fix connectivity issues.