Friday, January 28, 2011

Connect your Cr-48 to WPA/WPA2 Enterprise Networks

David Burrow at the University of Utah has figured out how to connect the Cr-48 to a corporate WPA or WPA2 network. As we've seen with other features, it seems that while the Chrome OS GUI interface doesn't support networks requiring a username and password, the underlying OS structure does. I was able to follow David's instructions to connect to my workplace WiFi network, meaning I could finally use my Cr-48 for Intranet work instead of being restricted to guest mode, Internet only. Please note that this is not an easy process, if you don't know what you're doing and aren't willing to take the initiative to figure this out on your own, it may be best to wait for Google to add GUI support. I'll help where I can but remotely troubleshooting connection issues is nearly impossible so you're just going to need to keep trying different settings. Dave's instructions are quite detailed so I won't repeat them here but a few points:

  • WiFi networks vary in terms of their configuration so you'll have to experiment with the various set_network commands. I found it very helpful to have an Ubuntu laptop (you might be able to use Ubuntu installed on the Cr-48 but it's going to mean lots of rebooting) connect to the Enterprise network first. Once you get it working in Ubuntu make sure "Available to all users" is checked for that WiFi profile. Now look in /etc/NetworkManager/system-connections/ (may need to be root) and you should see a configuration file for that network. Compare the settings in that file with the commands David has, you'll need to tweak his commands to match your network.
  • Once you figure out the exact commands necessary to get wpa_cli to connect, you can create a script that does it for you. Save the file to /mnt/stateful_partition. It should look something like:
    wpa_cli "set_network 1 ssid "MyWorkSSID"
    wpa_cli "set_network 1 scan_ssid 1"
    You'll need to experiment with what works here.
Be sure to share what works or didn't work for you in the comments (watch that you don't post your password though!)


  1. Okay, I was going to post my experience/thoughts here until Blogger got bored and told me my entry was too long.

    SO, if you'd like to read my helps/suggestions, please visit my blog.

    Thanks, Jay Lee, for all your help with this!!

  2. Okay, everyone, if you're pulling your hair out on this after an hour and you feel like you've tried everything, let me make what may seem like an agonizingly obvious suggestion: double-check your password.

    I think my school added a new unsecured "guest" network over the weekend, and so I thought something might have changed with our secured network. Nope, I'm pretty confident I was leaving off one character out of the 24 characters lastpass generated for my school password . . .

  3. Ok, I've managed to get it to autoconnect to my school's network on boot using the instructions below.

    The cliffs notes are that you can edit /etc/init/login.conf to contain a link to your script

  4. Hi,
    Could you explain - as in step-by-step - how to:
    1) create a script and
    2) how to save it to the stateful_partition?

    I am not very experienced with terminal etc...

  5. @--S and anyone looking for a step-by-step on how to save your enterprise network configuration, please see my new post, based on Nick's instructions:

  6. @Jay or anyone else, it looks to me like on the login.conf file is messed up so that it's missing some closing arguments, and I'm unable to get my .etc/wpa_supplicant/ script to run at login.

    Could you please take a look at /etc/init/login.conf and let me know what you think?


  7. So the David Barrow link seems to need authentication to view the article. Any way around this?

  8. It appears that the latest beta releases now support Enterprise WPA through the GUI.