[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[Richy_T]

This one looks likely:

-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327, terracoin:9322)

Use localhost:9332 but make sure not to lock your miner out. If you are on Windows, you can use Windows Firewall to restrict things somewhat and on Linux, you can use iptables to do all sorts of magic.

[1714208702]

1714208702

[1714208702]

1714208702

[1714208702]

1714208702

[Searinox]

This one looks likely:

-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327, terracoin:9322)

Use localhost:9332 but make sure not to lock your miner out. If you are on Windows, you can use Windows Firewall to restrict things somewhat and on Linux, you can use iptables to do all sorts of magic.

This only changes the port and locks the UI to a specific adapter. For example, I'd like to bind it to my Hamachi IP so I can access the page through my laptop when I'm away. But I can't stop everyone else on the network from peeking.

[Richy_T]

This one looks likely:

-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327, terracoin:9322)

Use localhost:9332 but make sure not to lock your miner out. If you are on Windows, you can use Windows Firewall to restrict things somewhat and on Linux, you can use iptables to do all sorts of magic.

This only changes the port and locks the UI to a specific adapter. For example, I'd like to bind it to my Hamachi IP so I can access the page through my laptop when I'm away. But I can't stop everyone else on the network from peeking.

If you bind to localhost, you can use SSHD or similar to provide access.

If I knew more Python, I'd probably be up for putting basic authentication in myself. How are the maintainers about accepting patches with this one?

[rav3n_pl]

Dear P2pool TRC miners:

Code:

1Cs5ZKBExgufTx2L6Rg5VNSuV7y4JguAHh
1Px7RGTTWPgSDfwBHC8iAGKH8orCF8wGFA
12J4TH1u9MBhbArWVwoGZBdASSP5EtnYMw
13jAyKvLj6W6LbyJjVwsLb4ZxFei7bVoH8
1AbSWqLYpywnbqdhrQ9UYpRK2dq6fSGmg6

Node that are you mining for have OUTDATED TRC daemon!
PLS update it or mine on another node.
You all are minig for broken TRC fork.
It is TRC block 103xxx not 100xxx

[twmz]

This one looks likely:

-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327, terracoin:9322)

Use localhost:9332 but make sure not to lock your miner out. If you are on Windows, you can use Windows Firewall to restrict things somewhat and on Linux, you can use iptables to do all sorts of magic.

This only changes the port and locks the UI to a specific adapter. For example, I'd like to bind it to my Hamachi IP so I can access the page through my laptop when I'm away. But I can't stop everyone else on the network from peeking.

Embrace you're operating system's built-in ability to do this (Windows Firewall, Linux iptables, etc).  You can not do what you want to do with just the p2pool software by itself as that feature doesn't exist in the software today.

[Shevek]

