Printable View
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.
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.
I can't get my adapter to even show up...
'ifconfig' only shows the loopback interface for me.Quote:
I can't get my adapter to even show up...
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/dr...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.
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.
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/con...-command-line/
http://www.cyberciti.biz/faq/debian-...fi-networking/
http://askubuntu.com/questions/14941...p-access-point
totally works!
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
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?
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....
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.
How to switch on the monitor mode? Driver is mwifiex_sdio.
airmon-ng start mlan0 gives error
Thanks - I am now at the same point you are. No dhcp lease.Quote:
Originally Posted by arkansasclp
The current driver for the internal wifi does not support monitor mode.
It barely supports normal mode...
xsspants are you using Alfa AWUS036H?
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-...fi-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
sudo iwlist auth
shows wpa/2, but I've only got it working on an open ap
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/53908...-to-my-wifi-ap
https://wiki.archlinux.org/index.php/WPA_supplicant
http://wirelessdefence.org/Contents/...ssCommands.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?
This page seems to insinuate that the wireless does support injection.
http://docs.kali.org/development/cus...k-kernel-image
Quote:
Patch the kernel, in our case, with wireless injection patches.
That only appears to patch mac80211.Quote:
Originally Posted by tpwn3r
Regardless, when i was messing with it earlier, -9 failed to confirm injection support.
I'll revisit it tomorrow.
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...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-Chro...-/261096746857
Murata SS2907002, WiFi/BT moduleQuote:
Originally Posted by mikez
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.
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