Jump to content

damen

Active Members
  • Content Count

    35
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by damen

  1. Nexus, OnePlus, Pixel phones should all work.
  2. Yes and more with the right hardware 😎
  3. I have had this issue also. Try rebooting the nano and trying again. Sometimes is may take several reboots.
  4. @Foxtrot So logging doesn't appear to work until I run a recon scan. Any idea why this might happen? I have both filters set to deny. For PineAP settings all are checked but broadcast.
  5. You need to set the nano ip to 192.168.1.2 255.255.255.0..........then open a browser and type 192.168.1.1
  6. Understood.......Just trying to bring some attention to the probe request issue lol.
  7. Thank you Darren and Foxtrot for responding.
  8. Multiple people are having same issue! I have posted about this on Discord, Darren's YouTube video, here and haven't heard back so GL.
  9. Just an Update##### I have posted about his issue on the Hak5 forum, Hak5 discord board and on Darren's new YouTube video lol. No suggestions, answers, responses as of today.
  10. Yes. Captive portals work well with an open wireless network. There are some templates on github.
  11. run lsusb and see if it shows up there.
  12. Forgot to mention I am also seeing this in the System Log: daemon.notice. netifd: radio 0 (3005): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory
  13. PineAP I have the following checked.... PineAP Enabled Log PineAP Events Client Connect Notifications Client Disconnect Notifications So when I do a recon scan and select a device, select Probe Requests, it says "No Probes Found. Is probe logging enabled?". I also noticed that if I select "Allow Associations" from the PineAp menu and watch logging I get no requests here also. Filters are set to: Allow, Deny
  14. Guys. Probe requests aren't working for me after upgrading to 2.5.2! I have performed a firmware recovery and it works until upgrading again. Any ideas or suggestions?
  15. I have tried the firmware recovery process, then updating to 2.5.2 with no luck. I even tried with Windows vs Linux and still have the same issue.
  16. I gave up and did a firmware recovery to 2.4.1 and everything seems to work!
  17. I am having the exact same issues.
  18. Just a small update - SSID's are being added but those SSID's do not show up in the PineAP Log.
  19. Hello I noticed after upgrading to either of these firmware versions I am not getting the same probe requests as before (devices or probe requests count). What I did to trouble shoot was do a firmware recovery, enabled pineap and it was working fine. I have tried all 3 versions of the newest firmware and I am not getting any probe requests at all. I have set the filters to both disable and enabled all pineap settings. I did notice this error in the system log: Sat Mar 30 19:58:52 2019 daemon.notice netifd: radio0 (3000): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Thu Mar 28 14:56:07 2019 user.emerg syslog: [!! 28-03-2019 20:56:07] [INTERFACE] Failed to create capture handle for wlan1mon: wlan1mon: No such device exists (SIOCGIFHWADDR: No such device) Any ideas on what this is or what I could try to fix the issue im having? debug.log
×
×
  • Create New...