I would recommend you install CK's latest firmware, I think that's still 0821. I have seen a couple of people complain they have had nothing but problems with the latest Avalon firmware installed on their machines.

Flash the machine with the CK firmware, do not restore the settings. And add your mining servers back manually and confirm if it's working.

I am not sure if you have are doing this, but my Avalon's are set to failover and I have two pools added to them, I found when I only added one Pool the hashing sometimes would not start at all, it's only when I added the second pool (as a failover) I didn't have any issues at all and at restart the hash kicks on pretty quickly.

Keep in mind when you update the firmware (pushing it back to CK's 0821) the default settings will be applied to the Avalon, so you will need to connect to it on 192.168.0.100.

When you connect a computer do your network does your computer get an IP address? If so there is a DHCP server (application if you want to call it) running likely on your internet modem or router. Avalon's by default enable DHCP server so you need to make sure this is disabled as two DHCP servers on the same subnet (192.168.0.xxx) will fight with one another as you are technically only supposed to have ONE DHCP server in your network environment.

So disable DHCP on your Avalon, assign the Avalon a static IP within the range that your DHCP doesn't operate in; example again DHCP servers may say the first IP is 192.168.0.100 with a pool of 50 so .150 is the last IP it will hand out. You have IP's 192.168.0.1 to .99 and .151 to .254 which you can statically assign out to your equipment. If you assign a DHCP server address statically when a second device grabs that IP from the DHCP server which doesn't know what machines have that IP assigned statically you will have an IP conflict problem between the two devices.

The last thing I forgot to ask or mention is plug your computer into your network and confirm you can get out on the internet. Then go to command prompt (if you are running windows) and type "ipconfig /all" without the quote, then look for the network adapter that has 192.168.0.x for the IP, copy down the numbers, IP, Subnet, Gateway, DNS.

On your Avalon you it should have it's own IP, subnet, the gateway must match what your computer says, and DNS I set mine to 8.8.8.8 which is Google's openDNS server.

[Firmware Version] => 20130923
cgminer: 48681dd
cgminer-openwrt-packages: 3527ce4
luci: 296b358
Socket connect failed: Connection refused

You need to set your computer IP address to 192.168.0.1, subnet 255.255.255.0 and leave everything else blank. Then apply the settings, and make sure your computer and the Avalon are plugged into the same network and then open up IE or Chrome and go to 192.168.0.100 or http://192.168.0.100/ and you should be able to log into your Avalon.

I believe if you have a look at the Avalon Wiki it explains how to log into the Avalon with the default settings.

$ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.


config 'interface' 'loopback'
      option 'ifname' 'lo'
      option 'proto' 'static'
      option 'ipaddr' '127.0.0.1'
      option 'netmask' '255.0.0.0'

config 'interface' 'lan'
      option 'ifname' 'eth0'
      option 'type' 'bridge'
      option 'proto' 'static'
      option 'netmask' '255.255.255.0'
      option 'ipaddr' '192.168.0.100'
      option 'gateway' '192.168.0.1'
      option dns '192.168.0.1'
      option broadcast '192.168.0.255'

Hm, if you are logged in on telnet, where are you trying to connect with ssh? i mean, the failsafe is already running on telnet for you to access. and it shows that you are logged in..

I suggest you, when logged in on telnet do:
more /etc/config/network

Show the output here. I assume it is a fixed ip-address you set a while back.
Put your pc on an ip on the same subnet, with that, you will be able to access the web admin using the ip you got from the above command and configure the unit again.

root@(none):/# ssh 192.168.1.1 -l root
ssh: Exited: Error connecting: Connection timed out
root@(none):/# ssh 192.168.1.2 -l root
ssh: Exited: Error connecting: Connection refused

Here's the full and very confusing link

http://wiki.openwrt.org/doc/howto/generic.failsafe

But yes, telnet is supposed to work first after a reset before you need ssh.

If you have set the IPv4 address of your avalon to 192.168.1.2 you also have to ssh to the same address or use your webbrowser (the address of the avalon thus 192.168.1.2).

Cheers

updated the firmware, with keep settings now the avalon is not responsive

so be carefull

Arrived today! Hashing away, been waiting so long.

Also got my tracking.  Batch 2 order placed Feb. 18, order 15xx.
Single unit to be delivered to Canada. Thanks Yifu!

did you pick DHL or EMS? As I am also in Canada and picked EMS for batch 3.

Did you call DHL to get it or did they email you info?