September 28, 2017 at 3:55 pm #12049
When I do airmon-ng start wlan0 I get error adding monitor mode interface: command failed: Operation not supported (-95)
September 28, 2017 at 6:43 pm #12050
you can run
nexutil -m2to put wlan0 into monitor mode.
Hope that helps,
September 28, 2017 at 7:52 pm #12051
I got Command not found.. I downloaded the 2017.1 image you have on the kern4l page and did apt-get update && apt-get upgrade. Then did apt-get install kali-linux-full. Then apt-get dist-upgrade. I don’t know if that would affect the kernel though.
September 28, 2017 at 8:48 pm #12052
Those images don’t have the nexmon drivers installed yet by default, I’m going to change that this weekend.
You can install them by cd’ing into the kernel installation directory/nexmon/
and follow the instructions in nexmon.txt.
Please let me know how your go.
September 29, 2017 at 6:00 am #12053
Thank you for the help dude, it works just fine.
September 29, 2017 at 6:29 am #12054
Well it just stopped working Rf kill soft blocked it and when I run Rfkill unblock wlan0 it says “bogus unblock argument ‘wlan0′” <– I fixed this problem
But nexutil -m2 was throwing socket error,bind error, and connect error.
Now “wash -i wlan0” won’t work it says failed to compile packet filter…
September 29, 2017 at 9:01 am #12055
Let me look into that.
Which model pi and kernel are your using?
September 29, 2017 at 1:01 pm #12059
Raspberry pi 3 model b with Linux Kali 4.9.41-Re4son-v7+
September 29, 2017 at 5:24 pm #12061
I’m currently having an active “airodump-ng wlan0” session and a “wash -i wlan0” running for over 7 1/2 hours and it’s still going strong.
What were you running when it bombed out?
September 29, 2017 at 8:32 pm #12063
I don’t remember what I was running so, I thought and manually removed everything from the directories that I was told to place. And redone the install and now it works. Some how nexutil got removed from /usr/bin/. No clue as to how though.
September 29, 2017 at 8:56 pm #12064
And I just figured out what i ran to make it bomb out.. I ran “service network-manager restart” and it completely messed it up. So had to re do what I mentioned above and it works again.And the only reason I ran the restart service command was because the network would constantly be trying to connect to my wifi
September 30, 2017 at 10:41 am #12069
I usually completely remove network-manager to avoid these things.
I configure my network connections via the command line. Makes it much more reliable and doesn’t do weird things when I don’t want it to.
September 30, 2017 at 12:02 pm #12072
Alright, thanks I might do that. Thank you for the awesome kernel and the help.
October 4, 2017 at 9:54 am #12087
Alright so I just downloaded the latest image with re4son-kernel, and I go to configure the network and network manager doesn’t work. So I uninstall it and try to connect through the terminal but doesn’t work. What do you use to do it? I tried iwconfig wlan0 essid (name) key (password) and it doesn’t work. But I do iwconfig wlan0. It shows my network name, mode managed and access point: not associated.
And how do we overclock on kali?
October 4, 2017 at 1:09 pm #12088
Just follow these steps to set up your wifi:
# uncomment the relevant overclocking line
That should do the trick
March 30, 2019 at 9:28 am #13661
I don’t now what I can do… I have The latest Sticky Fingers… I want use The onboard wifi in monitor mode, i use
iw phy phy0 interface add mon0 type monitorEverything Works fine, on “HDMI screen”… But when I do that, after installing TFT display, it does not work… I tried install on TFT everything separately… Operation not supported (-95)…
nexutil -m2socket errors… I tried install everything after “normal installation with HDMI” on the TFT, but nothing … The Kali Works on a different “partition” on TFT and HDMI? I’m new on Linux, and on Raspberry too… But I want to learn it:) Sorry for my Bad English, i hope you Will understant It… Thank You…!
March 30, 2019 at 11:26 am #13662
Thanks for getting in touch. Which screen are you using? I’ll try to reproduce the error.
March 30, 2019 at 11:56 am #13663
I use Osoyoo 3,5 non-hdmi… I use The Osoyoo “Oficial” driver, becouse with
kalipi-tft-config' Osoyoo does not working... I don't know why... I choosed the Kuman 3,5 too, but nothing... We are speaking about this "display thing"...<a href="https://whitedome.com.au/re4son/topic/installing-on-osoyoo-3-5-inch/#post-13652">Osoyoo 3,5</a> I Remember, one Time is working for me The./re4son-pi-tft-setup -t wave35c -d /root` (waveshare 3,5 Clones), but the monitor mode does not working after installation display… May I choosed the worst display ever…:D So I need your help, becouse I want use The RPI “anywhere”… You now… PowerBank, mini wir. keyboard… So… “mobile” Version…:D Thank you for The fast answer…:)
April 2, 2019 at 11:45 am #13668
Omg! I don’t want write New image to SD card, after every Bad Choice… I have Osoyoo 3,5 , but it does not work… I can’t find any solution on the web… Re4son, please help me!
April 2, 2019 at 1:09 pm #13669
I’m sorry, I use Osoyoo v6.3… Maybe you want this information…
April 4, 2019 at 9:19 am #13673
I thought I had one of those laying around somewhere for testing. Let me check
April 4, 2019 at 12:24 pm #13674
Did you run “LCD35_v” to install the display drivers?
April 4, 2019 at 7:25 pm #13675
April 21, 2019 at 9:56 am #13681
I tryin’ I tryin’ but I can’t find The Solution… Via HDMI The monitor mode work perfectly, but on my Osoyoo 3,5″ nothing… The correct info, What is writed on the back side on my screen is: 3,5 inch SPI TFTLCD, 480*320 16bit/18bit, Version 6.3 2018/4/9… I think, may some things I must enable ín kalipi-config… I was try enable SPI (white screen), I2C (nothing)… Another I forget, but I Think, something i must set in config… SPI, I2C, etc… I tried The official SPI image too, only white screen… I tried The re4son, with SPI TFTLCD driver (LCD35_show) driver, with enabled and disabled SPI, but the same white screen… I don’t know whats The problem… (I want little help for you, I think, on your site on whitedom.com.au/re4son/sticky-fingers-kali-pi/ The wget… https;//….current_kernel is wrong….. Sorry If I’m Wrong) I hope you Will find something for my problem… Thank You, and have a Nice day…!
April 21, 2019 at 9:59 am #13682
I was want to say, wget adress is nőt correct… Sorry…
- You must be logged in to reply to this topic.