Wireless Interface not appearing in Linux apps in Chrome OS

[DeepSeaDiver]

Good day everyone!

I am attempting to use my Chromebook's Linux installation for network penetration work. I am aware that the Linux "distro" officially available on Chrome OS is Debian-based, but is also sandboxed and is unaware of physical hardware present in my Chromebook.

Is there any way at all to force the virtual network interface to be visible to the Linux container in the Terminal app, for instance?

Thank you for anyone that has any input!

Regards,

DeepSeaDiver

[Mike Frysinger]

what do you mean by "virtual network interface" ?  there's already one visible in the container which is how it has network connectivity.

did you try running `ip a s` to enumerate them ?

-mike

--
--
Chromium OS Discussion mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-discuss

[DeepSeaDiver]

I have not tried that. I've been using "iwconfig" in the AirCrack-NG pentesting tool and I haven't had much luck.

For my own privacy, I've changed all identifiable IP addresses and MAC addresses with [XXXXXX]. But hopefully it's still readable for you guys...

I did try "ip a s" just now, though and it returned the following:

deepseadiver@penguin:~$ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether [XX:XX:XX:XX:XX:XX] brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet [XXX.XXX.XX.XXX]/28 brd [XXX.XXX.XX.XXX] scope global eth0
       valid_lft forever preferred_lft forever
    inet6 [XXXX::XXX:XXXX:XXXX:XXXX]/64 scope link
       valid_lft forever preferred_lft forever

It seems like both show some sort of connection, but then I try "sudo iwconfig" again and this is what is returned:

deepseadiver@penguin:~$ sudo iwconfig
lo        no wireless extensions.
eth0      no wireless extensions.

 

I also tried the Airodump-NG tool with the "lo" interface and it doesn't seem to like it. 

deepseadiver@penguin:~$ sudo airodump-ng lo
nl80211 not found.
ioctl(SIOCSIWMODE) failed: Inappropriate ioctl for device
ioctl(SIOCSIWMODE) failed: Inappropriate ioctl for device
Error setting monitor mode on lo
Failed initializing wireless card(s): lo

How to fix?? :D

Regards,

DeepSeaDiver 

[Mike Frysinger]

there is no way to access the WiFi settings or low level hardware from the container by design:

https://chromium.googlesource.com/chromiumos/docs/+/HEAD/containers_and_vms.md#can-i-access-layer-2-networking

so you can do pentesting at the IP level only.  e.g. nmap.

-mike

[DeepSeaDiver]

Dang... Alright. Thank you for the input! Guess I gotta use some different hardware then.

[Mike Frysinger]

or put the device into dev mode and run Crouton

-mike

[dragon788]

Crouton is the way to go, and I think you can even install Kali Linux in the chroot.

[Dano Tolonen]

if i use a usb wifi thing (i forgot the name) would that work?

something like this