Topic: 🚀🚀🚀🚀 | GorillaBucks | Custom Multipool LIVE | Social Media Network | 💵🐵💵 - page 22. (Read 133306 times)

Quote from: notabeliever on July 08, 2015, 07:55:54 PM

Yo, GorillaEx down? Or is it Paul doing updates and stuff?

Not me sorry
its under DDOS attack

Any news about Gorilla.exchange?

no the attack is still ongoing

How does one know a DDOS Attack is happening. what are the signs?

Denial of service comes in many forms, but the objectives are typically the same.

Signs of an attack are but not limited to

1) Slow loading website
2) Increased latency
3) 404 Timeouts

Ddos attacks work buy using hundreds or even thousands of computers to execute requests over and over again, eventually the server and its network are unable to cope.

Most DDoS Attacks can be filtered I say most about 95% some attacks though are much harder to filter and cause much bigger problems.

Even with DDoS Protections and our own firewalls some attacks just cant be totally filtered.

In this instance the attack profile has changed constantly no sooner do the filters start to become effective we have to go back and do it again.
In Gorilla's case, the attack profile is never ending, as soon as we start to filter the profile changes, even the NEW ips are hit as soon as there brought up.

Someone must really have a vendetta Undecided

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

Quote from: pjcltd on July 08, 2015, 03:34:08 PM

Quote from: baldpope on July 08, 2015, 10:37:47 PM

Yo, GorillaEx down? Or is it Paul doing updates and stuff?

Not me sorry
its under DDOS attack

Any news about Gorilla.exchange?

no the attack is still ongoing

How does one know a DDOS Attack is happening. what are the signs?

Denial of service comes in many forms, but the objectives are typically the same.

Signs of an attack are but not limited to

1) Slow loading website
2) Increased latency
3) 404 Timeouts

Ddos attacks work buy using hundreds or even thousands of computers to execute requests over and over again, eventually the server and its network are unable to cope.

Most DDoS Attacks can be filtered I say most about 95% some attacks though are much harder to filter and cause much bigger problems.

Even with DDoS Protections and our own firewalls some attacks just cant be totally filtered.

In this instance the attack profile has changed constantly no sooner do the filters start to become effective we have to go back and do it again.
In Gorilla's case, the attack profile is never ending, as soon as we start to filter the profile changes, even the NEW ips are hit as soon as there brought up.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: MoreBloodWine on July 08, 2015, 10:34:40 PM

Quote from: baldpope on July 08, 2015, 10:20:44 PM

Quote from: MoreBloodWine on July 08, 2015, 10:09:03 PM

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Ran from the cmd prompt so I can test easily.

instead of 127.0.0.1 try using 'localhost'

so http://user:pass@localhost:3333

also - is port 3333 what the service is listening on?

No, its custom port set in conf.

Trying now.

Nope, same errors even with localhost set.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

wait - is your json statement correct? it's complaing about not being able to connect on each of those fields - 1.0, id, etc. i don't know what you're trying to do, but it doesn't look like the json is good.

I didn't write it... and for further explanation.... read the quote of my post you originally quoted as it says what the end game is.

baldpope

full member

Activity: 144

Merit: 100

Quote from: MoreBloodWine on July 08, 2015, 10:34:40 PM

Quote from: baldpope on July 08, 2015, 10:20:44 PM

Quote from: MoreBloodWine on July 08, 2015, 10:09:03 PM

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Ran from the cmd prompt so I can test easily.

instead of 127.0.0.1 try using 'localhost'

so http://user:pass@localhost:3333

also - is port 3333 what the service is listening on?

No, its custom port set in conf.

Trying now.

Nope, same errors even with localhost set.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

wait - is your json statement correct? it's complaing about not being able to connect on each of those fields - 1.0, id, etc. i don't know what you're trying to do, but it doesn't look like the json is good.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: baldpope on July 08, 2015, 10:20:44 PM

Quote from: MoreBloodWine on July 08, 2015, 10:09:03 PM

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Ran from the cmd prompt so I can test easily.

instead of 127.0.0.1 try using 'localhost'

so http://user:pass@localhost:3333

also - is port 3333 what the service is listening on?

No, its custom port set in conf.

Trying now.

Nope, same errors even with localhost set.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

baldpope

full member

Activity: 144

Merit: 100

