Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 728. (Read 2591916 times)

member
Activity: 88
Merit: 10
Gliding...
I forward the port and use ddns

Many thanks, but can you explain how to do this in windows 7?

Panda Mouse.

It should be as simple as forwarding port 9332 through your router to your computer and then going to http://YOUR.IP.ADDR.ESS:9332/static from outside.

Yes, thanks a lot, greetings from Poland.

Panda Mouse.
legendary
Activity: 2912
Merit: 1060
Or get a ddns from no-ip.com
hero member
Activity: 516
Merit: 643
I forward the port and use ddns

Many thanks, but can you explain how to do this in windows 7?

Panda Mouse.

It should be as simple as forwarding port 9332 through your router to your computer and then going to http://YOUR.IP.ADDR.ESS:9332/static from outside.
member
Activity: 88
Merit: 10
Gliding...
I forward the port and use ddns

Many thanks, but can you explain how to do this in windows 7?

Panda Mouse.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Some people suggested that a node has to be "reliable" for people to connect to it. The node is running 24/7, but the internet connection reconnects every 24 hours. Maybe this is the reason.

If the IP address changes then other nodes will see you as a new 0 minute node.  Nodes identify other nodes based on IP address.  Theoretically that could be changed but I don't think it is a pressing concern.
Hmm interesting - my IP address changes every day also.

So does this mean that new connection nodes are effectively discouraged?
If your description above is correct then they are discouraged.
I guess there's some technical details that would explain that?
donator
Activity: 1218
Merit: 1079
Gerald Davis
Some people suggested that a node has to be "reliable" for people to connect to it. The node is running 24/7, but the internet connection reconnects every 24 hours. Maybe this is the reason.

If the IP address changes then other nodes will see you as a new 0 minute node.  Nodes identify other nodes based on IP address.  Theoretically that could be changed but I don't think it is a pressing concern.
donator
Activity: 1218
Merit: 1079
Gerald Davis
Ahh.. ok no i have no static ip address and I don't even run 24/7... ;-)

static IP isn't necessary as long as your IP address is relatively stable.  Looking at the incoming peers chart it looks like >8 hours is where # of incoming peers rapidly increases.  For most users DHCP leases tend to be 14 days or longer (I have the same dynamic IP address as I did last year) so there is no need for a static IP address.

Keeping p2pool running is important.  nodes rank other nodes based on how long they have seen them.  If you are always seen as a very short lived and unstable node it is unlikely any node will ever voluntarily connect to you (as there are other better options available).  Nodes are oppertunistic (as they should be).   They seek out the best possible nodes.

Currently looking at the code it looks like longevity is the only factor is how "good" a node is.  That probably could be expanded to include things like latency, share notification (what % of shares did that node report), bad shares (nodes should verify shares before forwarding), version reported, etc.

One thing to keep in mind if that even if you don't mine 24/7 you can keep p2pool & bitcoind running 24/7 (both use minimal resources & bandwidth).

Some people suggested that a node has to be "reliable" for people to connect to it. The node is running 24/7, but the internet connection reconnects every 24 hours. Maybe this is the reason.

If the IP address changes then other nodes will see you as a new 0 minute node.  Nodes identify other nodes based on IP address.  Theoretically that could be changed but I don't think it is a pressing concern.  One way I could see that changing is by nodes identifying themselves by a public key.  This would allow nodes to retain information on other nodes even when IP address changes.

A simpler patch would be to have the node list include dns entries.  Then using dyndns one could always be the same url despite IP address changing.  Personally I like the public key method better (prevents the need for frequent dns lookups) but using dns is much simpler.
donator
Activity: 1218
Merit: 1079
Gerald Davis
Looks like the people who where not upgraded got kicked from the network.

Well technically they are on an incompatible and minority fork.  That fork can continue to exist forever but hopefully they notice the 70%+ (from their point of view) drop in hashing power and take the time to actually upgrade their p2pool once a month or so.
legendary
Activity: 1064
Merit: 1000
great, using it from now on!
legendary
Activity: 2912
Merit: 1060
I forward the port and use ddns
member
Activity: 88
Merit: 10
Gliding...

How you put yours data (graphs) to outside server?
I have it only locally Sad

Panda Mouse
newbie
Activity: 62
Merit: 0
Ahh.. ok no i have no static ip address and I don't even run 24/7... ;-)
member
Activity: 88
Merit: 10
Gliding...
I have a question: I forwarded TCP and UDP on port 9333 from my router to my pc, but I always get:  
Code:
Peers: 10 (0 incoming)
Why doesn't it connect to more nodes?


I think the network is ok.
Here is an example of how after program re-installation new connections were coming slowly.
This is my last 24 hours.



Do you have a static IP address?

Panda Mouse.
legendary
Activity: 2126
Merit: 1001
May not be properly seeing your external address, also takes a day to get conncetions.

I  forwarded port 9333, the p2pool instance is reachable from outside, but noone ever connected to it (except one for testing). This is around one, two weeks now.
Some people suggested that a node has to be "reliable" for people to connect to it. The node is running 24/7, but the internet connection reconnects every 24 hours. Maybe this is the reason.

Ente
legendary
Activity: 2912
Merit: 1060
May not be properly seeing your external address, also takes a day to get conncetions.
newbie
Activity: 62
Merit: 0
why does the hashrate drop? Why are people leaving? We have more luck than ever!


Quote
You must upgrade to P2Pool 0.10.3 or greater before April 1st (or March 27th for Litecoin) and install either Bitcoin 0.6.0 or the 0.5.4 backport to ensure compatibility with BIP16

Looks like the people who where not upgraded got kicked from the network.
ah ok.. I use p2pool from git, so I didn't notice ;-)

I have a question: I forwarded TCP and UDP on port 9333 from my router to my pc, but I always get:  
Code:
Peers: 10 (0 incoming)
Why doesn't it connect to more nodes?
hero member
Activity: 560
Merit: 500
why does the hashrate drop? Why are people leaving? We have more luck than ever!


Quote
You must upgrade to P2Pool 0.10.3 or greater before April 1st (or March 27th for Litecoin) and install either Bitcoin 0.6.0 or the 0.5.4 backport to ensure compatibility with BIP16

Looks like the people who where not upgraded got kicked from the network.
newbie
Activity: 62
Merit: 0
why does the hashrate drop? Why are people leaving? We have more luck than ever!
hero member
Activity: 682
Merit: 500
Holy crap @ the day we're having. Cheesy

Shh...

Don't scare the luck away.  Wink


Forget I ever said anything. Wink

Jump to: