What's odd is that baby will happily connect after manually editing these files and rebooting:
/etc/network/interfaces
/etc/wpa_supplicant.conf

# cat /etc/network/interfaces
auto lo
iface lo inet loopback

mapping eth1
        script /etc/network/if_mapping

iface eth0 inet dhcp
        script /etc/network/udhcpc_action
auto eth1=befw11s4v4
iface befw11s4v4 inet dhcp
        script /etc/network/udhcpc_action
#
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={
        ssid="befw11s4v4"
        psk="12345678"
        proto=WPA
        key_mgmt=WPA-PSK
}
#

Can you try to catch the content of these two files while Baby tries to connect? They are updated and saved when Baby starts to connect, but if it can't connect, then the data about the AP is cleaned out again.

So, do a factory reset, go through setup for this AP and then while it tries to connect, do a couple of 'cat /etc/wpa_supplicant.conf' and 'cat /etc/network/interfaces'. I am wondering what's in these two files and how they differ.

Created attachment 5494 [details]
probably not too helpful

That was cat output from those two files while failing to connect with WEP. Do you want that output with WPA too?

Did you change the SSID? The example in comment #1 used: "befw11s4v4" but the attached failed WEP connection uses: "befw11s4 not rico" as SSID.

Do you guys have two of the same router with similar or same SSID? Maybe it picks the wrong one?

And yes, I would like to see the same output when trying to connect with WPA, i.e. use the same settings as you used in comment #1.

I'd like to compare the two automatically generated files to see if they differ from what you configured manually.

Can you also post the MAC address of your router? The attached log shows a connection to a router with MAC address: 00:12:17:15:5a:39. Is that the one you wanted to connect to?

Thanks
Felix

Created attachment 5500 [details]
baby serial WPA fail

Sorry Felix for not being more clear. Rico and I both have BEFW11S4's, mine is the one with SSID of 'not rico' :)

He and I are both able to reproduce in the same way. This is with baby r6633 since the newer ones wireless doesn't work (bug 12970). 

Does this help at all? Still doesn't connect showing me the key I entered.

For what it's worth, this is not an issue with r6537, I am able to connect after a factory reset.  r6608 does have the issue, maybe that helps narrow it down a bit?

The only difference I can see is that on 6537, there is no ap_scan=2 in the wpa_supplicant.conf.

r6537
ctrl_interface=/var/run/wpa_supplicant
update_config=1

network={


r6608
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
update_config=1

network={

Hi guys

Can you please retry with r6758?

ap_scan=2 was introduced to support hidden SSIDs, but it broke APs using TKIP and maybe others. Fortunately we do not need ap_scan=2 anymore as Atheros provided a driver patch which allows connecting to hidden SSIDs without that setting.

Thanks
Felix

Ricoman try it out please, 6758 works for me! Thanks Felix!