Jump to content

cexshun

Active Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

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

cexshun's Achievements

  1. System logs showing the following: Sun Oct 22:50:22 2021 daemon.warn dnsmasq-dhcp1928 no address range available for DHCP request via wlan2 Sun Oct 22:52:20 2021 daemon.notice hostapd wlan0: STA redacted IEEE 802.11: did not acknowledge authentication response Sun Oct 22:52:19 2021 daemon.debug hostapd wlan0: STA redacted MLME: MLME-DELETEKEYS.request(redacted) Sun Oct 22:52:19 2021 daemon.debug hostapd wlan0: STA redacted MLME: MLME-AUTHENTICATE.indication(redacted, OPEN_SYSTEM) Sun Oct 22:52:19 2021 daemon.debug hostapd wlan0: STA redacted IEEE 802.11: authentication OK (open system)
  2. Looking at iwconfig, I wonder if this has something to do running out of wlan. wlan0 is acting as the open AP. wlan2 is a wifi client to my AP to provide internet. So the recon/scan/broadcast AND client connections cannot both share wlan1, right? In order to do this, I either need a USB wifi/ethernet, or ICS with a PC in order to do all of these at the same time. Is my thinking correct? I don't have enough radios?
  3. Running pineAP is active mode is also not allowing clients to connect. Pine connected in AP client mode for internet. Whether I connect to the open AP or to one of the cloned SSIDs. From several laptops and phones, they attempt to connect then fail. Struggling with this one as it's sort of a crucial feature.
  4. For some reason, if pineAP is set to either/or Capture SSIDs to Pool Beacon Response I am unable to connect to any AP running on the pineapple. If I attempt to connect to either the open AP or to one of the collected SSIDs broadcasting, it attempts to connect then fails. Filters set to Deny/Deny. If I turn off one of the above options off, I can connect fine and use the AP as expected. The collected SSIDs continue to broadcast and can be connected to. I just cannot connect while SSIDs are being collected. Am I misunderstanding how these features work?
  5. Similar issues. Crashes frequently when run standalone using a thumb drive for the log. Numerous crashes. Ran kismet_capture_linux_pcap to run as a remote, but it doesn't support GPS in that mode which makes it not useful for war walking/driving.
  6. If I run something simple like kismet -c wlan1mon I still get ERROR: Unable to find driver for 'wlan1mon'. Make sure that any required plugins are loaded, the interface is available, and any required Kismet helper packages are installed. ERROR: Data source 'wlan1mon' failed to launch: Unable to find driver for 'wlan1mon'. Make sure that any required plugins are loaded, the interface is available, and any required Kismet helper packages are installed. But then I can access the web ui, and wlan1mon is listed and enables fine.
  7. Thanks, that worked. For some reason, I can't specify the interfaces in the config or at the command line or I still get the driver errors, but I'm able to enable them in the web UI. But it's working, so it's a start.
  8. I did an opkg update, then opkg install kismet. Installs fine, and runs fine. But it refuses to use any of the interfaces as a datasource. The web interfaces shows nothing under datasources. If I specify at the command line, I get ERROR: Data source 'wlan1mon' failed to launch: Unable to find driver for 'wlan1mon'. Make sure that any required plugins are loaded, the interface is available, and any required Kismet helper packages are installed. Tried is manually putting interfaces into monitor mode with airmon-ng, and tried it without putting them into monitor mode. Same result.
×
×
  • Create New...