Open na-ji opened 4 years ago
From the crashlog, it‘s not really possible to see where the error occurrs exactly and I never encountered this issue on the mac‘s I tested it on, so I can‘t do much about it.
So only thing you could do is launch it via xcode (as root!) and set many many breakpoints to identify at which line exactly the problem is.
Also getting the same crash... Will see if I can find anything useful.
Issue seems to be with pcap_inject call in ANInterface. Debugging is hard because it detaches after the authentication prompt succeeds.
@thermogl That why I said "as root!". Since when you launch it via xcode as root, it won't show the elevation prompt as its already root
Even just trying to step into pcap_inject results in the crash. Problem with the library perhaps.
pcap_sendpacket has similar issue. Difference is indefinite hang instead of crash.
Let me put my 2 cent on this issue, the issue only happens with all mac models from 2018 and on. All 2017 and prior models work, so it seems to be a card issue.
@MayhemGang Probably, bc all my testing Devices are pre 2018. But even the newer one's should technically support monitor mode, so injecting own packages should be possible, generally speaking.
@anonymouz4 how can I jam a network and stay connected to the internet. It was possible in the previous version. Is it not on this version?
I have this issue on my air 2019. xcode start as root but have a crash osX and restart pc
Same problem with my macbook pro 2018
Having the same issue with T2 MacBook Pro 2018. Click, wait 2 seconds, kernel panic.
Let me put my 2 cent on this issue, the issue only happens with all mac models from 2018 and on. All 2017 and prior models work, so it seems to be a card issue.
@MayhemGang this makes sense.. but if this is a hardware problem then we are doomed.
so i did a little research, for the 2019 MBP entry model, the wifi+bt module according to the iFixit teardown is Murata 1SA 339S00616 SS9521026 this is as far as I found... I can't pull out the datasheet of this chipset, perhaps this is Apple exclusive and the datasheet is not for public use.
It could be a firmware or driver issue, too. In that case, there's hope that Apple pushes a fix eventually.
@thermogl which mac yr and model are you running this on?
Even just trying to step into pcap_inject results in the crash. Problem with the library perhaps.
pcap_sendpacket has similar issue. Difference is indefinite hang instead of crash.
I unfortunately could not boot my older mac to try this on... I'm stuck with the 2019 MBP.
I was able to inject with a dumb demo program (read a packet and inject it back), but it wasn't in monitor mode. With JamWiFi I get the crash. I'm not sure the model (I'm quite noob with Mac), but at least I know it's Mojave.
I was able to inject with a dumb demo program (read a packet and inject it back), but it wasn't in monitor mode. With JamWiFi I get the crash. I'm not sure the model (I'm quite noob with Mac), but at least I know it's Mojave.
hi @Oppen can you share this demo program with me? thanks!
I have the same problem on my MacBook Pro (13-inch, 2019, Four Thunderbolt 3 port) but I will test this on my 2016 MacBook Air soon once this pandemic is over.
@acheong08 It crashed on my MacBook Pro (13-inch, 2019, Four TB3) but it worked on my friend's MacBook Pro (13-inch, 2017, Four TB3) tested today
ohh by the way, is the older version(JamWiFi without maintence) not functioning on newer MBP? I tried but the "Do it!" function never worked.
Guys, If you take a look at the README, it clearly says that devices build 2018 and later seem to crash, so there's no need for everyone to state that individually.
And if you post Kernel Panic Reports, please set your boot-args to keepsyms=1
, bc I'm not gonna resolve every symbol manually.
I think it is useful, actually. The developer stated a lack of hardware for testing, so knowing who else may help on testing is definitely useful.
@anonymouz4 let me know if I can help in anyway I have an MBP 15,1
I have tested other deauth tools on my MacBook Pro 2018/2019 and all of them crash my computer. Other tools such as Reaver and Pixie Dust which requires packet injection also crashes the computer. It seems like packet injection and deauth won't be working anytime soon for us.
This isn't a software issue
It's a hardware issue
From the crashlog, it‘s not really possible to see where the error occurrs exactly and I never encountered this issue on the mac‘s I tested it on, so I can‘t do much about it.
So only thing you could do is launch it via xcode (as root!) and set many many breakpoints to identify at which line exactly the problem is.
I debugged and it crashed by this block
@synchronized (writeBuffer) { [writeBuffer addObject:packet]; }
in file ANWiFiSniffer.m
Hello,
When I start de jamming after selecting the client, the app crash my whole OS. Here's the OSX report of the crash. I saw a lot of people had this problem, but no issue were created. So here it is.
I have a MacBook Pro (16-inch, 2019).
Thanks!