Pages:
Author

Topic: Antminer S1 setup (Read 2314 times)

hero member
Activity: 616
Merit: 500
June 30, 2014, 05:13:23 AM
#27
Great that you got it going.
Happy hashing!
newbie
Activity: 16
Merit: 0
June 29, 2014, 05:54:50 PM
#26
Ok, I found the problem. I do appreciate everyones help!

It was an upstream router doing intrusion prevention, specifically denying bitcoin transactions.
hero member
Activity: 616
Merit: 500
June 20, 2014, 09:40:00 PM
#25
Screenshots would be awesome.

I had the WAN ports set up, and the miner could talk outside the network just fine. But mining would never start. So I read some forums somewhere and they said the use the LAN port.

Now the LAN ports work the way they are supposed to, but still, no mining.

I'm not proud to say this, but I've been struggling at getting mining started for over 2 weeks, and I can't get anything to happen.

Isn't the LAN port only for the two ASIC boards to communicate with each other? 
No, the connection to the ASIC boards is sort of a USB one (checkout the System Log, it has entries such as "bitmain 1-1.1:1.0: USB Bitmain asic device now attached to USB Bitmain asic-0". 
The LAN/WAN interfaces exist because the controller is a TP-link router board (TP-Link TL-WR743N/ND).  In our application there is no real need for dual ports, especially as we have a single physical connector.

Cheers
newbie
Activity: 9
Merit: 0
June 20, 2014, 09:50:18 AM
#24
Screenshots would be awesome.

I had the WAN ports set up, and the miner could talk outside the network just fine. But mining would never start. So I read some forums somewhere and they said the use the LAN port.

Now the LAN ports work the way they are supposed to, but still, no mining.

I'm not proud to say this, but I've been struggling at getting mining started for over 2 weeks, and I can't get anything to happen.

Isn't the LAN port only for the two ASIC boards to communicate with each other? 
hero member
Activity: 616
Merit: 500
June 19, 2014, 11:01:51 PM
#23
Does your pool detect your miner?  Are you certain that your miner credentials are 100% correct (no extra spaces or missing characters?)
Could it be something as silly as you expecting the Antminer web gui status page to 'auto refresh' - unfortunately it doesn't, you need to click again on the 'Miner Status' tab or refresh the browser page.

(or you could just try to follow my instructions, which worked on many Ants...and consider that there are many firewall rules that you might not have changed with your bridged LAN/WAN connection... or is it the issue of using a MAC?....Smiley

Cheers
newbie
Activity: 16
Merit: 0
June 19, 2014, 04:54:38 PM
#22
I appreciate the help, but what I've got is not a networking problem. The miner is talking to the pools. It's just not mining.

How do I know it's talking to the pools? Because it's in the log files of both the miner and the firewall.

Network   Protocol   Source   Destination   Transfer
IPV4   UDP   192.168.254.111:137   192.168.254.255:137   7.47 MB (100453 Pkts.)
IPV4   UDP   192.168.254.111:17500   255.255.255.255:17500   3.55 MB (14105 Pkts.)
IPV4   UDP   192.168.254.11:17500   192.168.254.255:17500   1.08 MB (2107 Pkts.)
IPV4   UDP   192.168.254.11:17500   255.255.255.255:17500   1.08 MB (2107 Pkts.)
IPV4   UDP   192.168.254.111:17500   192.168.254.255:17500   727.29 KB (2821 Pkts.)
IPV4   TCP   192.168.254.11:62414   192.168.254.200:80   80.51 KB (740 Pkts.)
IPV4   TCP   192.168.254.200:60477   ec2-54-195-36-180.eu-west-1.compute.amazonaws.com:8332   3.87 KB (13 Pkts.)
IPV4   TCP   192.168.254.200:40196   stratum.btcguild.com:3333   2.24 KB (16 Pkts.)
IPV4   TCP   192.168.254.200:40198   stratum.btcguild.com:3333   2.24 KB (16 Pkts.)
IPV4   TCP   192.168.254.200:40200   stratum.btcguild.com:3333   1.19 KB (12 Pkts.)
IPV4   TCP   192.168.254.200:40201   stratum.btcguild.com:3333   1018.00 B (10 Pkts.)
IPV4   TCP   192.168.254.200:60666   ec2-54-225-68-97.compute-1.amazonaws.com:3333   1018.00 B (10 Pkts.)
IPV4   TCP   192.168.254.200:40202   stratum.btcguild.com:3333   1018.00 B (10 Pkts.)
IPV4   UDP   192.168.254.200:17016   google-public-dns-a.google.com:53   74.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:47324   google-public-dns-a.google.com:53   73.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:51647   google-public-dns-a.google.com:53   72.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:40278   google-public-dns-a.google.com:53   71.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:41035   google-public-dns-a.google.com:53   66.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:60944   google-public-dns-a.google.com:53   66.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:39171   google-public-dns-a.google.com:53   64.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:26529   google-public-dns-b.google.com:53   60.00 B (1 Pkts.)
IPV4   UDP   192.168.254.200:26529   google-public-dns-a.google.com:53   60.00 B (1 Pkts.)

THe problem is the miner won't start.
hero member
Activity: 616
Merit: 500
June 18, 2014, 11:58:01 PM
#21
Looking at my working Antminer settings








I hope that this helps.  Looks like the main differences are:
1) Use WAN not LAN
2) Don't bridge WAN with LAN

