Author

Topic: New P2Pool Testing *UPDATED* (Read 1719 times)

full member
Activity: 168
Merit: 100
November 09, 2014, 08:27:38 AM
#5
I have modified the DDNS method and would like to try it again.

This time use stratum+luckypyrate.noip.me:9332
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
November 06, 2014, 09:32:37 AM
#4
I don't know if anyone out there would be interested in helping me out, but I have a new P2Pool node I put up in the New Orleans area and I just need to see if it is accessible remotely.  I have to use DDNS since Cox does not allow for residential static IPs. 

If anyone is interested in pointing a miner in my direction the information is as follows and I greatly appreciate your assistance.

host:  stratum+tcp://luckypyrate.noip.me.

You shouldn't need to append it with port 9332 as the DDNS is already pointing to it. 

Thanks for your help and hopefully we can get this opened up to the public tonight.

Yes, it's accessible remotely.  I can see you've got about 3TH/s on your local node, and are running the stock p2pool front end.  Tracing shows the IP of 8.23.224.90, which is Level 3 communications and Vitalwerks Internet Solutions.  Pinging from my home in South NJ results in an average 109ms trip.

I know the interface is accessible, I was asking if anyone could actually mine with it. 
As of right now the pool shows as dead if I use the URL you provided in your original post.  The interface, however, is still remotely accessible.
full member
Activity: 168
Merit: 100
November 05, 2014, 08:02:47 PM
#3
I don't know if anyone out there would be interested in helping me out, but I have a new P2Pool node I put up in the New Orleans area and I just need to see if it is accessible remotely.  I have to use DDNS since Cox does not allow for residential static IPs. 

If anyone is interested in pointing a miner in my direction the information is as follows and I greatly appreciate your assistance.

host:  stratum+tcp://luckypyrate.noip.me.

You shouldn't need to append it with port 9332 as the DDNS is already pointing to it. 

Thanks for your help and hopefully we can get this opened up to the public tonight.

Yes, it's accessible remotely.  I can see you've got about 3TH/s on your local node, and are running the stock p2pool front end.  Tracing shows the IP of 8.23.224.90, which is Level 3 communications and Vitalwerks Internet Solutions.  Pinging from my home in South NJ results in an average 109ms trip.

I know the interface is accessible, I was asking if anyone could actually mine with it. 
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
November 05, 2014, 03:19:55 PM
#2
I don't know if anyone out there would be interested in helping me out, but I have a new P2Pool node I put up in the New Orleans area and I just need to see if it is accessible remotely.  I have to use DDNS since Cox does not allow for residential static IPs. 

If anyone is interested in pointing a miner in my direction the information is as follows and I greatly appreciate your assistance.

host:  stratum+tcp://luckypyrate.noip.me.

You shouldn't need to append it with port 9332 as the DDNS is already pointing to it. 

Thanks for your help and hopefully we can get this opened up to the public tonight.

Yes, it's accessible remotely.  I can see you've got about 3TH/s on your local node, and are running the stock p2pool front end.  Tracing shows the IP of 8.23.224.90, which is Level 3 communications and Vitalwerks Internet Solutions.  Pinging from my home in South NJ results in an average 109ms trip.
full member
Activity: 168
Merit: 100
November 04, 2014, 07:39:29 PM
#1
I don't know if anyone out there would be interested in helping me out, but I have a new P2Pool node I put up in the New Orleans area and I just need to see if it is accessible remotely.  I have to use DDNS since Cox does not allow for residential static IPs.  

If anyone is interested in pointing a miner in my direction the information is as follows and I greatly appreciate your assistance.

***EDIT***
New host:  stratum+tcp://luckypyrate.noip.me:9332

You shouldn't need to append it with port 9332 as the DDNS is already pointing to it.  

Thanks for your help and hopefully we can get this opened up to the public tonight.
Jump to: