Jump to content

Caedis

Active Members
  • Posts

    4
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Interests
    Certified Network Administrator, Software Development & Testing, Penetration Testing, Computer Design, Certified Network Security Specialist.

Recent Profile Visitors

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

Caedis's Achievements

Newbie

Newbie (1/14)

  1. You piqued my interest... I decided to pull a network repeater (Hub) out of the closet to see if it was a crossover issue. Negative. Still the same result with the MK3 plugged into the hub and my laptop to the hub likewise. I'll go ahead with contacting the HakShop as it seems this is, in fact a DOA. (Great....)
  2. Oh, forgot to include, I installed winpcap for Windows Version 4.1.2 (Driver +DLLs) from this website after seeing the wpcap.dll error when I started the flash program. I did a reboot of my laptop afterwards and what your seeing on that screenshot is the results *after* all that was installed. I did notice occasionally I get this error "stderr:Non arp received. Make sure, the device is connected directly!" (as noted in the screenshot attached) Edit: Also, to ensure we are on the same page here, I included a screenshot of my IP configuration on my MK3 connected NIC.
  3. I put my MK3 in redboot mode. (Disconnect from power, hold reset button, reconnect, keep holding for 2 seconds, release). as detailed here I notice no change in the indicator light pattern (If any visible change happens when it's in redboot, idk) I went here (http://forums.hak5.org/index.php?showannouncement=6) and downloaded the ap51-flash-gui-1.0-42.exe and paired it with the MK3-atherosFirmware1.9.zip which I unzipped into its component parts (openwrt-atheros-root.squashfs & openwrt-atheros-vmlinux.lzma) Changed my ip to 192.168.1.125/24 Also, according to this guide http://wifipineapple.com/doku.php?id=flashing_guide my IP should be 192.168.0.100. I tried that as well. In both cases the result was the same. The Attached screenshot show the result, which is the exact same regardless of my NICs IP. I used angry IP scanner to scan the entire 192.168.1.0/24 and 192.168.0.0/24 range no responding nodes but my own laptop NIC. I used PuTTY to attempt to Telnet into 192.168.0.1 port 9999 (while i was on the 192.168.0.0/24 network settings) No response. (As detailed here as well)
  4. The most exciting gift I got this Christmas! Imagine my dismay when, after following the directions in the quick start guide for Windows 7, the MK3 refuses to respond to any any attempts to open the management portal (http://172.16.42.1/pineapple). I wasnt even concerned with NAT at this point. I was just at the tourist stage trying to get it all working to have a look around. I retried the instructions numerous times over the next several HOURS. I even used Angry IP scanner to look at all the IP's in the 172.16.42.0/24 subnet. The ONLY IP responding was 172.16.42.42... my laptop. I even fired up a factory fresh install of Ubuntu 11.10 and of course it wont work even with the "Super Quick Start" script. Or using manual configuration with the appropriate ip and mask on the eth0 interface. I've tried holding down the pinhole reset button. Ive tried on battery and on AC. Ive used 4 different CAT5 cables (all of which work on other setups) I've used the NIC on my laptop to connect it to the internet to make sure the NIC on my laptop works in the first place. (It does) My LAN/WAN light on my MK3 is solid green. No activity. PWR is solid green. The pineapple (172.16.42.1) is not responding to any SSH attempts, Telnet, or ping. In short. By all accounts I think I got a brick from the HakShop. Am I missing any stupid obvious things?
×
×
  • Create New...