question about placing miners

[rizzler]

let's make this easy, i have a few computers at a house with internet coming from a school, if i where to start 2 miners onsaid computers, would the school be able to detect that the computers run bitcoin miners, yes or no? that's all i wonder.

if yes: what would the ods of detection be ?

[1714188910]

1714188910

[1714188910]

1714188910

[BurtW]

1) The bandwith used for mining is very small so I don't think your internet provider will care
2) The power consumed by (serious) mining is very large.  Your electricity bill will go way up.
3) The heat caused by (serious) mining is very large - do you have air conditioning?  Again, your electricity bill is the issue.

Oh, I think I get the jist of your question now:  you are stealing free internet from an open wireless system.  Am I right?

[jake262144]

...would the school be able to detect that the computers run bitcoin miners, yes or no? that's all i wonder.
if yes: what would the ods of detection be ?

Of course they would, what kind of question is that? You're connecting through their infrastructure.
The odds of being caught... are inversely proportional to the admin's laziness

Note, however, that should the admin take a glance at the AP's control panel (eg. for troubleshooting some issue) your machines will stand out like nudists in a convent - mostly due to nonstandard ports and constant connections.

[BinoX]

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

[rizzler]

Oh, I think I get the jist of your question now:  you are stealing free internet from an open wireless system.  Am I right?

yes, and electricity

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

Really? i am having a look trough my logs on my linuxrouter right now and i do not se almost none towards my pools ip or the port they are using, and currently i have 5 miners in my appartment.

but in short then, if they have a look and it will stand out, and i guess 2 rigs running at 1800~mhash would just scream "LOOK AT ME" ?

[BurtW]

Nice.  "Free" internet and electricity.  What is your hash rate for all your miners combined?

[eleuthria]

Oh, I think I get the jist of your question now:  you are stealing free internet from an open wireless system.  Am I right?

yes, and electricity

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

Really? i am having a look trough my logs on my linuxrouter right now and i do not se almost none towards my pools ip or the port they are using, and currently i have 5 miners in my appartment.

but in short then, if they have a look and it will stand out, and i guess 2 rigs running at 1800~mhash would just scream "LOOK AT ME" ?

If you were using tools a lot of offices use to monitor employees, bitcoin monitoring would stick out like a sore thumb.  It's all HTTP based requests, on a non-standard port.  Most miners are sending more than one request per minute, so if you were to sort a list of all the HTTP requests made by your office by number of requests, odds are it would be at the very top.

[DeathAndTaxes]

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

[eleuthria]

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

That's assuming the miner isn't also using an askrate/scantime shorter than 15 seconds.  I think quite a few miners default to 5 seconds.

[DeathAndTaxes]

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

That's assuming the miner isn't also using an askrate/scantime shorter than 15 seconds.  I think quite a few miners default to 5 seconds.

Why?  With LP is there any legit reason for a miner to ask faster that hashrate demands?  Is it just bad coding, bad defaults?

I mean w/ n-time-rolling I would assume the ask rate should be LESS than hashrate requires (as miner can increment the time locally).

[jjiimm_64]

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

with cgminer, you can easily double this, as there are at least 2 threads per miner.

[DeathAndTaxes]

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

with cgminer, you can easily double this, as there are at least 2 threads per miner.

There are two (or more) threads but they run at half speed and thus each thread requests work half as often.

[BinoX]

It's not the size of the requests, but the AMOUNT of requests that are made...

I ran a miner at work (with permission from the sysadmin [note: I AM the sysadmin]) Over a 2 week period... That one machine (275mhash) made so many requests to just 1 site that it stuck out on the web logs like a sore thumb...

So yes, they will be able to tell very easily.

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

That's assuming the miner isn't also using an askrate/scantime shorter than 15 seconds.  I think quite a few miners default to 5 seconds.

Why?  With LP is there any legit reason for a miner to ask faster that hashrate demands?  Is it just bad coding, bad defaults?

I mean w/ n-time-rolling I would assume the ask rate should be LESS than hashrate requires (as miner can increment the time locally).

Don't forget the fact that if you're mining 24/7 it'll show up on the evening and night stats even more when there's a lot less people (or no-one) using it. Hourly stats are not your friend.

Even at 4 requests/min you're looking at 5760 requests a day to basically ONE URL from ONE CLIENT happening with a fairly regular pattern. It shows up even more if it's going on during Sundays when no-one is working...

That tends to show up unless someone isn't checking, doesn't care or shouldn't be running a network... My morning schedule begins with a backup check, server integrity check and log file check... This takes about 2 hours in all. I like days where I find something because security investigations are more interesting than user requests

[jjiimm_64]

@ 275MH/s it will take 15 seconds to complete a getwork.  That should be like maybe 4 requests per minute.

with cgminer, you can easily double this, as there are at least 2 threads per miner.

There are two (or more) threads but they run at half speed and thus each thread requests work half as often.

edit: my stuff disappeared......


when I migrated to cgminer, I had to install a new router to handle the extra requests.  If what your saying is tru, why does cgminer make so many more requests then say..  guiminer using phenix?