Sebkinne

Make sure you configure ngrep correctly. As far as I know the current config fails for me too. I will add it to my list of fixes. See the front page for a list of upcoming fixes. Regards, Seb

When you say "done" you mean booted into the firmware? If so, "opkg install <package name>" Most packages are installed already though. How are you connected to the router? The "OpenWRT" Wifi issue is almost resolved, I am just working out a couple more kinks. You should still be able to SSH in, that is the first I hear of it not working.. About the wifi light, that may not even turn on, I would have to script that in. Could someone with a working MK3 confirm? Best, Seb

I would appreciate it if you would edit your posts, otherwise this thread gets so cluttered no one will find anything anymore. There is no need for telnet, SSH is enabled from boot. Regards, Sebkinne

Can you try not assigning yourself a static IP address? See if you get one from the MK3's DHCP pool. Maybe something went wrong there. Otherwise, you can always try re-flashing the router, that should work. Preferably I would want to fix this issue though. Try to do the above and report back! Best, Seb

I saw this happen before in one of my first attempts at porting the firmware. In my newest firmware urlsnarf works fine. I can try to dig out the change I made if that would help? Best, Seb

The page holds the information contained in Post 1 and Post 2 here, so as far as I know it should work. Alos, httpCrash, the instructions for microRedboot differ slightly. They require it to be: fis create -e 0x80041000 -r 0x80041000 linux Instead of fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7

If you check my post #2 in the beginning, you will see that the spacing is correct there. The guide has the values I posted, so yeah, I was wondering why people said it didn't work. @Alison, it should work, and as you can see httpCRASH got it working. Regards, Seb

If you don't mind, I recommend you flash my firmware. You can find it in this forum. That will install all of the packages you need for you. Best, Seb

@All, I will be fixing the issue with the "OpenWRT" SSID showing and not allowing you to connect. I am already working on a new version. @Stuffses In regards to why the index.php files are there, well, they are part of the MK3 firmware. Not only that, but turning DNSspoof on, that index.php takes care of everything for you. Just add files into the folder (such as facebook.html) and it will redirect people there. I suggest people leave those files intact and simply navigate to http://72.16.42.1/pineapple @httpCrash Interesting, can you pull up the pineapple web interface? In regards to testing firmware, write me a PM on here, that could be useful! Thanks. Regards, Sebkinne

@httpCRASH, Space problems I think I fixed in the firmware. The firmware I put up includes all the things you need, you do not have to patch hostapd. Regards, Seb

Wifi starts automatically now. Or at least it should ;) Can you confirm that?

This sounds strange. Instead of "free" run df -h, that makes it more readable. Try out my newest firmware, I trimmed it a bit, hope it fixes some issues!

Hm, I misread the description. Still, what settings would there be that can't be re-done?

Great idea! I will experiment with this for a bit, such a useful thing!

I think hop wise, it will be hard to tell for anyone not experienced. If you know what you are looking for and do a traceroute and start investigating each hop then yes, you will know. It all depends on the set-up you have though. Karma for network shares / printers. That sounds like an interesting idea. I believe something similar exists in Metasploit. I think it targets single clients though. I sadly don't know enough about that..

@allisonmagic Do you have a web server installed at all? Sorry if I misunderstood, but it seems like you haven't installed all of the packages required for all of this to work. Darren has a long list of packages on the wiki you will need to download, transfer onto the router and install using "opkg install *". If you have done all of that and it still does not work, report back! Best, Seb

I would suggest you re-flash the firmware on the device. Depending on what you want, there are different tutorials around here. That way you have a clean install and an updated firmware. (Most likely). Regards, Sebkinne

@Darren Yeah, it fixes the symlinks, fixes the wifi and sets the password to "pineapplesareawesome". I was originally going to do "pineapplesareyummy" but it slipped my mind and it was too early to recompile. I will do later ;) @Vile, It reboots the 2200? That sounds odd. While the OM1P does have more resources, it should run just fine. Could you let the router run for a while and see if it reboots on its own? If it does not, can you see if all features make the 2200 reboot? If so, could you start the services manually and see if you get any errors or if it crashes immediately?