Cheers
sr. member
Activity: 244
Merit: 250
June 18, 2014, 06:14:30 PM
#20
And still nothing? I am going to start posting my settings. Let me know if you see something different. Also are you hitting save and apply when you make changes?



Wan settings
sr. member
Activity: 244
Merit: 250
June 18, 2014, 04:44:57 PM
#18
Ok on the lan interface under physical settings put a check in the bridge interfaces box and set it to eth0.

Also check the firewall settings

newbie
Activity: 16
Merit: 0
newbie
Activity: 16
Merit: 0
June 18, 2014, 03:10:26 PM
#16
Ok, my updated:

https://www.evernote.com/shard/s2/sh/ddd32bda-b733-4d0a-a217-ca33cab35ed8/5d85abba82a6e58a604d3baf0d480f24/deep/0/Ant-Miner.png

I suppose I'll know in 10 minutes or so if it's working. BUt I have to step away.
sr. member
Activity: 244
Merit: 250
June 18, 2014, 12:50:53 PM
#15
My interface screen does not look like this. On the Lan interface it says br-lan(Bridged) But my wan interface says eth1. Assuming you are using the wired connection I would move the wan interface to eth1 in physical settings.
newbie
Activity: 16
Merit: 0
June 18, 2014, 11:24:18 AM
#14
There is nothing listed on the miner status page - just "This section contains no values yet." It's been sitting empty for 3 weeks.

The lights on the actual device are flashing slowly, and the Realtime Load on the Realtime Graphs - Load page shows the average load at .04. I'm pretty sure based on that it's completely idle.

There is traffic on eth1.

https://www.evernote.com/shard/s2/sh/49978fdc-8528-49cd-8998-79655f210dcf/dd9f1111c61badf0f473d8f42cb16f28/deep/0/Ant-Miner.png

The WAN interface is set up just as the manual and the youtube video describes. There is no configuration on the LAN. You can see packets on the WAN interface in both directions.
https://www.evernote.com/shard/s2/sh/eaf5db00-618f-44f8-9626-c087cbcf81c5/86e5cbd4753ca7034e5b8c9bd246607a/deep/0/Ant-Miner.png

I can ping and traceroute from the box to both stratum.btcguild.com and api.bitcoin.cz

I don't get it.
hero member
Activity: 616
Merit: 500
June 18, 2014, 08:31:35 AM
#13
On my Ants I ignore the LAN, set only the WAN (wide area network) to a FIXED IP (not DHCP, because you'll reach the end of your finite time DHCP lease, and you don't want to 'baby sit' your miner and manage renewing the lease).  The fixed IP needs to be within your router's range and not clash with any existing devices (if your router supports local network IP 'reservation' use that to reserve the same fixed IP for the Ant, so you if there is some new device connected while the Ant is off for some reason, it won't 'capture' the intended address of the Ant).
Ensure that your pool settings are 100% correct (or after factory reset it will bring the 'test' pools and you can check that these hash after your fixed your WAN, before you try your own pool(s)).

If you read Bitmain's AntMiner S1 Manual, and Sushi's guide, they all refer to the WAN.  Note also that the LAN and WAN cannot be on the same network segment (Bitmain's S1 manual, page 6 of 9).

Good luck
sr. member
Activity: 244
Merit: 250
June 18, 2014, 07:27:38 AM
#12
Well that confirms that you have full communication. On the miner status page do you have any getworks at all?
newbie
Activity: 16
Merit: 0
June 18, 2014, 06:36:18 AM
#11
Yes, my IP range is 192.168.254.1

iMac:~ woneal$ telnet stratum.btcguild.com 3333
Trying 198.245.63.145...
Connected to stratum.btcguild.com.
Escape character is '^]'.
sr. member
Activity: 244
Merit: 250
June 17, 2014, 08:04:42 PM
#10
Normally I would say it's something blocking port 3333, but you can see it in your router logs. Out of curiosity can you telnet to port 3333 on stratum.btcguild.com?(from a command prompt) telnet stratum.btcguild.com 3333 You wont be able to actually connect, but you should get a black screen. You should not get an unable to connect error.

This assumes your pc is on the same subnet as your miner.(192.168.254.??)
newbie
Activity: 16
Merit: 0
June 17, 2014, 07:43:16 PM
#9
I sent my settings over to the support people at jonesgear, where I bought the miner. They are using my worker on one of their miners. that same exact information will not work for me.

So yes, my worker is in the right format, and yes, I created the username on btcguild.com

There is only one pool in there (listed 3 times), but on your suggestion I made another one on another site to see what would happen.
sr. member
Activity: 244
Merit: 250
June 17, 2014, 07:34:47 PM
#8
That's really weird.

Are your worker names in the correct format?(fillmywallet_1) Any password will work. The number is the actual worker. The other name is your username on btcguild.com. Also did you create the worker on your btcguild account?

Also have you tried another pool? You really need a backup pool anyway.
Pages:
Jump to: