Swedish ASIC miner company kncminer.com

[Paladin69]

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

If the pools were all ddos'd before a difficulty change, could that mess with the adjustment and keep it lower than it should?

[1714038492]

1714038492

[1714038492]

1714038492

[1714038492]

1714038492

[1714038492]

1714038492

[Paladin69]

he next difficulty is estimated to change by 34.72% to 360,699,846 on block #266,111. That should be 5 days 5 hours 59 mins 42 seconds from now.

Thanks for ruining my day...

The final will go above 400m at this rate.

[Templer]

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

Web server is down, pool is up. Pool is what matters however I'm sure they are aware of it and are working to remedy the web server.

Thx...thats really what matters! i give a shit about stats, the income have to be correct^^

sry for OT

[xyzzy099]

eligius under DDOS

I can't seem to pull up the website with stats but my miner shows it's getting shares accepted. New to Eligius, assuming this is par for the course?

same here!

If the pools were all ddos'd before a difficulty change, could that mess with the adjustment and keep it lower than it should?

I don't think so.  The diff change is calculated based on how fast the last 2016 blocks were generated, right?  So unless you DDOS them for the whole 2016 block run, it won't make much difference.

[soy]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0. 

[soy]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0.  

And got the RPI working as a router.  It had an eth0 address 192.168.1.50 before.  I added the Cisco USB adapter.  That was given the address 192.168.1.116.  

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well.  Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked.  Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

[xstr8guy]

Oh, you cant blame Avenger for holding them to their confident promises that they made over and over. That is their mess completely. They seem to think that one rig displayed on 30th Sept. hashing over the spec is worthy of claiming ALL rigs are similar. A great many aren't close to spec. We didn't pay for a lucky dip. ALL rigs should meet the min stats.

No, but you did pay for 400Gh/s.  Anything over that spec is gravy.

[Phoenix1969]

Am I having a nightmare, or did KNC forget to give us an update?

[soy]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0.  

And got the RPI working as a router.  It had an eth0 address 192.168.1.50 before.  I added the Cisco USB adapter.  That was given the address 192.168.1.116.  

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well.  Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked.  Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse.  Say you have a non-wireless router.  Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

Darn 60 something unread messages I've got to catch on back there, got no work done outside, will do my mileage on my treadmill rather than on the road so at least I'll get in an hour running.  Didn't get to adding caps to the ASIC module to test if it can then run better on 0.95.  I have one die that keeps losing 1 to 3 cores and I think it's possibly the VRM getting the least cooling, but where does the time go.  Isn't that a song?  ...where does the time go?

[Phoenix1969]

I tried wireless routers, bridges, modems, and smoke signals.....
the best/most stable connection to wireless I found, was thru a cheapo laptop & a simple ethernet switch. I have 2 desktops, and 3 miners connected to the web thru the laptop's wifi to the android.
Rock solid

[texaslabrat]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0.  

And got the RPI working as a router.  It had an eth0 address 192.168.1.50 before.  I added the Cisco USB adapter.  That was given the address 192.168.1.116.  

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well.  Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked.  Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse.  Say you have a non-wireless router.  Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

You guys are making integration into a wireless network waaaaay too difficult.  I mean, if you enjoy creating Rube Goldberg inspired networks, then by all means don't let me stop you.  However for those who want something a little more straight-forward, let me introduce you to:

http://www.amazon.com/gp/product/B003KPBRRW/ref=oh_details_o04_s02_i01?ie=UTF8&psc=1

[soy]

I tried wireless routers, bridges, modems, and smoke signals.....
the best/most stable connection to wireless I found, was thru a cheapo laptop & a simple ethernet switch. I have 2 desktops, and 3 miners connected to the web thru the laptop's wifi to the android.
Rock solid

This was my first attempt at wireless isolation.  Nothing like the dependability of a cat5 connection so unless I hear thunder....

[soy]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0.  

And got the RPI working as a router.  It had an eth0 address 192.168.1.50 before.  I added the Cisco USB adapter.  That was given the address 192.168.1.116.  

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well.  Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked.  Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse.  Say you have a non-wireless router.  Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

You guys are making integration into a wireless network waaaaay too difficult.  I mean, if you enjoy creating Rube Goldberg inspired networks, then by all means don't let me stop you.  However for those who want something a little more straight-forward, let me introduce you to:

http://www.amazon.com/gp/product/B003KPBRRW/ref=oh_details_o04_s02_i01?ie=UTF8&psc=1

What? spend more money?

[Phoenix1969]