1 hour after block 230983 is solved my node does not report it (you know: http://127.0.0.1:9332/static/)

What's the problem!?

[rav3n_pl]

1 hour after block 230983 is solved my node does not report it (you know: http://127.0.0.1:9332/static/)

What's the problem!?

No problem, it was solved by orphaned share

Code:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.

edit: post #500

[Shevek]

1 hour after block 230983 is solved my node does not report it (you know: http://127.0.0.1:9332/static/)

What's the problem!?

No problem, it was solved by orphaned share

Code:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.

Opss... so this is what it means.

Thanks!

[gdsl]

1 hour after block 230983 is solved my node does not report it (you know: http://127.0.0.1:9332/static/)

What's the problem!?

No problem, it was solved by orphaned share

Code:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.

edit: post #500

Uhm. Block 230653 was orphaned, not 230983

[Mogumodz]

Mmmhmmmm Keep those blocks coming 

[Krak]

1 hour after block 230983 is solved my node does not report it (you know: http://127.0.0.1:9332/static/)

What's the problem!?

No problem, it was solved by orphaned share

Code:

Note that blocks may have been orphaned from the P2Pool chain and so not be here.

edit: post #500

Uhm. Block 230653 was orphaned, not 230983

The share that found the block was orphaned, not the block itself.

[Shevek]

Mmmhmmmm Keep those blocks coming 

This ja appears in my stats! :-) (and in my wallet... of course!)

Now one question: why does blockchain.info credit deepbit as solver!? Is deepbit now a node of p2pool?

[Richy_T]

Nicely

[Richy_T]

Hmmm...

13qnEgPTxJW6mm88dLpnHXZyryN5EXBciq (Richy_T ) 0.03825833 BTC

Received 0.01253471 In wallet. What's up with that?

[lbr]

How to change WebInterface(stats) listening port but leave workers port the same?

[Searinox]

This one looks likely:

-w PORT or ADDR:PORT, --worker-port PORT or ADDR:PORT
                        listen on PORT on interface with ADDR for RPC
                        connections from miners (default: all interfaces,
                        bitcoin:9332, litecoin:9327, terracoin:9322)

Use localhost:9332 but make sure not to lock your miner out. If you are on Windows, you can use Windows Firewall to restrict things somewhat and on Linux, you can use iptables to do all sorts of magic.

This only changes the port and locks the UI to a specific adapter. For example, I'd like to bind it to my Hamachi IP so I can access the page through my laptop when I'm away. But I can't stop everyone else on the network from peeking.

That worked. Now the UI is only accessible from the PC running it. It's a partial solution. Thanks.

Another problem popped up when I did this. I killed p2pool with the miner still running and restarted it with the new command line. As p2pool came back online, it reported that 90%+ of the hashes were DOA. I let thing run for a little so that bfgminer would have a chance to resync but the DOAs remained high. Does bfgminer eventually resync with p2pool after it's done whatever work it may have been doing or do I have to force reset bfgminer? I mean while this isn't difficult for me, it would be problematic on an automated setup that goes through all sorts of ups and downs over months of running.

[gdsl]

The share that found the block was orphaned, not the block itself.

Aha. I see.

[hippiex]

Hi All,

   Im trying to set p2pool server but it seems that it is not working at all....  Shares and Payout always set to 0.
   Am i missing something ? Ideas?

p2pool log:

013-04-14 08:40:17.904862 > ########################################
2013-04-14 08:40:17.905458 > >>> Warning: (from bitcoind) Warning: this version is obsolete, upgrade required
2013-04-14 08:40:17.905888 > ########################################
2013-04-14 08:40:17.906335 P2Pool: 17333 shares in chain (8687 verified/17334 total) Peers: 6 (0 incoming)
2013-04-14 08:40:17.906670  Local: 103kH/s in last 4.6 minutes Local dead on arrival: ~2.7% (1-5%) Expected time to share: 8.4 hours
2013-04-14 08:40:17.908512  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 LTC
2013-04-14 08:40:17.908934  Pool: 389MH/s Stale rate: 21.7% Expected time to block: 54.0 minutes

cgminer 1 :

cgminer version 2.11.4 - Started: [2013-04-14 08:37:54]
--------------------------------------------------------------------------------
 (5s):775.3K (avg):775.8Kh/s | A:65  R:2  HW:0  U:15.1/m  WU:30.7/m
 ST: 2  SS: 0  NB: 1  LW: 164  GF: 0  RF: 0
 Connected to 192.168.0.221 diff 3 with stratum as user 1
 Block: 122cad68baf38a83...  Diff:19.2M  Started: [08:37:53]  Best share: 543
--------------------------------------------------------------------------------
 [P]ool management [G]PU management ettings [D]isplay options [Q]uit
 GPU 0:                | 387.9K/390.4Kh/s | A:32 R:0 HW:593 U:  7.43/m I:15
 GPU 1:                | 386.9K/390.0Kh/s | A:33 R:2 HW:565 U:  7.66/m I:15
--------------------------------------------------------------------------------

[mdude77]

2013-04-14 08:40:17.905458 > >>> Warning: (from bitcoind) Warning: this version is obsolete, upgrade required

Here's your problem.

M

[hippiex]

2013-04-14 08:40:17.905458 > >>> Warning: (from bitcoind) Warning: this version is obsolete, upgrade required

Here's your problem.

M

Even if i am using it to LTC ?