Fern issue

[Pandemic]

Hi,

First time poster here. I just installed kali linux 2. I'm having an issue with Fern wifi cracker. It'll set wifi into monitor mode and then I'm able to click 'scan' for APs. Thing is, after that, no APs come up in either WEP or WPA. I have a test router about 6 feet away. This all used to work when I was running Kali 1. I'm also able to see various APs in the wifi list. I was considering an uninstall/reinstall but thought I'd come here first to see if you have any suggestions.

Thanks

[Max555]

I'm having the same issue and have also noticed that wan0 becomes wan0mon and every refresh or use of airmon-ng adds another ext e.g. wan0monmonmonmon

[aGravity]

I've never used Fern before reading this post but can confirm I get issues with any wireless adapter I use, post-Fern. Fern works OK (for what it does) but I can't connect to any wireless APs after exiting Fern. I don't get wlan adapter renaming issues, they just refuse to connect to any valid access point unless I first remove then re-add the adapter...

RE Fern; if you're proficient with the aircrack-ng suite are there any benefits (besides automation) to using it? Is it kind of like wifite, but with a GUI?

Cheers, aG

[Pandemic]

I'm having the same issue and have also noticed that wan0 becomes wan0mon and every refresh or use of airmon-ng adds another ext e.g. wan0monmonmonmon

I noticed that too.

[SamNeuer]

After updating to Kali 2 I do have the same issues. After starting Fern WIFI Cracker 2.2 I select Wlan0, messages appears "Monitor Mode Enabled on wlan0mon", Scan is "Active"
but it doesn't find any WEP or WPA networks. Checking with ifconfig wlan0mon is up, also some month ago with an older version, it found a lot of Wifis in my area, I was easily
able to crack my WiFi on the same machine i'm working right now. Anyone has some tips for me who to make Fern Cracker work again?

[cartof]

I have the same issue but i had it working a few times. Forget all the networks that you connected in the past restart and try fern again. After crack you need to restart it won't connect like aGravity said....or just use wifite

[savioboyz]

Hello Everyone,

Im savioboyz the author of Fern Wifi Cracker, your issues have been acknowledged, ill start work on fixing the issues, a new update should be up before next week.

[grid]

Thanks for the response, savioboyz

[savioboyz]

@Grid Thanks

The bugs has been fixed, Please update to version 2.3

You can download the update using the update button on Fern or simply checkout via SVN or GIT

SVN checkout URL:

https://github.com/savio-code/fern-w...n-Wifi-Cracker

GIT Clone URL:

https://github.com/savio-code/fern-wifi-cracker.git


DEB installers will be available for download soon

If you face any other issue, please you can let me know on this thread or through the issue tracker on the github

Regards

[grid]

Appreciate the quick work, savioboyz

[alnemir]

Update button doesn't work: no new update is avail

[destinyflynn]

Good day,

I have 2 user accounts on my kali linux, on the root account fern wifi cracker is working. On the 2nd account with the same admin account I get this error

root@kali:~# fern-wifi-cracker

(process:5557): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(python:5557): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Qt: Session management error: None of the authentication protocols specified are supported
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
X Error: BadAccess (attempt to access private resource denied) 10
Extension: 130 (MIT-SHM)
Minor opcode: 1 (X_ShmAttach)
Resource id: 0x140
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0000f
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0000f
X Error: BadAccess (attempt to access private resource denied) 10
Extension: 130 (MIT-SHM)
Minor opcode: 1 (X_ShmAttach)
Resource id: 0x140
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0001a
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0001a
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0000f
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 2 (X_ShmDetach)
Resource id: 0xc0001a
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0xc0000f
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension: 130 (MIT-SHM)
Minor opcode: 2 (X_ShmDetach)
Resource id: 0xc0000f

Need some assistance

[bigbiz]

Fern uses aircrack in the background try setting your moniter mode with terminal first then restart fern.tick little box under attack tab next time to see what I mean.