Quote from: MoreBloodWine on July 08, 2015, 10:09:03 PM

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Ran from the cmd prompt so I can test easily.

instead of 127.0.0.1 try using 'localhost'

so http://user:pass@localhost:3333

also - is port 3333 what the service is listening on?

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: baldpope on July 08, 2015, 10:04:10 PM

Quote from: MoreBloodWine on July 08, 2015, 09:37:58 PM

added an rpcallowip for 127.0.0.1, ran curl command and got this back.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

would have to see the curl command to see what you requested

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Ran from the cmd prompt so I can test easily.

baldpope

full member

Activity: 144

Merit: 100

Quote from: MoreBloodWine on July 08, 2015, 09:37:58 PM

added an rpcallowip for 127.0.0.1, ran curl command and got this back.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

would have to see the curl command to see what you requested

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

added an rpcallowip for 127.0.0.1, ran curl command and got this back.

curl: (6) Could not resolve host: 1.0,
curl: (6) Could not resolve host: id
curl: (6) Could not resolve host: method
curl: (6) Could not resolve host: walletpassphrase,
curl: (6) Could not resolve host: params
curl: (3) [globbing] bad range in column 6
curl: (6) Could not resolve host: 99999,
curl: (3) [globbing] unmatched close brace/bracket in column 5
curl: (3) [globbing] unmatched close brace/bracket in column 1
curl: (6) Could not resolve host: text
{"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null}

baldpope

full member

Activity: 144

Merit: 100

Quote from: MoreBloodWine on July 08, 2015, 08:41:48 PM

Quote from: baldpope on July 08, 2015, 08:37:35 PM

Quote from: baldpope on July 08, 2015, 08:36:01 PM

Quote from: MoreBloodWine on July 08, 2015, 07:11:54 PM

Got CURL installed, seems to run ok but failing on the commands. Wana ask somethin first, does the "ip" 127.0.0.1 or would that be say the internal ip of 192.x.x.x I should be using instead ?

127.0.0.1 is the ip address for the host you're on. It's called 'localhost'. So when you see that as a limit, it means that ONLY the local host (ie the computer the application is running ) is allowed to talk to this service.

So in this case, it means that if you're running in server mode, only a request from the local PC can ask questions of the server node.

It's like they say.. 127.0.0.1 is where the heart is...

cheers,
baldpope

Conversely, if you were to put in any other address, it would mean that a remote client (not of the same machine) could talk with the server instance. Not necessarily bad, but you have to ensure your wallet is protected.

Basically the computer that will be running the CURL command is the same one the nodes on, so I would leave it as the local host address of 127.0.0.1 right ?

Also, what about an rpcallowip= in the config, wont that be needed as well ?

whatever you decide to put in for that directive will be the whitelist of clients allowed to connect to the wallet, so I'd keep it at 127.0.0.1 - but it's your call.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: baldpope on July 08, 2015, 08:37:35 PM

Quote from: baldpope on July 08, 2015, 08:36:01 PM

Quote from: MoreBloodWine on July 08, 2015, 07:11:54 PM

Got CURL installed, seems to run ok but failing on the commands. Wana ask somethin first, does the "ip" 127.0.0.1 or would that be say the internal ip of 192.x.x.x I should be using instead ?

127.0.0.1 is the ip address for the host you're on. It's called 'localhost'. So when you see that as a limit, it means that ONLY the local host (ie the computer the application is running ) is allowed to talk to this service.

So in this case, it means that if you're running in server mode, only a request from the local PC can ask questions of the server node.

It's like they say.. 127.0.0.1 is where the heart is...

cheers,
baldpope

Conversely, if you were to put in any other address, it would mean that a remote client (not of the same machine) could talk with the server instance. Not necessarily bad, but you have to ensure your wallet is protected.

Basically the computer that will be running the CURL command is the same one the nodes on, so I would leave it as the local host address of 127.0.0.1 right ?

Also, what about an rpcallowip= in the config, wont that be needed as well ?

baldpope

full member

Activity: 144

Merit: 100

Quote from: baldpope on July 08, 2015, 08:36:01 PM

Quote from: MoreBloodWine on July 08, 2015, 07:11:54 PM

Got CURL installed, seems to run ok but failing on the commands. Wana ask somethin first, does the "ip" 127.0.0.1 or would that be say the internal ip of 192.x.x.x I should be using instead ?

127.0.0.1 is the ip address for the host you're on. It's called 'localhost'. So when you see that as a limit, it means that ONLY the local host (ie the computer the application is running ) is allowed to talk to this service.

So in this case, it means that if you're running in server mode, only a request from the local PC can ask questions of the server node.

It's like they say.. 127.0.0.1 is where the heart is...

cheers,
baldpope

Conversely, if you were to put in any other address, it would mean that a remote client (not of the same machine) could talk with the server instance. Not necessarily bad, but you have to ensure your wallet is protected.

baldpope

full member

Activity: 144

Merit: 100

Quote from: MoreBloodWine on July 08, 2015, 07:11:54 PM

Got CURL installed, seems to run ok but failing on the commands. Wana ask somethin first, does the "ip" 127.0.0.1 or would that be say the internal ip of 192.x.x.x I should be using instead ?

127.0.0.1 is the ip address for the host you're on. It's called 'localhost'. So when you see that as a limit, it means that ONLY the local host (ie the computer the application is running ) is allowed to talk to this service.

So in this case, it means that if you're running in server mode, only a request from the local PC can ask questions of the server node.

It's like they say.. 127.0.0.1 is where the heart is...

cheers,
baldpope

notabeliever

hero member

Activity: 726

Merit: 504

Quote from: pjcltd on July 08, 2015, 03:34:08 PM

Quote from: Ricky Petrovich on July 02, 2015, 03:57:55 AM

Yo, GorillaEx down? Or is it Paul doing updates and stuff?

Not me sorry
its under DDOS attack

Any news about Gorilla.exchange?

no the attack is still ongoing

How does one know a DDOS Attack is happening. what are the signs?

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: MoreBloodWine on July 01, 2015, 11:06:16 PM

Quote from: Ricky Petrovich on July 01, 2015, 04:17:26 PM

Quote from: MoreBloodWine on July 01, 2015, 03:09:31 PM

Screw it, why not... really want to be able to do this and it has to be possible in some respect since IGS brought it up but can't seem to clarify in the way he originally meant.

Snippet: You can auto-launch with walletpassphrase

BOUNTY TIME !!!

50 bucks to the FIRST correct solution to the linked post in this thread !

https://bitcointalksearch.org/topic/m.11765543

You have to put the RPC config in your conf file:

Code:

rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=3333

Then you make your call using curl like this:

curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["", 99999, true] }' -H 'content-type: text/plain;' http://:@127.0.0.1:3333

