-
DataHoarder
sethsimmons: FoxMulder is asking about your guide/docker p2pool setup in #p2pool-log, having issues with p2pool not connecting to RPC
-
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
-
DataHoarder
made it work, plus added link to monerod in p2pool
-
DataHoarder
additionally the user had to pull new image after they managed to get it connected, due to new one being pushed
-
DataHoarder
they were using the full docker-compose.yml btw
-
sethsimmons
Adding `--rpc-port "18089"` instead, I'm not sure how I missed that :/
-
sethsimmons
To p2pool
-
DataHoarder
no link needed I guess, due to exposing ports?
-
DataHoarder
also btw, do you know about the multiline syntax?
-
sethsimmons
Don't need to either way as they're using the same network
-
sethsimmons
DataHoarder: Not very familiar, no!
-
DataHoarder
well, sometimes they don't get ports properly exposed
-
DataHoarder
-
sethsimmons
sethsimmons: Because the Dockerfile natively exposes those ports it works without
-
DataHoarder
>-
-
DataHoarder
yes, because it exposes them, indeed
-
sethsimmons
Yeah I'm using that here but it's new to me:
-
sethsimmons
-
DataHoarder
ah yes, was looking at monerod
-
DataHoarder
define in-peers too to some limit, or so sech1 recommends
-
sethsimmons
I should migrate the monerod ones over though
-
DataHoarder
so you don't end up with too many connections if they expose their port
-
sethsimmons
DataHoarder: Wonder why, default is no-cap IIRC
-
sethsimmons
DataHoarder: Makes sense, I'll add that now
-
DataHoarder
but you can end with too many and hit fdlimit
-
sethsimmons
-
DataHoarder
-
sethsimmons
DataHoarder: Yeah, would be very nice to have :)
-
DataHoarder
you can already get around it without hardcoding though, but it is suboptimal
-
sudo_ki[m]
Why would someone want to connect/listen to a p2p stratumserver?
-
sudo_ki[m]
I wonder if anyone has noticed alien connections
-
sech1
Port scans maybe
-
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?
-
sech1
if they send invalid data they're banned
-
sudo_ki[m]
So if random clients connected, there's nothing to really worry about
-
pauliouk
if you're lucky, they might even mine a little for you