Bitcoin Forum
December 03, 2016, 11:57:21 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 [375] 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029194 times)
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 11:03:39 PM
 #7481

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

So should I block port 9333 for now until the issue is fixed?

1480809441
Hero Member
*
Offline Offline

Posts: 1480809441

View Profile Personal Message (Offline)

Ignore
1480809441
Reply with quote  #2

1480809441
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480809441
Hero Member
*
Offline Offline

Posts: 1480809441

View Profile Personal Message (Offline)

Ignore
1480809441
Reply with quote  #2

1480809441
Report to moderator
1480809441
Hero Member
*
Offline Offline

Posts: 1480809441

View Profile Personal Message (Offline)

Ignore
1480809441
Reply with quote  #2

1480809441
Report to moderator
clown
Member
**
Offline Offline

Activity: 70


View Profile
January 19, 2014, 11:04:18 PM
 #7482

I just remembered the name.  Was p2pmining. 

https://bitcointalk.org/index.php?topic=66202.0

There wasn't any risk to the pool operator, to my knowledge.  The basic principle was the subpool had it's own share chain (or equiv - could manage with a properly designed database) to track the p2pmining users.  Each share was also submitted to the real chain under the p2pmining address.  When a payout occurred, it was divided among the users in the subpool based on their piece of the subchain.  This also allowed merged mining to occur at a sub pool level, instead of basically solo, which is what p2pool is now.

The downside, of course, was it was a mini centralized pool, subject to possible pool operator abuse and hacking.  Hacking is what brought it down..

He's serving diff 1 shares though. No vardiff, how does his server not get spammed to death?

My Dogecoin mining pool. 0% fee, proxypool into p2pool network
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
January 19, 2014, 11:08:32 PM
 #7483

I just remembered the name.  Was p2pmining. 

https://bitcointalk.org/index.php?topic=66202.0

There wasn't any risk to the pool operator, to my knowledge.  The basic principle was the subpool had it's own share chain (or equiv - could manage with a properly designed database) to track the p2pmining users.  Each share was also submitted to the real chain under the p2pmining address.  When a payout occurred, it was divided among the users in the subpool based on their piece of the subchain.  This also allowed merged mining to occur at a sub pool level, instead of basically solo, which is what p2pool is now.

The downside, of course, was it was a mini centralized pool, subject to possible pool operator abuse and hacking.  Hacking is what brought it down..

He's serving diff 1 shares though. No vardiff, how does his server not get spammed to death?

Back then large miners were < 100 GH/s.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
oldbushie
Member
**
Offline Offline

Activity: 94


View Profile
January 19, 2014, 11:15:10 PM
 #7484

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.
Thanks, giving it a try now.

smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 11:19:52 PM
 #7485

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that? Smiley
bitpop
Legendary
*
Offline Offline

Activity: 1918


https://keybase.io/bitpop


View Profile WWW
January 19, 2014, 11:23:56 PM
 #7486

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that? Smiley

You need to compile it from the latest commit

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 11:33:17 PM
 #7487

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Sorry when you say "try the most recent commit" what exactly do you mean by that?

Update the software or something else?

Something else on github

Can you be any more vague than that? Smiley

You need to compile it from the latest commit

Where do I find the info on doing this?
ikolubr
Newbie
*
Offline Offline

Activity: 13


View Profile
January 19, 2014, 11:33:37 PM
 #7488

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.
bkminer
Full Member
***
Offline Offline

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 19, 2014, 11:38:04 PM
 #7489

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 19, 2014, 11:46:51 PM
 #7490

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart



Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help! Smiley
bitpop
Legendary
*
Offline Offline

Activity: 1918


https://keybase.io/bitpop


View Profile WWW
January 19, 2014, 11:57:11 PM
 #7491

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart



Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help! Smiley

Wait so you know how to do that but my mention of running last commit didn't trigger this?

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
bkminer
Full Member
***
Offline Offline

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 20, 2014, 12:05:07 AM
 #7492

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick
bitpop
Legendary
*
Offline Offline

Activity: 1918


https://keybase.io/bitpop


View Profile WWW
January 20, 2014, 12:06:53 AM
 #7493

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

Give it time to block them

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 20, 2014, 12:13:40 AM
 #7494

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart



Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help! Smiley

Wait so you know how to do that but my mention of running last commit didn't trigger this?

Obviously you haven't been paying attention in the other thread on setting up P2Pool? I have only had my pool setup for uhm, close to 24 hours now. With the questions I was asking its obvious I didn't know much about linux otherwise I would have been done ages ago. Thanks to the guys over at the openSUSE forum who did a great job at translating the ubuntu mumbo jumbo stuff into openSUSE. Smiley

It would have been more simpler if you had said.. run git pull on p2pool instead of saying it the other way. LOL

There is no need to complicate your life and the life of others. Smiley

Thanks,
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 20, 2014, 12:16:34 AM
 #7495

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.
bkminer
Full Member
***
Offline Offline

Activity: 216

Don't let the nam-shub in your operating system.


View Profile
January 20, 2014, 12:59:26 AM
 #7496


It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

I should look at the code but I thought it would block the peer that sends bad shares before it went into it's loop that kills everything.  I have a monit script setup to restart it when it starts to act up. Unfortunately Apple AirPorts cut the connection for a minute or so when changing that level of settings.  I could just add an iptables rule..

smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 20, 2014, 01:56:10 AM
 #7497


It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

I should look at the code but I thought it would block the peer that sends bad shares before it went into it's loop that kills everything.  I have a monit script setup to restart it when it starts to act up. Unfortunately Apple AirPorts cut the connection for a minute or so when changing that level of settings.  I could just add an iptables rule..



Sounds like something I should find for openSUSE; the script that restarts it when something acts up.
smoothrunnings
Hero Member
*****
Offline Offline

Activity: 546


View Profile
January 20, 2014, 02:56:21 AM
 #7498

There is currently a problem and a fix is being worked on. For now, refusing incoming connections (--max-conns 0) is a temporary solution. Expect more news in the next half hour.

Just had it happen to me after applying the fix a couple of hours ago. I have added --max-conns 0 to my startup until a more perminate fix is found.

Thanks,
oldbushie
Member
**
Offline Offline

Activity: 94


View Profile
January 20, 2014, 03:16:51 AM
 #7499

Yeah I had another drop 2 hours after I pulled from git.

ikolubr
Newbie
*
Offline Offline

Activity: 13


View Profile
January 20, 2014, 04:09:15 AM
 #7500

Here is working fine so far!  Cheesy
Pages: « 1 ... 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 [375] 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!