Jump to content

httpCRASH

Active Members
  • Posts

    107
  • Joined

  • Last visited

Everything posted by httpCRASH

  1. set your computers interface to 192.168.0.100 start a ping -t 192.168.0.1 connect pineapple to power when you see the first ping reply telnet to 192.168.0.1 port 9000 (have telnet ready so you can telnet excact when you see the ping) now you are in redboot... then follow seb's guide in the start of this threath Seb>> it still amazes me that you have been able to install all the pakages, and still have 3,7MB of free space, is your surname potter? :D
  2. okay.. just wanted to point out that when i blindly followed the guide (yes i know, think think think) and used the linux i ended up with a pineapple that would not boot, but just stop at redboot.. after changing it to vmlinux.bin.l7 i got a working MK3
  3. damm... overlooked that entirely... sorry mann.. didnt see that you already had the rigth values for fis create in this threat.. but still had to change the second line to: fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
  4. i just followed that guide.. it needs to be modified a little, there are 2 lines missing a break in the mittle.. it says load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma fis create -e 0x80041000 -r 0x80041000 linux and should say load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma fis create -e 0x80041000 -r 0x80041000 linux and the same for the other file.. and mayby change the second line to: fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7 (or change the boot script) :) EDIT: and YES, it just worked for my MK3 so i was missing the rigth values for fis create yesterday, with the ones from wifipineapple.com the MK3 install was pice of cake.. :D there is ofcourse still the "openwrt" SSID error, but seb said he was working on that, so i would say this works perfect...
  5. on the FON2100 i get both SSH and pineapple web interface... on the AP51 i get none of the above, but as said, i can ping the IP you gave it...
  6. FON2100 i have the exact same errors with a MK1 flashed with this firmware, everything seems to work, ecept for showing the right SSID, and letting me connect... havent had the time to play with the wireless config yet... AP51 on my MK3 i get no SSID at all, and no SSH, even though i can ping the router on 172.16.42.1 (so i know that its running with Seb's firmware) Seb>> if you need a newer version tested, just say so, i dont mind re-flashing my routers.. i'll just wait with my pentesting :D
  7. it starts up, i get an openwrt SSID, but cant connect to it, have tried a couple of clients :) EDIT: i just realized that i should see the "pineapple3c" SSID, and not the openwrt right? but i only see the openwrt with a clean install
  8. hmm, but your firmware is for MK1 and MK2 rigth? when im flashing my AP51 i only got it working with the openwrt-atheros-vmlinux.gz file, and NOT openwrt-atheros-vmlinux.lzma so my guess is that i need the .gz file from the openwrt version you use to get your version working on my DIY MK3?? :) EDIT: have just tried with both your files, and with switching out the lzma file with the gz file from http://downloads.openwrt.org/snapshots/trunk/atheros/ (guessed that you used this version?) both attemps failed.. i get ping on 172.16.42.1, but cant connect to ssh or web...
  9. anyone els having space problems when adding phising sites? the install and *.ipk install uses so much space, that i have very little space left for phising files, witch i find a bit weird. When i look at my old fon2100 installed with the new firmware from sebkinne there is allot of free space i also still need to find out how to patch hostapd with digininjas patch... but rome wasnt build in a day
  10. i would think none... but thats not for me to decide.. i just flashed my old mk1 (FON2100) with your firmware from here: http://forums.hak5.org/index.php?showtopic=23575&pid=189896&st=0entry189896 and if we can solve the wifi not starting up automaticly, this might also be the rigth way to go for him to get an updated firmware ;)
  11. his description of the topic is "Trying to recover a pineapple settings", and a re-flash will destroy all settings, so didnt think that was an option :D
  12. try connecting it with a crossover cable, and use wireshark on that interface, if it has an ip in another range that the one you expect you can see the rigth ip in the data it sends..
  13. i know its the atheros files, but wich files exactly did you use for kernal & rootfs? i thought i was using the rigth ones, and semi-bricked mine :D so have to wait for my console cable to arrive, but would be nice to have everything sorted out in the meantime :) EDIT: okay, you just gave me a good idea there, just started wireshark, and is also getting allot of data from the AP51... and stupid me had not seen that it was actually flashed ok, because it was not on the ip i expected, and not starting wireless by itself...
  14. Have you found out how to get jasager running? i get this when trying to install the patched files from digininja root@Pineapple:/tmp# opkg install *.ipk Package kmod-madwifi (2.6.30.10+r3314-4) installed in root is up to date. Unknown package 'jasager'. Collected errors: * pkg_hash_fetch_best_installation_candidate: Packages for jasager found, but incompatible with the architectures configured * opkg_install_cmd: Cannot install package jasager.
  15. nice, im waiting for a USB to TTL cable that i orderet... dont want to mod the one i have made for my old FON, might still need it at some point :D cant wait :D
  16. just need to ask, do you mean compile from source and flash that, or flash the lastest prebuild? :)
  17. do anyone know the pinout of the TTL connecter in the AP51?? have tried googling it, and is only getting fon and fon+ pinout (even though im searching for "alfa ap51 pinout")
  18. nope, im looking aswell, found an AP51 from a german shop, and would like to set a MK3 up my self, its just to damm expensive to have anything shipped from the US when you live inside EU (customs), but also want to support the show, so going to buy alot of stickers if we get the MK3 firmware/setup... they are going under the radar at customs
  19. Im using the build in VPN client, set to L2TP, and yes, the server should be set up for this as well, have followed a guide to the Letter, but dont know enough about this to be shure that i have set it up correctly... My main reason for setting it up internaly and then routing it out is that All the guides i have found show you how to set VPN clients up in the same range as your network card in the server, and dont show anything about making a NAT between the VPN ussrs and an external IP. My first idea was to put it directly on my server in a hostingcenter, but after alot of trial and error i gave that up, and went for the other aproach, to try and get a working internal setup that i could route out to an external IP first, so that it would be easier to follow a guide
  20. Hi guys, hope that someone in here uses openswan and can help me... Im setting up an VPN server with 2 goals, first of all getting my iphone/ipad a secure gateway to the internet when on the road.. second to let the the iphone use my own DNS server while using a 3G connection (so that i can change the reply to an app by sending the requests from the app to my own webserver (but thats another story)) back to the VPN, im setting it up on a ubuntu on 192.168.3.161 im testing with an ipad from the same lan, to be shure not to get nat/firewall issues ipad has 192.168.3.100 I have tried some different guides, and of-course goggled all errors i have seen, but now i am stuck, got the following output from my auth.log and cant figure out what to change to solve this :( Nov 20 17:49:45 sm-laptop pluto[5469]: ERROR: asynchronous network error report on eth0 (sport=4500) for message to 192.168.3.100 port 4500, complainant 192.168.3.100: Connection refused [errno 111, origin ICMP type 3 code 3 (not authenticated)] Nov 20 17:50:55 sm-laptop pluto[5469]: last message repeated 7 times Nov 20 17:51:06 sm-laptop pluto[5469]: ERROR: asynchronous network error report on eth0 (sport=4500) for message to 192.168.3.100 port 4500, complainant 192.168.3.100: Connection refused [errno 111, origin ICMP type 3 code 3 (not authenticated)] Nov 20 17:51:15 sm-laptop pluto[5469]: "L2TP-PSK-NAT"[1] 192.168.3.100 #1: DPD: No response from peer - declaring peer dead Nov 20 17:51:15 sm-laptop pluto[5469]: "L2TP-PSK-NAT"[1] 192.168.3.100 #1: DPD: Clearing Connection Nov 20 17:51:15 sm-laptop pluto[5469]: "L2TP-PSK-NAT" #2: deleting state (STATE_QUICK_R2) Nov 20 17:51:15 sm-laptop pluto[5469]: "L2TP-PSK-NAT" #1: deleting state (STATE_MAIN_R3) Nov 20 17:51:15 sm-laptop pluto[5469]: "L2TP-PSK-NAT"[1] 192.168.3.100: deleting connection "L2TP-PSK-NAT" instance with peer 192.168.3.100 {isakmp=#0/ipsec=#0} Nov 20 17:51:15 sm-laptop pluto[5469]: ERROR: asynchronous network error report on eth0 (sport=4500) for message to 192.168.3.100 port 4500, complainant 192.168.3.100: Connection refused [errno 111, origin ICMP type 3 code 3 (not authenticated)] Nov 20 17:52:33 sm-laptop pluto[5469]: last message repeated 2 times
  21. but for us that likes to get our hands "dirty" this would be great fun, even only with some notes the horrible part would be to find an AP51 to play with uh, and maybe a pinout for serial connecter would also be nice :D
  22. hmm, is the AP51 not a 12v router? how did you get it to run on a 4xAA battery pack? :)
  23. hmm.. i have only seen a tutorial for flashing the old pineapples, is there a new one out for the MK3?, or have anyone confirmed that the old tutorial is also compatible with the MK3? i dont know if the new one has a diffrent size flash thats need other parameters when flashing, but my guess is that Darren will give you the info for flashing it the right way (if it is different from the old) :)
  24. you do normaly have a warranty on new hardware, but that is voided if you fuck the firmware up your self, for an examble, if you updating your BIOS in your PC and get a power loss during the update so your BIOS is fucked you cant get a new one or a refund either... when that is said, even if you cant connect/reflash it from the network, most routers have some pins (or soldering points) on the inside you can connect to a com port and still save a bricked router :)
×
×
  • Create New...