Yeah, now I've reconfigured it so wlan0 is the WAP and plugged wlan1 in for monitor mode ... but "airmon-ng start wlan1" won't put wlan1 into monitor mode, so it sounds like your idea is right on the...
Type: Posts; User: rpilover
Yeah, now I've reconfigured it so wlan0 is the WAP and plugged wlan1 in for monitor mode ... but "airmon-ng start wlan1" won't put wlan1 into monitor mode, so it sounds like your idea is right on the...
Ah, no I've not had this working simultaneously as WAP and monitor. Both functions have worked, but only now am I trying them simultaneously.
Now I've removed wlan1 and commented out the wlan1...
Interesting.... How would changing it to be wlan0=WAP/wlan1=mon fix it if the problem is two instances of the same driver?
I'm running Kali 1.06 on a Raspberry Pi with 2x identical USB WiFi NICs. wlan0 is for pentesting, wlan1 is set up as a WAP for SSHing in. Both NICs have been on my home network and work just...
I have the same result.
root@kali:~# lsusb
-bash: lsusb: command not found
root@kali:~# lspci
bcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
But lsmod...
Thanks for the info, everyone. I'm home again and rebooted, will let you know if it happens again. I was downloading the realtek drivers at the time (and "aptitude show" indicates that it's...
Thanks, @bond benz ... is that a permanent fix or just a good way to bring it back up? My biggest concern is getting disconnected while SSH'd into it and unable to reboot.
I have Kali 1.06 installed on a Raspberry Pi (thanks for all the fixes, by the way) with two Edimax 7811Un USB wifi dongles (RTL8192cu chipset) on a powered hub. Wlan0 has a static address that...
Huh, interesting...
If you go to kali.org and click for Downloads/Custom Kali Images, it takes you to http://www.offensive-security.com/kali-llnux-vmware-arm-image-download/ where there are ARMEL...
Thanks for getting the 1.06 ARM images out, but I don't see one for the Raspberry Pi. Anyone have an ETA?
Looks like there was a problem with the 1.04 ARMEL release for RPi. The 1.05 release fixed this problem. Thanks to all for their help.
I just saw that there's a 1.05 image available for the Raspberry Pi, that seems to have fixed my issues! Yay!
Ah, good point, I should have mentioned the RPi build in my original message. Yes, it's the Model B, 512MB version. Does that help anyone?
If this is one of those "... it's been answered elsewhere" kinds of problems, I'm open to reading up on a few key terms pointing me in the right direction and I'll do my own research.
I've installed Kali on an SD card and it boots on a Raspberry Pi. During boot, eth0 pulls an IP just fine and I can log in locally, but my problem is that wlan0 never comes up. I have four...
I'm installing rfkill now, having found a wired network to use.
"Can't open RFKILL control device: No such file or directory"
Does it matter that this is Kali running from an SD card in a Raspberry Pi? The image came from the main downloads page on kali.org.
Both "rfkill list" and "rtkill list" result in "command not found".
"rtkill list" shows "command not found". Any other ideas?
From a default installation of Kali on Raspberry Pi, I've edited /etc/networking/interfaces and added:
auto wlan0
iface wlan0 inet dhcp
auto wlan1
iface wlan1 inet dhcp
and restarted...