Samsung chromebook wireless support? [Archive]

View Full Version : Samsung chromebook wireless support?

xsspants

2013-03-13, 15:40

Since I don't have one to test on;
Does the internal wifi chipset on the ARM chromebook support packet injection, or is this build more focused on USB wifi adapters?

Thanks

Google fu tells me it's a murata ss2907002 wifi chip.
There is nothing for any info on it though. Other than it's samsung and possibly in the galaxy S3 as well.

tpwn3r

2013-03-14, 22:15

I have this build now running on my chromebook.
There is a mlan0 network interface present and the 'mwifiex_sdio' and 'mwifiex' modules are loaded.
I dont see any NetworkManager software to use it to connect to the network though.

sgtboost

2013-03-14, 23:54

I can't get my adapter to even show up...

tpwn3r

2013-03-15, 16:40

I can't get my adapter to even show up...
'ifconfig' only shows the loopback interface for me.
I had to use ifconfig -a to see it.
then 'ifconfig mlan0 up' to bring up the interface.

Im not familier with this driver and info is still more scarce compared to other more common drivers.
Here is some info here https://www.kernel.org/doc/readme/drivers-net-wireless-mwifiex-README

I tried to get kismet running on it but no luck. Looks like it cant turn on monitor mode at this time.

I dont see any NetworkManager or WiCd for simple connecting. Might need to get online with a usb ethernet device until this chromebooks quirks are better documented.

mikez

2013-03-16, 17:18

Having the same problem here. Also, when I start networking service it says it can not find eth0. I'm new to this disto and it sure would be nice to the the wifi working.

mikez

2013-03-16, 18:49

To get the wifi to work, check out the info on these pages and replace wlan0 with mlan0

http://www.ghacks.net/2009/04/14/connect-to-a-wireless-network-via-command-line/
http://www.cyberciti.biz/faq/debian-linux-wpa-wpa2-wireless-wifi-networking/
http://askubuntu.com/questions/149411/iwconfig-usage-for-wep-access-point

totally works!

arkansasclp

2013-03-17, 01:43

Here is what I did:

ifconfig mlan0
iwlist mlan0 scan
iwconfig mlan0 essid myssid key s:mywifikey
dhclient mlan0

Getting closer, but not pulling an IP for some reason, but at least getting closer.....

Note: My network is WPA2-PSK, you might need to remove the s: if yours is a hex based key

g0g4

2013-03-17, 16:12

Hi all!
root@kali:~# airmon-ng start mlan0
interface chipset driver
mlan0 unknown mwifiex_sdio - [phy0] mon0: ERROR while getting interface flags: No such device.

Does anyone know how to switch on monitor mode on chromebook?

xsspants

2013-03-17, 21:10

I've since aquired an ARM chromebook.

Running into the same issues all of you have.

I suspect things will get better once the upstream support reaches our kernel, but for now I'm just plugging in an Alfa and it works flawlessly that way.

Now to find one of those pico sized wifi adapters with injection support....

konez90

2013-03-17, 23:19

after doing the iwconfig mlan0 essid myssid key s:key I am getting error for wireless request "Set Encode" (8B2A)
Seems that if you have a wifikey it does not work, needs to be unencrypted.

g0g4

2013-03-18, 09:58

How to switch on the monitor mode? Driver is mwifiex_sdio.
airmon-ng start mlan0 gives error

sgtboost

2013-03-18, 14:22

xsspants

2013-03-18, 15:10

The current driver for the internal wifi does not support monitor mode.
It barely supports normal mode...

konez90

2013-03-18, 17:21

xsspants are you using Alfa AWUS036H?

arkansasclp

2013-03-18, 18:59

For those of you still trying to get wireless working in general on the Chromebook, here is what I followed and worked based on http://www.cyberciti.biz/faq/debian-linux-wpa-wpa2-wireless-wifi-networking/ posted by previous users.

nano /etc/network/interfaces
auto mlan0
iface mlan0 inet dhcp
wpa-ssid YOUR-SSID-HERE
wpa-psk YOUR-PASSWORD-HERE

mikez

