Antminer S1 setup

[kabopar]

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

[willoneal]

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.

[kabopar]

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?....

Cheers

[CDCoinminer]

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? 

[kabopar]

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

[willoneal]

Ok, I found the problem. I do appreciate everyones help!

It was an upstream router doing intrusion prevention, specifically denying bitcoin transactions.

[kabopar]

Great that you got it going.
Happy hashing!