Cheesy

Please send them to this stealth address:
cYBjoey3EfezH2qJDekP4QHiB6zhEykt2BifBVcGgET3GPDbRFsSsxjNg9XXaR2ywzfnnQwvbqkJoRZ pjiHCLYe7UCTot36TMTB1jb

Gracias

Edit: And double Gracias because I learned something new today Cheesy

Edit2: ["", 99999, true]
99999 : timeout
true : for staking only

Probably shoulda mentioned this is on a windows machine but I can't get this to work even using a batch file. Might just have to give up on this little endeavor.

You start the wallet and AFTER the wallet is running you execute the curl command. You do have to install curl on windows. And create a scheduled task to run after boot. Give a little time like 5 mins. And that should do it.

Edit: And obviously, if you have more than one wallet running , your RPC port should be different for each wallet.

Got CURL installed, seems to run ok but failing on the commands. Wana ask somethin first, does the "ip" 127.0.0.1 or would that be say the internal ip of 192.x.x.x I should be using instead ?

annad

newbie

Activity: 25

Merit: 0

Quote from: trickyriky on July 08, 2015, 10:09:07 AM

AngelLox & baldpope thank you very much, now running gorillabucks wallet and email sent, hopefully they will be nice to me with the coin swap amounts, certainly taught me not to buy any coin over 1 mil sat each lol

Wow, are you in for a big disappointment.

The coins you had in the wallet are only worth about 5 of the new bucks, the others that were on the exchange are lost.

You have about 60,000 sat in total at current market rates.

pjcltd

legendary

Activity: 1778

Merit: 1003

NodeMasters

Yo, GorillaEx down? Or is it Paul doing updates and stuff?

Not me sorry
its under DDOS attack

Any news about Gorilla.exchange?

no the attack is still ongoing

2bacco

full member

Activity: 196

Merit: 100

The Smoker Friendly Coin 2BACCO