Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 569. (Read 2591920 times)
April 12, 2013, 12:32:01 PM
Nicely
April 12, 2013, 12:28:50 PM
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?
April 12, 2013, 12:26:12 PM
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 What's the problem!?
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
April 12, 2013, 12:19:48 PM
Mmmhmmmm Keep those blocks coming
April 12, 2013, 10:20:12 AM
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 What's the problem!?
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
April 12, 2013, 10:17:24 AM
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 What's the problem!?
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!
April 12, 2013, 10:03:14 AM
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 What's the problem!?
Code:
Note that blocks may have been orphaned from the P2Pool chain and so not be here.
edit: post #500
April 12, 2013, 09:26:01 AM
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!?
What's the problem!?
April 12, 2013, 05:46:00 AM
This one looks likely:
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.Quote
-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)
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.
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.
April 12, 2013, 03:30:43 AM
Dear P2pool TRC miners:
PLS update it or mine on another node.
You all are minig for broken TRC fork.
It is TRC block 103xxx not 100xxx
Code:
1Cs5ZKBExgufTx2L6Rg5VNSuV7y4JguAHh
1Px7RGTTWPgSDfwBHC8iAGKH8orCF8wGFA
12J4TH1u9MBhbArWVwoGZBdASSP5EtnYMw
13jAyKvLj6W6LbyJjVwsLb4ZxFei7bVoH8
1AbSWqLYpywnbqdhrQ9UYpRK2dq6fSGmg6
Node that are you mining for have OUTDATED TRC daemon!1Px7RGTTWPgSDfwBHC8iAGKH8orCF8wGFA
12J4TH1u9MBhbArWVwoGZBdASSP5EtnYMw
13jAyKvLj6W6LbyJjVwsLb4ZxFei7bVoH8
1AbSWqLYpywnbqdhrQ9UYpRK2dq6fSGmg6
PLS update it or mine on another node.
You all are minig for broken TRC fork.
It is TRC block 103xxx not 100xxx
April 12, 2013, 02:06:04 AM
This one looks likely:
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.Quote
-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)
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.
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?
April 11, 2013, 11:16:08 PM
This one looks likely:
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. Quote
-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)
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.
April 11, 2013, 03:58:17 PM
This one looks likely:
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.
Quote
-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)
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.
April 11, 2013, 03:39:18 PM
Is there any way to add a list of black/whitelisted IPs that can access the p2pool web interface? I know you can do it with a firewall, but i'm asking about native support. Is there any compromising info listed on that page were an untrusted party to have access to the UI?
There's not much. Arguably, it displays your public key which could be a way to tie your account to your IP and other activities. It should really only bind to localhost by default. Then, optionally, it should have a whitelist and/or require authentication. Also, it would be a good idea if it had yet another step required if it was being accessed from a public IP rather than a private one.
April 11, 2013, 03:18:43 PM
Is there any way to add a list of black/whitelisted IPs that can access the p2pool web interface? I know you can do it with a firewall, but i'm asking about native support. Is there any compromising info listed on that page were an untrusted party to have access to the UI?
There's not much. Arguably, it displays your public key which could be a way to tie your account to your IP and other activities. It should really only bind to localhost by default. Then, optionally, it should have a whitelist and/or require authentication. Also, it would be a good idea if it had yet another step required if it was being accessed from a public IP rather than a private one.
April 11, 2013, 01:57:56 PM
Is there any way to add a list of black/whitelisted IPs that can access the p2pool web interface? I know you can do it with a firewall, but i'm asking about native support. Is there any compromising info listed on that page were an untrusted party to have access to the UI?
April 11, 2013, 07:22:44 AM
HELP:
I was a previous user of p2pool with no problems for months; i used it on bitcoin as well as litecoin and terracoin;
I did afresh re-install of windows re-downloaded and set-up my coins and p2pool etc.
P2pool launches with no error and connects to the network.
When i launch my miner to connect it connects and finds the p2pool network but results in this error and no shares are submitted. please help!!!
Thank you for the help!!
[/quote
Using the latest release will fix this.
I was a previous user of p2pool with no problems for months; i used it on bitcoin as well as litecoin and terracoin;
I did afresh re-install of windows re-downloaded and set-up my coins and p2pool etc.
P2pool launches with no error and connects to the network.
When i launch my miner to connect it connects and finds the p2pool network but results in this error and no shares are submitted. please help!!!
Thank you for the help!!
[/quote
Using the latest release will fix this.
April 11, 2013, 07:07:32 AM
hey guys, just started mining on the litefcoin p2pool and its great!
question though, I'm trying to connect to 127.0.0.1:9332/something, I login and it spits out this json error.
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
thats the only thing that shows up on the screen, am I missing something?
The litecoin p2pool network listens on port 9327, not 9332.question though, I'm trying to connect to 127.0.0.1:9332/something, I login and it spits out this json error.
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
thats the only thing that shows up on the screen, am I missing something?
-- Smoov
April 11, 2013, 06:19:31 AM
hey guys, just started mining on the litefcoin p2pool and its great!
question though, I'm trying to connect to 127.0.0.1:9332/something, I login and it spits out this json error.
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
thats the only thing that shows up on the screen, am I missing something?
question though, I'm trying to connect to 127.0.0.1:9332/something, I login and it spits out this json error.
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}
thats the only thing that shows up on the screen, am I missing something?
April 11, 2013, 05:34:54 AM
Dear P2pool TRC miners, PLEASE UPADTE TRC CLINET up to 30 or current GIT!
Network is forked, current proper number of blocks is over 102`000!
Network is forked, current proper number of blocks is over 102`000!
Jump to: