Jump to content

csystem

Active Members
  • Content Count

    33
  • Joined

  • Last visited

About csystem

  • Rank
    Hak5 Fan +

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the info and the links!!! I guess I'll have to buy a t-shirt. :-))
  2. OK, will you allow me a rebuttal? I agree, OSS should always be free. However seems obvious to me the new firmware Mk4 release is being delayed, at least to non-paying customers (who do not buy the retail package which is released presently). Understandably, the hard facts are the forum servers and Darren and company have significant expense in their operation. However a purely pay for download would indeed be chilling and I do not support that. So if a membership program were in effect it would allow access to the latest project code, which would still be made available freely later to
  3. Greetings all: This very subject has also been on my mind. I am an ardent DIYer and have built two pineapples to date. The hardware for the MK4 **is** available if you know where to look, and I don't want to undercut any of the hard work of the devs and the hakshop by posting details. Yes I am going to build a MK4 from an OM2P (not the same HW as the MK4) when the fw becomes available but I will have to wait until that time. Darren and the devs have put in a lot of work and should be compensated for their work, I agree. But here's my dilemma: Buying at retail a fully plug and play uni
  4. M1k: The TP link 703 is a similar board as the Hornet, 32mb ram 4 mb flash. Did you have any luck swapping out the flash chip, which one did you use for the 8 mb? Thanks!
  5. To flash over serial this works (see section 5) HERE But you will need a pinout diagram: +---+ |GND| +---+ |TXD| +---+ |RXD| +---+ |VCC| +---+ +-----+ +-----+ +---+ |Power| | LAN | |Ant| Note when you issue the transfer command when logged into Redboot you will still have to initiate the ymodem transfer on your terminal program, its not automatic like when using an IP based transfer. Because your USB/serial adapter requires drivers some of them do not work well for serial transfers. If your chip is FTDI it should work. Or find a vintage PC with a serial port. Go
  6. If your project would work with an older version (fon with 16mb ram, 8 mb flash) I have it flashed with Mk3. Works for karma and MITM, but can't run URLsnarf because of the smaller RAM. Heatsink mod and fan installed. Mint condition (except for the mods). 25.00 shipped priority mail. Photos if interested.
  7. Some info..mostly a photo... on the MK4 HERE
  8. Seb will be testing soon for OM2P. (802.11n) Different SoC, 7240 I think, also uses U-boot instead of Redboot. I was not referring to the current 2.01.
  9. If you can't flash with the gui app or using refboot.pl and tftp, you will have to re-flash using a serial connection and ymodem. How did you flash before you had the problem? After you reboot the pineapple, can you ssh into it? You may be better off with reflashing. good luck
  10. Mr Protocol is correct however I know the actual temp of the 2315 chip is higher still, unless you add a heatsink. The foam tape the mfr placed on the chip below the RF shield to conduct heat is very inadequate, imho. Then again, with the new firmware for the 7240 routers (om2p) coming???? its not all a big issue.
  11. OK, if the karma SSID and the non-karma SSID are the same here (yes I should have read the notes :-() here's my question: I edited the ssid in the wireless config non-karma mode editing window (named it FreeWifi,) clicked the "update wireless" and the SSID indeed changes in normal mode, after a reset. I then enabled Karma on the pineapple, and disabled my normal access point, (unsecured, SSID is homewifi) and set my phone to connect to "homewifi" which was in my wireless access point list. Yes, the phone connected to "homewifi" . As the pineapple was then the only access point in range, I
  12. I don't know if this may help, I am having the same problems changing the ESSID through the web interface. V. 2.01, OM1p. I looked at the /etc/hostapd/karma.conf, it was **missing**, I found a karma.conf.old, renamed it back to karma.conf, manually edited the ESSID, reset, and all is fine now. Possibly the web UI is not writing the new file? I was using Firefox on BT5R1 when I tried changing the ESSID, btw. Anyone else have a missing karma.conf after making the change?
  13. Big improvement in temps. If you cut the RF shield carefully, it will still make contact with the heatsink, effectively making it part of the RF shield. Sure, its probably not foolproof and I'm not too concerned with leakage. If you remove it entirely I'm sure your TX output would be reduced, but have no actual measurements to go by.
  14. The RF shield top cover snaps off, I used a small dull screwdriver....carefully...very little force was needed. I flashed MK3 after mounting the heat sink, I ran Karma and URL snarf using my phones wifi as the "victim", no heavy traffic or MITM, maybe 20 minutes in total, without a fan, cover on, no air circulation, even with the heat sink the temp was around 140 def F, measured with a IR thermometer, they can be inaccurate on bright surfaces like aluminum. If there was no heat sink or the just stock foam tape and RF shield who knows what temp the chip was at. I SSHed into the router an
×
×
  • Create New...