Jump to content

lunokhod

Active Members
  • Content Count

    77
  • Joined

  • Last visited

About lunokhod

  • Rank
    Hak5 Fan ++

Profile Information

  • Gender
    Male

Recent Profile Visitors

973 profile views
  1. Excellent, thanks for that... good to hear! No more adapters needed to connect to most of my external WiFi antennas 🙂
  2. Does the Mark VII have normal or reverse polarity SMA sockets for the antennas? I couldn't see this specifically mentioned in the specs.
  3. Hi Everybody, After seeing the news about the new Mark VII Wifi Pineapple, I though I would pull my old Mark V off of the shelf and see if it still works... it does! My config is still intact, the clock is still set and it seems to be working (with the Beta 3.0 firmware) quite OK. PineAp is doing it's thing as expected. Is the Mark V still a useful tool in today's Wifi world? Regards, Lunokhod
  4. No... I can't see it either! I hope this does make it's way back in here. I'm going to miss it if it's a no show. I wonder if it is included in the Tetra and Nano version of the firmware.
  5. I've got a question about the radio configuration used in the Tetra. I'm a long time Mk V user and remember needing to get a third radio for the the WiFi Client connection as wlan1 couldn't be used in client mode AND be used for PineAP simultaneously. wlan0 is the access point. wlan1 is used for PineAP, injection/deauth/etc. wlan2 is used to connect to my local friendly WiFi internet source. I'm presuming a third WiFi radio needed for the Tetra if I want to configure it in a similar fashion? I'm using the Beta 3.0.0 firmware on my Mk V at the moment and am VERY happy with
  6. Yes I did. I've been playing with it at work today and am most impressed with it's stability. I used to be plagued with the Wireless Client connection to the internet dropping out randomly with the 2.x firmware. No issues with that at all so far.
  7. Thanks for that. I worked around the issue. I rebooted without the NEH plugged in and the RTL8187 was still coming up as wlan2. I then "Reset WiFi Configs to Default" in the Advanced section of Networking. This reset the RTL8187 as wlan1. Plugging in the NEH after resetting the WiFi Config resulted in it coming up as wlan2. All good. Now the two MKV radios remain at wlan0 and wlan1 regardless of the external radio being plugged in at boot or not. Lunokhod.
  8. How have I missed this for two months? :-) I've just flashed my Wifi Pineapple MkV with the Beta Firmware 3.0... and it's working very nicely. I was even able to update the MkV with my wacky +9.5 hours ahead of UTC time zone. One thing that is a bit strange... my external AWUS036NEH USB Wireless radio is wlan1. The MkV AR9331 radio is wlan0 (as expected), but the built in RTL8187 radio is now wlan2. phy0 wlan0 ath9k Not pci, usb, or sdio phy0 wlan0-1 ath9k Not pci, usb, or sdio phy1 wlan1mon rt2800usb Ralink Technology, Cor
  9. Will an attached USB Ethernet adapter be able to be configured for both direct connection to a computer (inbuilt DHCP "classic" mode) and also direct to an existing Ethernet network with it's own DHCP server/gateway etc?? I'm glad you've decided to use RP-SMA connectors... I never fully understood why the Mk V had "normal" SMA sockets when 99.99% of all other WiFi SMA implementations are RP-SMA. Not overly keen with dropping of the native Ethernet port, nor the dedicated DC jack... but this being said, I'll still buy one!
  10. Have you enabled Client Mode in the Wired tab, in the Network tile? Classic Mode is the original (classic) Wired network mode where eth0 is bound to br-lan and the inbuilt DHCP server. This is the mode to use if you want to connect a computer directly to the WiFi Pineapple via Ethernet. Client Mode is for when you want to connect the WiFi Pineapple to an existing wired network. You can then enable DHCP (the WiFi Pineapple will get an IP address, gateway, etc. for eth0 from an existing DHCP server on the wired network)... or you can set a Static IP address, Netmask, Gateway and DNS entries
  11. I've seen this behavior as well. Both on my Nexus5 phone (5.1.1) and a no-name generic Android tablet. In my experience, it seems to happen after an undetermined time. Right after boot, I can see and connect to the spoofed SSIDs generated by the WiPi without a problem... but after a time, I get the same result as you see in the video.
  12. What kind of power supply did you use? Was it a regulated power supply? A high current un-regulatated wall wart power supply can have an open circuit voltage of 16V or higher. You should never use an un-regulated power supply... unless you are 100% sure the device you are using it with can handle it.
  13. I notice you have wlan1 enabled. I believe that Dogma and Beacon Response uses wlan1 as part of it's operation. I have wlan1 unchecked and I seem to have no (short term) trouble with PineAP doing it's thing, I have seen many clients connect. Try and uncheck wlan1 and see what happens. Could be that if wlan1 is enabled... PineAp cannot use it?
×
×
  • Create New...