P2pool peers 8 out 0 in | Bitcointalksearch.org

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: Acejam on June 26, 2014, 05:49:57 PM

Quote from: KyrosKrane on June 26, 2014, 02:29:00 PM

Do NOT open port 8332 unless you intentionally want to allow RPC commands to your bitcoin daemon! That means that an outsider could send a command to empty all coins on the wallet and send them to himself. Yes, I know you can mitigate this by limiting the allowed IPs in the config file, but my point is, why expose yourself to unnecessary risk? Port 8333 should be open so bitcoind can connect to other nodes.

For p2pool, open port 9332 if you want to see the Web interface or connect miners to your pool from outside your firewall. If you don't want either, you can safely keep it closed. Open port 9333 so p2pool can connect to other p2pool nodes. This port should generally be open.

For other coins, again, you want to keep the RPC port closed, but the other, generic port open. I don't know which of those ports are which from your list; check your coins' documentation.

rpcallowip=192.168.1.*
OR
rpcallowip=127.0.0.1

Yes, you can limit the allowed IP addresses; however, do so in conjunction with keeping closed port 8332 (and any other coin daemon's RPC port) to the outside.

Acejam

full member

Activity: 124

Merit: 251

Quote from: KyrosKrane on June 26, 2014, 02:29:00 PM

Do NOT open port 8332 unless you intentionally want to allow RPC commands to your bitcoin daemon! That means that an outsider could send a command to empty all coins on the wallet and send them to himself. Yes, I know you can mitigate this by limiting the allowed IPs in the config file, but my point is, why expose yourself to unnecessary risk? Port 8333 should be open so bitcoind can connect to other nodes.

For p2pool, open port 9332 if you want to see the Web interface or connect miners to your pool from outside your firewall. If you don't want either, you can safely keep it closed. Open port 9333 so p2pool can connect to other p2pool nodes. This port should generally be open.

For other coins, again, you want to keep the RPC port closed, but the other, generic port open. I don't know which of those ports are which from your list; check your coins' documentation.

rpcallowip=192.168.1.*
OR
rpcallowip=127.0.0.1

KyrosKrane

sr. member

Activity: 295

Merit: 250

Quote from: webiky on June 26, 2014, 01:59:15 PM

Thank you for your answer Wink

I also noticed that some connetions are trying to go throught firewall, so I allowed them.
I don´t know which port open made that, but it almost immediately gave me 1 IN peer for BTC/LTC/VTC p2pool.

These are open ports:
5889, 8332, 8333, 9171, 9172, 9327, 9328, 9332, 9333, 9338, 9346, 10333

Do NOT open port 8332 unless you intentionally want to allow RPC commands to your bitcoin daemon! That means that an outsider could send a command to empty all coins on the wallet and send them to himself. Yes, I know you can mitigate this by limiting the allowed IPs in the config file, but my point is, why expose yourself to unnecessary risk? Port 8333 should be open so bitcoind can connect to other nodes.

For p2pool, open port 9332 if you want to see the Web interface or connect miners to your pool from outside your firewall. If you don't want either, you can safely keep it closed. Open port 9333 so p2pool can connect to other p2pool nodes. This port should generally be open.

For other coins, again, you want to keep the RPC port closed, but the other, generic port open. I don't know which of those ports are which from your list; check your coins' documentation.

webiky

newbie

Activity: 17

Merit: 0

Thank you for your answer Wink

I also noticed that some connetions are trying to go throught firewall, so I allowed them.
I don´t know which port open made that, but it almost immediately gave me 1 IN peer for BTC/LTC/VTC p2pool.

These are open ports:
5889, 8332, 8333, 9171, 9172, 9327, 9328, 9332, 9333, 9338, 9346, 10333

Acejam

full member

Activity: 124

Merit: 251

Quote from: webiky on June 26, 2014, 04:31:24 AM

I tried to find out something more about this problem, but I couldn´t.

My problem is, that I don´t get any IN connections.

http://84.42.144.19:9332/static/

Version: 13.4
Pool rate: 292TH/s (17% DOA+orphan) Share difficulty: 1280000
Peers: 8 out, 0 in
Local rate: 8.85GH/s (5.1% DOA) Expected time to share: 7.2 days
Shares: 0 total (0 orphaned, 0 dead) Efficiency: Huh

I use P2Pool release 13.4 for Windows (https://bitcointalksearch.org/topic/1500-th-p2pool-decentralized-dos-resistant-hop-proof-pool-18313)
I have open all ports OUT, and these ports IN: 8333,9332,9333

Thank you in advance for any help.

As of right now, your node uptime is 25 minutes. You're connected to 7 other nodes. Other P2Pool nodes and clients out there are simply connected to other nodes. The longer your node is up, the more incoming connections you will gain. However, having zero incoming connections isn't a bad thing, so don't treat it like one.

I have P2Pool nodes in my cluster than have been up for 60+ days and have 40+ incoming connections. They also use noticeably more bandwidth than the ones that only have 5 or 10 connections.