Jump to content

Ghostshell

Active Members
 View Profile  See their activity

  • Posts

    113

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by Ghostshell

    Alfa Ap51 Discontinued

    in WiFi Pineapples Mark I, II, III

    Posted

    I have been in touch with Alfa, and have working on a deal directly with them. Due to environmental factors some parts and items may be limited for them. I have made a deal with Alfa directly and will be receiving 100 AP51's or a mix of AP51's and iMesh51's, i will be selling them just slightly over cost once the deal has been finalized and the routers are received.

    Mk3 Firmware V2.1.2

    in WiFi Pineapples Mark I, II, III

    Posted · Edited by Ghostshell

    Have 2.0.1 working on the following hardware, added my script to enable wifi regardless of karma being on or off after flashing

    Fon 2100 A/B/C/D/F

    Fon 2200

    Fon 2201

    Open Mesh 3201A

    Open Mesh OM1P

    **will test the OM2P when the time comes**

    Alfa AP51

    Alfa iMesh51

    Alfa **** ( new hardware i am testing and not sure if everything works yet)

    Mk3 Flashing Guide

    in WiFi Pineapples Mark I, II, III

    Posted · Edited by Ghostshell

    same question here guys.

    Flash process is stalled, likely, because of an incorrect IP listed in the guide. A few posts up it was mentioned to use 172.16.42.100 and below asking if 172.16.42.1 is correct. Can you guys please shed some light on which IP should be used (for the AP51 from the hakshop).

    Cheers,

    Diggs

    To just connect to the pineapple after flash or when you get it delivered from the hakshop 172.16.42.1 is the router IP with the web interface at 172.16.42.1/pineapple, when flashing you can leave your IP dynamic or set it to 192.168.1.100, if you set it to static make sure you follow the last steps and set it back to dynamic, if you are done flashing or got yours just delivered, make sure you have a dynamic IP chosen or set a static of 172.16.42.XXX

    Mk3 Flashing Guide

    in WiFi Pineapples Mark I, II, III

    Posted

    JUST FINISHED!

    Went perfectly, thanks for the hard work on the instructions Ghost, Mr-Protocol and SEB

    From the WinPCap FAQ -->http://www.winpcap.org/misc/faq.htm#Q-3

    Q-3: How can I see if WinPcap is currently running on my Win2K/XP/2k3 machine?

    A: Click on the Start button and then on run. Type msinfo32. The System Information panel will show up. Choose Software Environment, then System Drivers. The entry NPF should appear there. If you launched a WinPcap application previously, the state should be running. Remember that WinPcap should have been run at least one time in order to appear in this list.

    If you have purchased the MK3 from the HakShop and want the simple winblows (oops did I say that?) GUI method use the AP51-flash-gui-1.0-42.exe utility.

    Use the instructions provided by Ghost and go to page 5.

    Once you set your ethernet connection back to dhcp you should be able to ping 172.16.42.1 .... Allow the interface some extra time to fire up (maybe 5 minutes) and connect using the web browser to http://172.16.42.1/pineapple

    Thanks WCS, i will add this to the guide which will help out for sure!

    Mk3 Flashing Guide

    in WiFi Pineapples Mark I, II, III

    Posted

    same question here guys.

    Flash process is stalled, likely, because of an incorrect IP listed in the guide. A few posts up it was mentioned to use 172.16.42.100 and below asking if 172.16.42.1 is correct. Can you guys please shed some light on which IP should be used (for the AP51 from the hakshop).

    Cheers,

    Diggs

    redboot auto uses and is coded with the range 192.168.0.XX it will never use the IP range 172.16.42.XX, that is only for when you go to connect to the pineapple after you have finished flashing as listed as the last step to set your ethernet back to dynamic.

    Mk3 Problem - Interface Disabled

    in WiFi Pineapples Mark I, II, III

    Posted

    One thing to note, during my flashing of about 10 devices i noticed some it took a while for it to fully boot and show interface enabled so i would first, unless you want to re-flash due to other issues, try unplugging the router for about 1 min and then plugging the power back in and leave it sitting/booting for 5min and then check on it. Just a suggestion

    Mk3 Problem - Interface Disabled

    in WiFi Pineapples Mark I, II, III

    Posted · Edited by Ghostshell

    If you are getting stuck at the point where it connects, shows peer ip and your ip and mac's, but goes no further it is not flashing, i would recommend what Protocol said and download the 1.9 FW, place it in a different location like C:\, re-run the flash tool and follow the steps in my guide:

    "Next step is to make sure your router is connected via ethernet to your computer, it should NOT

    be plugged into its power/AC adapter, and lastly you choose the correct interface in the

    Interface drop down in the Ap51 Flash tool.

    Once you have checked the above, hit Go!, once you see the first entry for No Packet!

    Very quickly plug in the power to your router and you should see the following pop up.

    If it does not take the first time, unplug your router, hit Close on the AP51 Flashing tool and then

    reopen the tool, reselect your files and this time as soon as you see the first two lines showing

    reading rootfs and kernel file plug your routers power in very quickly. I during testing have left

    the tool displaying No packet! For over 30sec and then powered my router in and it still worked

    but beware each device has its own mind, for the AP51 router you may need to plug it in very

    quickly after starting the tool."

    Mk3 Flashing Guide

    in WiFi Pineapples Mark I, II, III

    Posted

    Props to you Hfam, pinging it and making sure you plug the power in

    AS SOON as the first 'No Packet' message appears really does the trick,

    seeing messages now so heres hoping! :)

    Right, flashing worked, but now it wont let me connect to http://172.16.42.1/pineapple

    or ping the IP, any ideas?

    SOLUTION: Set the IPv4 settings to automatic, sorted!

    ya going back to dynamic is in teh last part of the flashing steps, always a kicker

    Mk3: Atheros Based Files To Flash

    in WiFi Pineapples Mark I, II, III

    Posted · Edited by Ghostshell

    on my OM1P i turned on all services except airmon-ng, after a few hours i went to check on it and it looks like it rebooted itself, now just running karma and urlsnarf, will post as i test, urlsnarf still will reboot the Fon2100 since it runs out of RAM. going to vegas for the weekend and i plan to bring my OM1P, 3201A and 2201 for testing, maybe the 2100 too, cant wait to see the airport results tonight

    Update: after turning karmer and urlsnarf on i can no longer access the web interface, its still on, per the code the wifi light is on so karma must be on, will try a power cycle and see what happens

    Update: currently trying a 3201A, going to start the services karma and urlsnarf and let it run for a few hours.

    Update: i to only see data in the ARP and DHCP logging section, nothing else, this happens on all my devices i test, 2100 A/B/C, 2100 D/F, OP3201A, OM1P, 2201, and my 2202.

    Update: have an Open Mesh 3201A fired up, one weird thing is that this out of all my devices responds the quickest and seems to work the best even though my OM1P has better HW, have the following services up Karma, URLSnarf and NGrep, no data showing in both but i did just fire them up and connect the pineapple to internet, will check the data in about 30min or so and also to see if i ran into the same issues as last night, as far as the different range of IP on the internet SSID, i thought that was intended and a good idea so no one could access the interface at all, but i do understand how it could be useful, with the non karma SSID, pineapple, i can access the interface and get my services started

    Update: had my 3201A MK3 crash and had to power cycle, same happened to my OM1P, services running were karma, ngrep and urlsnarf, after reboot ran just karma and ngrep and after a few clients connecting it started to lag and almost crash if i didnt stop ngrep, now its running as normal with just karma, per the data and logs it looks like ngrep running is causing the router to crash and freeze up, but resources are not running out since it doesnt reboot itself, now trying karma and urlsnarf

    Update: nope, karma just died, it looks like urlsnarf is causing the problem, retrying karma and ngrep again, even though no data shows for ngrep, this crash took only a few minutes.

    Update: narrowed down the reboot cause, if i plug any of the MK3 routers directly into a switch/router to give it internet it causes the reboot, if i leave it unplugged it stays up and catches clients, have been watching it since the last update. I have not tried the normal way to give it internet via connection sharing, will try that tonight in the airport and post the results...

    Update: added a GPIO script i created so i can see if wifi is on regardless if Karma is started to see what happens after it crashes, so far it works on boot

    Update: while at my hotel i put up a 3201A Open Mesh MK3, just started Karma and URLSnarf, when i got back All services where off, but the interface was still enabled.

    Note: usually when i start karma and when it switches to the karma SSID and i connect it issues a IP other then the non Karma SSID 172.16.42.XXX, now with Karma running when i connect to SSID internet i still get the 172.16.42.XXX IP and can connect to the pineapple web interface, i am using my linux laptop vs the Winblows 7 laptop i used before to admin the pineapple. Can anyone confirm this IP issued?

    Update From Weekend: i used one specific pineapple all weekend while at the airport twice and while at my hotel, the weirdest thing that happened was that while leaving it running for two days if i didnt stay connected via cable it would i believe reboot, i didnt get to check uptime, if i didnt stay connected or connect via wirless when i came back at the least 2 hours later it would show all services off including karma. so i now have a router with great logs and other info to possibly identify any issues during a 2-3 day runtime. other then the possible reboot all services ran, but i never saw any data in the Ngrep, URLSnarf log areas, NGrep is a known issue and URLSnarf i didnt run/try prior to 1.9 so it could have worked previously.

×
×
  • Create New...