its simpler than that even...
just plug it to a laptop, which has wifi
a cheapo 10/100 is plenty

[texaslabrat]

you might try staying off the 192.168.1.0... just use 192.168..1.1 for gateway, and 192.168.1.(2-245)for clients. the only one with DHCP on should be the server
I often ran into problems using .0

When the last digit is a zero it is the network.  A gateway on 192.168.1.1 is on network 192.168.1.0.  

And got the RPI working as a router.  It had an eth0 address 192.168.1.50 before.  I added the Cisco USB adapter.  That was given the address 192.168.1.116.  

I added a route to network 2.0 with "route add 192.168.2.0 eth0"

I went into /etc/network/interfaces and changed the eth0 static address from 192.168.1.50 to 192.168.2.50 and changed the broadcast address as well.  Then I restarted networking with /etc/init.d/networking restart which this time didn't disconnect me because wlan0 stayed.

Then I booted my WinXP and gave its internet connection a static address of 192.168.2.6 and changed the gateway to 192.168.2.50 and rebooted.

Could ping 192.168.2.50 and 192.168.1.116 so the WinXP laptop was reaching the wlan0 port of the RPI but when I tried pinging 192.168.1.1 it failed.

I gave the command as root on RPI "sysctl -w net.ipv4.conf.all.forwarding=1" the tried pinging 192.168.1.1 from a dos box on the WinXP home and Bob's your uncle it worked.  Then I pinged yahoo.com from WinXP with complete success.

Now I can use the RPI as a wireless router I'll just have to establish a static address in the .2.0 net on the machine that's going to be forwarded.

Bet it's possible to do the reverse.  Say you have a non-wireless router.  Bring up the RPI, plug in a USB wireless, put the wireless on another net, adding routing and forwarding, boot a tablet and assign it a static IP in that new net, and you've converted a non-wireless router into a wireless router.

You guys are making integration into a wireless network waaaaay too difficult.  I mean, if you enjoy creating Rube Goldberg inspired networks, then by all means don't let me stop you.  However for those who want something a little more straight-forward, let me introduce you to:

http://www.amazon.com/gp/product/B003KPBRRW/ref=oh_details_o04_s02_i01?ie=UTF8&psc=1

What? spend more money?

Just saying that your time is worth something too.  And not everyone has a spare RPi laying around. Nor a spare laptop to use as a horribly energy-inefficient wireless bridge/router.  While the 2 of you seem to have a working solution up and going (Rube Goldberg style), I just thought I'd mention some far easier solutions to others who might be contemplating the same.  Since it doesn't rely on USB to work (it's a true wireless-to-cat5 bridge), you can use it on any device with an ethernet port...or even a switch/hub to get more than 1 box talking over the wireless bridge.  

[Altomesi]

I would not rely on a raspberry pi to act as a wireless bridge, I would much rather have a wireless gaming adapter for nearly the same price as a raspberry pi. While no longer sold, I'm using this without issue and it took a whole 10 seconds to setup...

http://support.linksys.com/en-us/support/adapters/WGA600N

[Phoenix1969]

I tried a wireless bridge... it sucked... totally.
Want one?...lol
whatever works for you...

[texaslabrat]

I tried a wireless bridge... it sucked... totally.
Want one?...lol

There are some crappy ones out there for sure...but the one I linked is pretty awesome for those just now starting to wonder about how to put their miner on wireless and don't want to jump through a lot hoops to do it.  I do high-end networking for a living and I'm not easily impressed with home consumer-grade gear..but this little box really surprised me for the build quality and the signal strength it was able to maintain throughout the house during my wireless torture test.

[Phoenix1969]

I tried a wireless bridge... it sucked... totally.
Want one?...lol

There are some crappy ones out there for sure...but the one I linked is pretty awesome for those just now starting to wonder about how to put their miner on wireless and don't want to jump through a lot hoops to do it.

sure... all helps...
I was not satisfied at all with a bridge, it liked to drop connections randomly...
The laptop's range is like 10x as far, gets waaay better reception, and has never dropped the connection in 6 days so far...

[The Avenger]

Am I having a nightmare, or did KNC forget to give us an update?

They are such a groundbreaking company they redefine words as they go along.

"Daily" means reporting on what happened yesterday, which as that was nothing, it means they have to wait for 2 days of production before giving us a "daily" report. Least that is what happened last week.
+
"shipped" means "meh, dunno what happened to your order"
+
"in progress" means "not in progress"

Let's not even start on what "no later than October 15th" means to them...