Jump to content

Vertices

Active Members
  • Content Count

    7
  • Joined

  • Last visited

About Vertices

  • Rank
    Newbie

Contact Methods

  • Website URL
    http://www.perfectcobalt.com

Recent Profile Visitors

383 profile views
  1. Hi wintermute, Which video did you watch? There are a couple that Darren's posted, but the following has some extra config for forwarding (which sounds like it might be your problem): https://hak5.org/episodes/hak5-1921-access-internal-networks-with-reverse-vpn-connections Also see this thread: I can't comment on the floating IP, but have you made sure the "Listen on all interfaces" option is selected under the Server Network Configuration tab on OpenVPN? This is likely related to your timeouts, too. http://www.perfectcobalt.com/ https://perfectcobalt.blogspot.co.uk/
  2. Hi kanalia It sounds like you're missing some packet forwarding settings. Check out this HAK5 Turtle vid (the stuff you may have missed is at ~22min mark): https://hak5.org/episodes/hak5-1921-access-internal-networks-with-reverse-vpn-connections It was these settings in /etc/config/network and /etc/config/firewall that eventually got me up and running with the VPN. Hope this helps -- PerfectCobalt.com http://perfectcobalt.blogspot.co.uk/
  3. Awesome! Everything seems more stable since 1.0.2, and stuff seems a little quicker too. One issue I am seeing (1.0.1/2/3 all included) is if I have PineAP running and publishing SSIDs, my phone/tablet/whatever can see a load of open networks - all hosted on the Pineapple (good, obviously). That other device is still connected to my own home wifi, however - just showing available networks. If I then do a client recon, it usually finds my client device, and all seems fine. If I then deauth my device, all those open networks change to "Out of range", and don't return ("never" is a long time to claim, but I waited ... a while). Anyone else seen behaviour like this?
  4. Hi telot, Yes thanks - it makes sense. Key here is the Open Networks. I'd not read enough about pre-shared keys and the WPA handshaking. This post makes clear why the Pineapple can't do it (and it's hard in general): http://www.smallnetbuilder.com/wireless/wireless-howto/30278-how-to-crack-wpa-wpa2?start=2 Hope this makes things clear for someone else :)
  5. Hi folks, I can see this post might be stale by now, but it seems the right place to ask this. I've got a tame friend who agreed to plant my turtle on his own LAN. I set it up for autossh, and that worked right out of the box. I want to try to poke around on his network from *my* network, and so followed Darren's video instructions (and this post) for configuring an OpenVPN server. It all seems fine, but I don't get the route to the remote LAN pushed to my client. The turtle's VPN user is set up as to gateway the remote LAN - as shown above, but for 192.168.90.0/24 - and if I connect my end to the VPN, I can ping the turtle's VPN IP address directly, and even ssh to it directly from either Windows or Linux, but I cannot ping the remote LAN from my home network.As I understand it, the gateway setting on the OpenVPN server should push a gateway route to me, and should manage the traffic between the VPN clients to that remote net. I'm sure there's an important point I've misunderstood, so any help much appreciated
  6. Hi folks, Received my Nano a short while back - in the UK, and it's my first experience with a Pineapple. I've got it set up, using Firefox and Win7/10, and even using a Sammy tablet with tethering. It all seems fine, and following Darren's "nano primer" vid, I can scan for clients, and see my own (and other) devices, connect back out to the Internet over sharing or tethering, etc.. So I go ahead and enable the PineAP, with all the tick boxes, along with the honey-trap landing page as described in the video, and then death my mobile phone (another Samsung). I see it getting disconnected from my internal wifi, which is WPA2 protected. Around half the time it just reconnects to the "real" access point, but if it attempts to connect to the Pineapple's AP, it shows "Authentication Error Occurred". I'm new to mucking about with wifi and networks, so excuse my noobness. I guess the problem is because the phone is expecting to provide the pass-key to the real AP, whereas the Pineapple rogue AP is (presumably) open. Does this mean that the Rogue AP will only work for devices probing Open wifi? Or is there some other problem I've missed? Cheers for any help
×
×
  • Create New...