Great to hear that! I have released a new and updated version of the system, now there is no need to configure anything after flashing! Just be patient and wait for it to fully boot. Edit: I have a new version I am working on eliminating the reboot. Just takes too long overall. Best Seb

What Pineapple do you have? Seb

Ah, I can't believe I forgot that. I was certain that I had commented that out! I will do so and re-up the files. I used your config files for wifi (and some others) to keep it as close to the MK3 as possible. Give me a few minutes to recompile! Seb

Thank you Darren, If you run into any issues, let me know, I can recompile the tree for the different systems. Best, Seb

Flashing Instructions: Method 1: Download an app called Freifunk EasyFlash and use this to flash. It automates the process for you and gives clear instructions. Method 2 - Redboot: Credits to Digininja for the script: Just follow the instructions here http://www.digininja.org/jasager/installation.php Method 3 - Manual way: If you decide to do this, you know what you are doing. There is no need for me to explain. Method 4 - If you have microRedboot: 1. Boot your router into redboot (OM1P: Disconnect from power, hold reset button, reconnect, keep holding for 2 seconds, release). 2. Set your interface's IP to 192.168.0.100 (ethernet interface) 3. Telnet into 192.168.0.1 port 9999 4. Set up a TFTP server (plenty of guides out there) 5. Follow these instructions: #Redboot reflash guide ip_address -h 192.168.0.100 fis init #Load and flash the kernel load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma fis create -e 0x80041000 -r 0x80041000 linux If you have the normal redboot please use the following line: fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7 #Load and flash the filesystem #This can take 5 minutes or more load -r -b %{FREEMEMLO} openwrt-atheros-root.squashfs fis create -l 0x6E0000 rootfs reset I will be neatening this up and adding more detail later. This is just to get you guys started! Regards, Sebkinne

Dear All, First off, let me apologize for earlier this year, I promised to release my work on the OM1P work on things and just didn't ever really get the chance to. Now that MK3 has been released, I thought I would build the MK3 interface into my previous work. The files in the link below are your complete set up. No need to install extra packages or awkwardly copy files over! So, without further ado, here are the .lzma and .squashfs files: 1.9 Release I do not accept any responsibility if you brick your device. I doubt you will but flashing is always risky! The files should work for the MK2, MK3, OM1P and most Atheros based routers. If you have a different router and want to get this firmware, let me know and I will see what I can do. After flashing these two files, the pineapple is available under 172.16.42.1. The first boot after flashing will take around five minutes, depending on your device, maybe longer. It is executing boot scripts configuring itself. Don't worry though! After about five minutes, ssh into the router. If you can't ssh, wait a bit longer. It will work. When you ssh, use "root" as the username and "pineapplesareyummy" as the password. To change the password please execute "passwd" and change it there. There you go, you should be all set up now! I hope you enjoy this and accept my apology ;) Credits go to Darren and Robin for Karma and MK3. Thank you guys for your amazing work! If there are any questions, do not hesitate to ask. Best Regards, Sebkinne Changelog: 1.0: Initial Release 1.1: Fixed Mac address in /etc/conf/wireless 1.2: Added boot scripts 1.3: Enabled SSH by default. Set root password. 1.4: Sped up boot process. 1.5: Eliminated reboot + added macchanger (Not added to the startkarma script though, I will be adding a toggle / I am sure Darren has thought of that) 1.6-Beta: Fixed startup WIFI. (Not tested yet) 1.7: Protected pineapple interface, fixed wifi, added tweaks. 1.8: Added wifi LED. Note: Wifi LED will only activate when karma is activated. Normal wifi will not turn LED on. 1.9: Fixed the "restore factory defaults" in pineapple interface. Upcoming / todo: *Look into ngrep not working *Fix de-auth webinterface *fix wifi mode to g

Simply "vi httpd.conf" and remove the unwanted line. Try then, if it still does not work, try obtaining a tarball containing the php files. Seb