cypto Posted March 27, 2013 Share Posted March 27, 2013 (edited) New user to the pineapple and wifi pen testing in general however have worked with php and servers for a couple years now. info. OS: currently Windows 7 but bootable into blackbuntu (just prefer winscp for moving files) Pineapple IV version: 2.8.0 originally came with 2.7.0 however updated using the .bin file download. Pineapple is also pointed directly to 172.16.42.42 / 255.255.255.0 in the ipv4 settings under local area connection porperties. The problem. Pineapple has been working fine ran the "hello world" nancat script, however the "List available Infusions (aka modules)" link comes up with the error... "Error connecting!Please make sure you have an internet connection." as with the update over the net link. The pineapple is turned on connected to ethernet using the PoE port on the rear and the PC is connected to the net via wireless 802.11n with working internet access. However just can't seem to find out why the pineapple gui is failing to use it. Forgive me if this is a novice mistake but have read through both the quickstart guide/50 page guide and the wiki, very possible it might be something I just missed. -Cypto Edited March 27, 2013 by cypto Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted March 27, 2013 Share Posted March 27, 2013 Have you double checked your ICS (Internet Connection Sharing)? Example: pinging google.com and so on? Quote Link to comment Share on other sites More sharing options...
cypto Posted March 27, 2013 Author Share Posted March 27, 2013 After looking over all the settings, Ive managed to resolve it had the subnet as 255.255.0.0 instead of 255.255.255.0 just a typing error. It's funny you start going to almost derastic measures to fix the problem only to realise it something very simple. Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted March 27, 2013 Share Posted March 27, 2013 After looking over all the settings, Ive managed to resolve it had the subnet as 255.255.0.0 instead of 255.255.255.0 just a typing error. It's funny you start going to almost derastic measures to fix the problem only to realise it something very simple. Been there many times... Congrats on getting it resolved :D. 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.