skunk.ink Posted July 4, 2014 Share Posted July 4, 2014 I'm trying to install Kali on my old MacBook Pro (late 2006) and I am unable to connect to my WIFI. I am thinking that it may just be my network card is old and acting up as in OSX it seems to also have problems connecting, but the strange thing is that I have no problem seeing my WIFI network, it's just trying to connect that causes me problems. I have double checked that the password is correct about 5 times so I am now at a loss. I also read that old macbooks can have connection problems if they are upgraded to OSX 10.6.5 and that reinstalling the old firmware for the network card can solve this problem, but that only solve my problem in OSX. Does any one have any suggestions? I could just continue the install over a wired connection but this problem is really bothering me, and really, whats the point of installing Kali if my wireless card won't work? Quote Link to comment Share on other sites More sharing options...
digininja Posted July 4, 2014 Share Posted July 4, 2014 Have you tried disabling security on your AP to see if that helps? You could also try an external wifi card, see if that works any better. Quote Link to comment Share on other sites More sharing options...
skunk.ink Posted July 4, 2014 Author Share Posted July 4, 2014 No I haven't tried disabling security yet, I'll do that. I don't really want to buy an external wifi card since it's a crappy old computer, just wanted something to play around with. I know, I'm cheap haha. Quote Link to comment Share on other sites More sharing options...
digininja Posted July 4, 2014 Share Posted July 4, 2014 I'm suggesting the card for debugging not permanent use. If that card with the same config can connect then it implies your card is bust, if it can't then it suggests your config. Quote Link to comment Share on other sites More sharing options...
sedpaffy Posted April 1, 2015 Share Posted April 1, 2015 I had a similar problem on my mid 2009 macbook pro. I could see networks in Kali but not connect to my home's wifi. At one point I actually was able to connect and I tried to run reaver then (putting my card into monitor mode, my own mistake after I learned the chip didn't support packet injection)... But when I tried to bring back up my wlan interface I couldn't connect again to my home AP. After a few days I thought about re-installing kali but instead, booted into my mac and deleted my AP info from System Preferences --> Network --> Wifi --> Advanced Re-booted, booted back into Kali and success! Tested a couple of other times by saving my AP's details in OS X and failing to connect in Kali - but haven't exhausted all possibiliites. Just a suggestion anyway! Quote Link to comment Share on other sites More sharing options...
digip Posted April 1, 2015 Share Posted April 1, 2015 I had a similar problem on my mid 2009 macbook pro. I could see networks in Kali but not connect to my home's wifi. At one point I actually was able to connect and I tried to run reaver then (putting my card into monitor mode, my own mistake after I learned the chip didn't support packet injection)... But when I tried to bring back up my wlan interface I couldn't connect again to my home AP. After a few days I thought about re-installing kali but instead, booted into my mac and deleted my AP info from System Preferences --> Network --> Wifi --> Advanced Re-booted, booted back into Kali and success! Tested a couple of other times by saving my AP's details in OS X and failing to connect in Kali - but haven't exhausted all possibiliites. Just a suggestion anyway! sounds more like you needed to just change back to managed mode and clear DHCP and re-authenticate, either manually or via a connection manager. Monitor mode, will not let you connect to the AP, only capture packets. If using the aircrack suite, use airmon-zc to to start monitor mode, which will give two interfaces for the same card, then change it back/stop monitor mode with airmon to go back to normal monitor mode. If going manual for a single adapter, just change it from monitor mode back to managed and you should be all set. Quote Link to comment Share on other sites More sharing options...
Catch22 Posted April 2, 2015 Share Posted April 2, 2015 Make sure you have the right drivers. Linux installs don't always find the right drivers and that can cause hell! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.