15:16:32 <DataHoarder> sethsimmons: FoxMulder is asking about your guide/docker p2pool setup in #p2pool-log, having issues with p2pool not connecting to RPC
15:36:58 <DataHoarder> sethsimmons: your docker-compose setup does not expose port 18081 which is what p2pool uses to request it, so adding to monerod this --rpc-bind-ip=0.0.0.0 --rpc-bind-port 18081 --confirm-external-bind --restricted-rpc
15:37:11 <DataHoarder> made it work, plus added link to monerod in p2pool
15:37:32 <DataHoarder> additionally the user had to pull new image after they managed to get it connected, due to new one being pushed
15:40:11 <DataHoarder> they were using the full docker-compose.yml btw
16:05:23 <sethsimmons> Adding `--rpc-port "18089"` instead, I'm not sure how I missed that :/
16:05:27 <sethsimmons> To p2pool
16:07:26 <DataHoarder> no link needed I guess, due to exposing ports?
16:07:37 <DataHoarder> also btw, do you know about the multiline syntax?
16:08:07 <sethsimmons> Don't need to either way as they're using the same network
16:08:14 <sethsimmons> DataHoarder: Not very familiar, no!
16:08:41 <DataHoarder> well, sometimes they don't get ports properly exposed
16:08:56 <DataHoarder> see here sethsimmons https://github.com/WeebDataHoarder/p2pool-compose/blob/master/docker-compose.yml#L36-L40
16:09:15 <sethsimmons> sethsimmons: Because the Dockerfile natively exposes those ports it works without
16:09:16 <DataHoarder> >-
16:09:38 <DataHoarder> yes, because it exposes them, indeed
16:09:39 <sethsimmons> Yeah I'm using that here but it's new to me:
16:09:39 <sethsimmons> https://sethforprivacy.com/guides/run-a-p2pool-node/#download-and-run-monerod-and-p2pool-via-docker
16:09:56 <DataHoarder> ah yes, was looking at monerod
16:10:15 <DataHoarder> define in-peers too to some limit, or so sech1 recommends
16:10:19 <sethsimmons> I should migrate the monerod ones over though
16:10:34 <DataHoarder> so you don't end up with too many connections if they expose their port
16:10:36 <sethsimmons> DataHoarder: Wonder why, default is no-cap IIRC
16:11:00 <sethsimmons> DataHoarder: Makes sense, I'll add that now
16:11:00 <DataHoarder> but you can end with too many and hit fdlimit
16:12:18 <sethsimmons> Migrating to:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/bda0f56916bc23be21a06ce59b2a508fc466d6ef)
16:14:38 <DataHoarder> also I see https://github.com/monero-project/monero/issues/7963, nice
16:15:05 <sethsimmons> DataHoarder: Yeah, would be very nice to have :)
16:15:25 <DataHoarder> you can already get around it without hardcoding though, but it is suboptimal
19:44:36 <sudo_ki[m]> Why would someone want to connect/listen to a p2p stratumserver? 
19:44:36 <sudo_ki[m]> I wonder if anyone has noticed alien connections
19:50:43 <sech1> Port scans maybe
19:59:45 <sudo_ki[m]> What protections are in place for this kind of thing? Are there ban criteria for clients who connect but don't accept jobs?
20:07:42 <sech1> if they send invalid data they're banned
20:19:08 <sudo_ki[m]> So if random clients connected, there's nothing to really worry about
20:43:15 <pauliouk> if you're lucky, they might even mine a little for you