[ANN] The First Litecoin PPS Pool (litecoinpool.org) - page 67.

splat44

sr. member

Activity: 384

Merit: 250

Quote from: pekv2 on December 05, 2012, 04:03:20 PM

Quote from: pooler on December 05, 2012, 07:49:07 AM

Quote from: splat44 on December 05, 2012, 06:06:15 AM

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

This &

https://bitcointalksearch.org/topic/tutorial-solo-mining-litecoins-guide-windows-83371

+

For offline use.
[TUTORIAL] Solo Mining Litecoins Guide--Windows! Offline PDF

Thank and I certainly take note of this!

I also notice mining ltc value has increased and difficulties decreased, Is this good and does it means we earn more?

Regards

pekv2

hero member

Activity: 770

Merit: 502

Quote from: pooler on December 05, 2012, 07:49:07 AM

Quote from: splat44 on December 05, 2012, 06:06:15 AM

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

This &

https://bitcointalksearch.org/topic/tutorial-solo-mining-litecoins-guide-windows-83371

+

For offline use.
[TUTORIAL] Solo Mining Litecoins Guide--Windows! Offline PDF

pooler

hero member

Activity: 838

Merit: 507

Quote from: splat44 on December 05, 2012, 06:06:15 AM

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

To mine solo just tell cpuminer to connect to your local Litecoin daemon, using the local IP of the machine and the RPC username and password defined in your litecoin.conf. The default port is 9332.
If you want to set up failover pools in cpuminer, see this thread.

Quote from: splat44 on December 05, 2012, 06:06:15 AM

Oh yes, about public key, what this all about?

At present it's only used for the avatar, you don't need to worry about it.

splat44

sr. member

Activity: 384

Merit: 250

I'm glad to server is up and running!

Just in case of further DDos attack, how we set up for solo mining using cpuminer?

I especially want to know the string and where to enter it as command line (while using server:port and userpass)

Oh yes, about public key, what this all about?
Can use we use this in cpuminer and if so, then what the string?

Regards

Dagger75

full member

Activity: 156

Merit: 100

Thanks Pooler, was wondering what was up today!! Cry

Simran

hero member

Activity: 714

Merit: 500

Quote from: pooler on December 02, 2012, 02:54:56 PM

DDoS attack is in progress. Sorry for the inconvenience.

Don't worry, pooler!

pooler

hero member

Activity: 838

Merit: 507

DDoS attack is in progress. Sorry for the inconvenience.

burnside

legendary

Activity: 1106

Merit: 1004

Lead Blockchain Developer

Quote from: wndrbr3d on October 19, 2012, 07:14:49 PM

Quote from: burnside on October 19, 2012, 05:53:51 PM

Quote from: wndrbr3d on October 19, 2012, 04:25:59 PM

Quote from: pooler on October 19, 2012, 12:56:41 PM

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance. Two problems:

1) Cost. an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

Right, but if you used DNS load balancing you could just map a new IP and update your A-Record.

I mean, unless a DDoS attack does a DNS on each request, I imagine you would suffer minimal downtime. I'm making assumptions though, I've personally never launched a DDoS myself.

DDoS attacks primarily originate from compromised machines serving a botnet. Thus when a DDoS attack is pointed at a domain name, the attack follows the domain name just as fast as your dns changes reach the compromised machines.

wndrbr3d

hero member

Activity: 914

Merit: 500

Quote from: burnside on October 19, 2012, 05:53:51 PM

Quote from: wndrbr3d on October 19, 2012, 04:25:59 PM

Quote from: pooler on October 19, 2012, 12:56:41 PM

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance. Two problems:

1) Cost. an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

Right, but if you used DNS load balancing you could just map a new IP and update your A-Record.

I mean, unless a DDoS attack does a DNS on each request, I imagine you would suffer minimal downtime. I'm making assumptions though, I've personally never launched a DDoS myself.

burnside

legendary

Activity: 1106

Merit: 1004

Lead Blockchain Developer

Quote from: wndrbr3d on October 19, 2012, 04:25:59 PM

Quote from: pooler on October 19, 2012, 12:56:41 PM

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

I don't want to get too far off topic, this isn't my pool thread.

I have thought about splitting the web services from the poolserver instance. Two problems:

1) Cost. an LTC pool doesn't make money and even my full dedicated server has load issues periodically.
2) The attack we were seeing today was icmp flood + http flood + pushpool port flood, so having separate servers wouldn't have helped much.

Cheers.

Nicksasa

sr. member

Activity: 288

Merit: 250

Quote from: wndrbr3d on October 19, 2012, 04:25:59 PM

Quote from: pooler on October 19, 2012, 12:56:41 PM

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

You'd probably spend a lot on bandwidth ... I've considered this myself before.

wndrbr3d

hero member

Activity: 914

Merit: 500

Quote from: pooler on October 19, 2012, 12:56:41 PM

Sorry guys, pool is currently down. Yes, DDoS once again.

Have you thought of using DNS load balancing and apache reverse proxies?

I thought if someone were to do that using say, Amazon micro instances to host apache, you could make your pool rather resilient to DDoS as it would isolate the nodes from the actual pool instances.

burnside

legendary

Activity: 1106

Merit: 1004

Lead Blockchain Developer

Quote from: powersync on October 19, 2012, 01:17:10 PM

Burnside is getting hit at the same time.

PS

Yeah, not fun. Working on shifting the traffic to a larger DDoS setup.

powersync

member

Activity: 77

Merit: 10

Burnside is getting hit at the same time.

PS

PandaMiner

sr. member

Activity: 322

Merit: 250

Well, this time I don't mind, it means that the total network has has gone down, and it may result in a lower difficulty.

3 days ago I switched back to BTC mining for that reason.

pooler

hero member

Activity: 838

Merit: 507

Sorry guys, pool is currently down. Yes, DDoS once again.

DiCE1904

legendary

Activity: 1118

Merit: 1002

Quote from: mufa23 on October 12, 2012, 06:01:29 PM

I've been trying to find a good pool. I like this one, but it looks like you aren't accepting more miners. I'll shoot you an email.

In the mean time, does anyone have a suggestion for another pool?

I have been using http://ltc.r00t3d.com:9327/static/

mufa23

legendary

Activity: 1022

Merit: 1001

I'd fight Gandhi.

I've been trying to find a good pool. I like this one, but it looks like you aren't accepting more miners. I'll shoot you an email.

In the mean time, does anyone have a suggestion for another pool?

meebs

hero member

Activity: 616

Merit: 500

Quote from: pekv2 on October 08, 2012, 01:59:04 PM

Quote from: meebs on October 03, 2012, 05:06:02 PM

Looks like the pool keeps going down for a few minutes at a time..

anyone else having this issue?

Seems like its happening all this week. Becoming very annoying.

even more annoying since I am unsure how to setup a backup pool in reaper (i use a 7950, so cgminer is not a viable option).

pekv2

hero member

Activity: 770

Merit: 502

Quote from: meebs on October 03, 2012, 05:06:02 PM

Looks like the pool keeps going down for a few minutes at a time..

anyone else having this issue?

Seems like its happening all this week. Becoming very annoying.

Topic: [ANN] The First Litecoin PPS Pool (litecoinpool.org) - page 67. (Read 226967 times)