2013-03-19, 01:59

sudo iwlist auth

shows wpa/2, but I've only got it working on an open ap

mikez

2013-03-20, 00:32

So I could get it to connect to an open access point as well as to WPA2-PSK with the resources at:

http://wiki.debian.org/WiFi/HowToUse
http://ubuntuforums.org/showthread.php?t=263136
http://forum.chumby.com/viewtopic.php?id=7939&p=3
http://superuser.com/questions/539082/why-cant-i-connecto-to-my-wifi-ap
https://wiki.archlinux.org/index.php/WPA_supplicant
http://wirelessdefence.org/Contents/LinuxWirelessCommands.htm

seems the trick is to use wpa_supplicant

in any case, once connected I did:
apt-get install wicd

makes life much easier

Hopefully this helps someone...

# I did not modify: /etc/network/interfaces

# Setup credentials for your network:

/usr/bin/wpa_passphrase NETWORKID NETWORKPASSWORD | tee -a /etc/wpa_supplicant.conf

# This spits out the following into: /etc/wpa_supplicant.conf

network={
ssid="NETWORKID"
#psk="NETWORKPASSWORD"
psk=5114234sdfsdf987dblahblahblah9ablahblahblahbla hblahblahblahblahblahblahblhab45345e
}

# Edit that file to make it look like this, while retaining the previous name/value pairs:

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="NETWORKID"
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
#psk="NETWORKPASSWORD"
psk=5114234sdfsdf987dblahblahblah9ablahblahblahbla hblahblahblahblahblahblahblhab45345e
}

# pass the credentials to the adapter using wext driver

wpa_supplicant -d wext -i mlan0 -c /etc/wpa_supplicant.conf

# depending on what you messed with, you may need to kick the adapter or serivce

/etc/init.d/networking restart
ifconfig mlan0 up/down (rather down/up)

# if you still dont get resolution it could be dhcp...refresh with

dhclient mlan0

# you could also try connecting manually

iw dev mlan0 connect NETWORKID

# if you see the following result from the previous command be patient and wait
# a min before pinging google again, it may be trying to connect to the ap

command failed: Operation already in progress

Also does anyone else find it ironic that when you run chromium (after apt-get install) it seg faults?

tpwn3r

2013-03-20, 07:33

This page seems to insinuate that the wireless does support injection.
http://docs.kali.org/development/custom-chromebook-kernel-image

Patch the kernel, in our case, with wireless injection patches.

xsspants

2013-03-21, 18:13

This page seems to insinuate that the wireless does support injection.
http://docs.kali.org/development/custom-chromebook-kernel-image

That only appears to patch mac80211.

Regardless, when i was messing with it earlier, -9 failed to confirm injection support.

I'll revisit it tomorrow.

mikez

2013-03-22, 00:58

Setting monitor mode returns Operation not supported. It doesn't look to be an option in the driver (line 97 (assuming its current))
http://lxr.free-electrons.com/source/drivers/net/wireless/mwifiex/README

It's possible the hardware doesn't support injection, does anyone know what kind of chip is in the device? Is this it:
http://www.ebay.com/itm/Samsung-Chromebook-XE500C21-H04US-Wireless-WiFi-Card-T77Z204-26-/261096746857

xsspants

2013-03-22, 05:03

mikez

2013-04-03, 19:11

The chip is soldered to the motherboard, so swapping it out is not easy, interestingly, my is labeled as SS2907001. Short of contacting Murata or the driver developers, there is pretty much no info on the adapter. The driver seems to be the only one available for this chip set http://linuxwireless.org/en/users/Drivers/mwifiex and the git repo doesn't seem to have anything about monitor mode. http://git.marvell.com/?p=mwifiex.git;a=summary. It's probably easiest just to get a usb wifi adapter that supports the functionality.

j0k3rr

2013-04-24, 03:25

The Alpha card works perfect with the Kali Linux Chromebook the issue seems to be the power source, on your alfa card the USB cable has two ends, the "main USB" male connector and an extra usb cable attached to it , u can plug it into a portable USB battery pack and it will get the alfa card up and working, hope this helps