What do you set to DHCP and why? 
I use only the WAN interface on my Antminers, and leave it with fixed IP which is set to a different value for each Antminer S1. All these fixed IP addresses are within the range supported by my router, and do not conflict with other devices.  I read many posts by people who got their Antminer S1's into trouble by trying to use the LAN interface, bridging it with the WAN and all sorts of other combinations.  Note that WAN means "Wide Area Network"  (NOT "Wireless").

Why use a fixed IP?  - because it removes the variability of different IP every time you cycle power on your Antminer and removes the issue of DHCP lease expiry (DHCP grants a 'temporary' IP address which expires after some set time, which may cause connection loss).
While some people managed to use their Antminer's with the WiFi, there are also many who reported issues with that, so a wired network connection is the preferred way to go.

Follow one of the setup guides such as https://bitcointalk.org/index.php?topic=355387  or  https://bitcointalk.org/index.php?topic=344970.0

Cheers

Any updates on ETA?

Cheers

While the price of S3 has not been announced yet, the anticipated price is likely to have a similar GH/s/BTC to the current market price of the S1.  As the S3 hash rate is about 2.5 twice that of S1, the price is likely to be proportionally higher.  The biggest advantage of S3 is in the relative power consumption, where it clearly beats the S1.  If you get free electricity that wouldn't matter to you.  There are second order issues like cooling needs (advantage to S3 on a per GH/s basis).  You may also consider delay until supply (S3 is brand new, there is huge interest, it make take some time until deliveries start and actually happen). There is also a potential issue of 'infant mortality' issues, firmware/software bugs etc.  (s1 had 3 firmware releases, a few h/w versions etc).  Today the S1 is stable and mature.  Mining difficulty changes all the time, so in bicoin mining time is of the essence.  In my opinion, get a cheap S1 today, later either upgrade it to S3 or 'down-volt' it to improve energy efficiency (only if you pay for electricity).
('Somebody' just cancelled a S1 purchase from me, and I'm actually grateful...

Cheers

Enjoy

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

Check if you are not going over your power limit - how many U2's are you using per hub? What is the current spec of your power supply?

I've been using these with bfgminer, where the instruction that worked for me to overclock to about 2 GH/sec per device is
--set-device antminer:clock=x0981

Note that Bfgminer uses the silabs VCP DRIVERS. Not the WinUSB driver installed with Zadig. To fix go to device manager with it plugged in right click choose driver settings make sure the checkbox for delete driver is ticked.  Download and install the silabs VCP drivers instead.

If you want to stick with cgminer, check out https://bitcointalk.org/index.php?topic=658668.0 where ckolivas addresses this.

Cheers

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

Where are you shipping from?

Cheers

Thanks for the link to the setup guide.
I think that the fixed IP setting is the better choice.  Assuming that you want your Antminer to mine independently, without 'babysitting', the last thing that you want is expiry of a DHCP lease.  DHCP is fine for a PC that you periodically connect, and the lease gets renewed and runs for the duration of your PC use session. With a 'permanent' connection like a miner, this is a bad choice. My Ants have been running for weeks or months without interruption, the last thing that anyone needs is a lost connection because the DHCP lease happened to expire.

Cheers

A comparison to S2 is irrelevant imho, as S3 comes without a PS or full enclosure.

Actually the smaller hash rate/size is a good decision, as it will be easier to ship, easier to make a 'buy decision' and will come below the customs/VAT/GST threshold in some cases (or at least will make it less painful).  Another consideration is that if you intend to mine and then sell the h/w, it is a lot easier to sell something like S1 or S3 on eBay than a >=1TH 'beast'.

Cheers

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

Interested in 1 at this stage.
Assume that shipping will be directly from China to members of the GB (doesn't make sense to double ship to US then re-distribute, all GB gains will be consumed by shippers).
If there are coupons to existing Bitmain customers, these should be applied to buys through the GB.

Cheers

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

Will it be possible to upgrade existing S1s?
This may be a huge marketing opportunity, if the new blades are compatible with existing controller/chassis.

You have to describe EXACTLY what you are doing if you want to get effective help, then you need to follow the instructions.
The troubleshooting should be done in the simplest setting possible, that is one PC to one Antminer, direct LAN connection, no router involved.
1) Change your PC network connection from DHCP to fixed IP: The PC or laptop should be set to a fixed IP address (not DHCP)  Assuming that you are running Win7 and connect through a wired LAN: go to Control Panel, Network and Sharing Center, on the left side click on 'change adapter settings', right click on the adapter (called something like 'local area connection xyz'), click on properties (you need to have admin rights), select internet protocol version 4(TCP/IPv4), click 'properties', write down the current settings, then change the setting from 'obtain an IP address automatically' to 'use the following IP address', then enter a fixed IP address which is different from the Antminer one, but on the same subnet, for example 192.168.1.50. 
2) Disconnect your PC from your router/network. 
3) Connect your PC directly to the Antminer S1 being tested using either a 'crossover' LAN cable or 2 normal LAN cables and a Hub/Switch (which is not connected to the rest of your network, only between the PC and the Antminer).  Use only LAN cables that you have previously verified to be 'good', or test them before use with a LAN cable tester.
4) Restart the PC (to make sure that it gets the fixed IP that you nominated in step 1).
5) start the Antminer S1.
6) On the PC start your browser and enter the Antminer's default IP address written on the sticker on the front panel of the Antminer (usually 192.168.1.99).  This should bring the gui (graphical user interface) page.
7) If it doesn't: Press and hold the small reset switch on the Antminer controller for  at least 3 seconds.  Try to refresh the gui page on the PC.  If it still doesn't come up over a few tries and a few minutes, then try cycling the Antminer's power off, wait for at least 30 seconds then turn on.

Report everything that happened (including screen shots if possible)
If you are successful, then change your antminer's settings to whatever you require.  Note that the main LAN interface that matters in my experience is the WAN (wide area network).  It is better to set it to a fixed IP address within the range supported by your router.  Once you finish changing your settings you can connect the Antminer to your network, change your PC back to original DHCP settings that you wrote down in step 1).

Cheers

Thanks Dogie,
I was clearly wrong when I said that it is 5V..

Cheers

I don't think that the R-box is powered off the USB port, as it uses a direct barrel connector for 5V, so the USB hub could be used just to power the rPi.

Cheers

pm sent

Rockminer read your post, and understood that their price is 'too good', so they increased it to 1 BTC on their web site...

It would be nice if it was priced under about USD 500, as the import threshold for GST in Australia is AUD500 (which the Antminer S1 met, but Bitmain probably was not aware of this).

Cheers

In my case I never used the LAN, only the WAN (they are all wired).  Note that WAN means Wide Area Network (not wireless).  On the TP-link board used as a controller both LAN and WAN are accessed through the same RJ-45 connector, but can't be on the same subnet.  I think that the Bitmain intention is to use the WAN, as that is how they come configured from the factory.  I've set the WANs of all of my ants to different fixed IP addresses, which are also reflected in the IP address reservation of my router (to prevent them being assigned to another device if that Ant happened to be off).  Using DHCP seems 'easy' from the router point of view, but that has a few disadvantages:  1) DHCP has a finite time lease, assuming that you want your ants mining for weeks without interruption and 'baby sitting', you may have issues when the lease expires.  2) it is so much easier to manage your ants using mdude7's great Antminer Monitor, or just a browser gui when the IP addresses are fixed.

Good luck