Jump to content

shortmaniak

Active Members
  • Content Count

    14
  • Joined

  • Last visited

1 Follower

About shortmaniak

  • Rank
    Hackling

Recent Profile Visitors

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

  1. Are you on the most up to date firmware? I'm having the same issue after upgrading.
  2. Here's the contents of /etc/config/wireless: root@Pineapple:~# cat /etc/config/wireless config wifi-device 'radio0' option type 'mac80211' option channel '11' option hwmode '11g' option path 'platform/ar933x_wmac' option htmode 'HT20' option country 'US' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option maxassoc '100' option encryption 'none' option ssid 'PNANO' option hidden '1' config wifi-iface option device 'radio0' option ifname 'wlan0-1'
  3. Iw list: root@Pineapple:~# iw list | grep "Wiphy phy" Wiphy phy2 Wiphy phy1 Wiphy phy0 airmon-ng: root@Pineapple:~# airmon-ng Found phy1 with no interfaces assigned, would you like to assign one to it? [y/n] y (mac80211 monitor mode vif enabled on [phy1]wlan2mon PHY Interface Driver Chipset phy0 wlan0 rt2800usb Ralink Technology, Corp. RT5370 phy2 wlan1 ath9k_htc Qualcomm Atheros Communications AR9271 802.11n phy1 wlan2mon ath9k Not pci, usb, or sdio Am I reading that wrong or is it one of the onboard radios that isn't getting assigned? It looks like phy1 is the othe
  4. iwconfig shows the following adapters (in order): wlan1, lo, br-lan, eth0, wlan0. Just for fun I tried another ralink-based usb wireless adapter I have lying around. Same behavior, shows up in lsusb but isn't assigned to wlan2.
  5. Upgraded to 2.6.0 with a factory reset. While the lsusb output on the advanced page shows the ralink RT5370 (purchased with the nano) it does not get assigned to WLAN2. The only interfaces i have available are 0 and 1. Anything I can try to get the adapter working?
  6. Yeah I kind of figured that was where this was going, worth a shot. Thanks again for helping me troubleshoot!
  7. I ran the simpler command: hcxdumptool -i wlan1 --enable_status=3 and received the same error. I was connected to the management ap directly, and had removed the usb adapter just to be safe. I had all modules and pineap disabled at the time. I'm not familiar with "C2 Client," do you mean the client mode for wlan2? Here is the output from ps and logread: root@Pineapple:~# ps PID USER VSZ STAT COMMAND 1 root 1408 S /sbin/procd 2 root 0 SW [kthreadd] 3 root 0 SW [ksoftirqd/0] 4 root 0 SW [kworker/0:0] 5 root 0 SW&l
  8. Thanks for the tips! Do you have a link to how to change the radio for the management ap? I'm not sure i'm going to try it but it would be nice to know. I actually ended up having wlan2 connect in client mode to my phone's hotspot and then connecting to the pineapple through that network instead of direct.
  9. So I tested again when I got home and found that it does work as intended when I connect to the Pineapple over USB, but I get the error above when I'm connected to the management AP., which I supposed makes some sense. Ideally I would like to be able to run this attack while connected to the pineapple over the management AP instead of over USB. By any chance do you know it is possible to move the management AP to the usb wireless adapter (wlan2)? Oh and since you asked for version: root@Pineapple:~# opkg info hcxdumptool Package: hcxdumptool Version: 5.1.5-5 Depends: libc, libpcap Sta
  10. @Zylla First of all, thanks for setting this up! I'm having some trouble getting this to run properly no matter what interface I use it throws an error that it needs full monitor mode: root@Pineapple:/sd# hcxdumptool -o test.pcapng -i wlan2 --enable_status 3 initialization... warning: wpa_supplicant is running with pid 2227 interface may not be operational failed to init socket hcxdumptool need full (monitor mode and full packet injection running all packet types) and exclusive access to the adapter that is not the case This happens even if I manually put the interface into monito
  11. I found that while this option would say that it succeeded, it would not actually make any changes to the card, nor would it mount.
  12. Just got a nano and was banging my head against the wall trying to get my SD card mounted. Finally got it working so I figured I should leave a PSA for anyone else that has the same problem in the future. In my case the SD card was visible with fdisk -l and when attempting to use the gui to format the card it would report it as a success but would not actually format it. Fdisk would note the card as /dev/sda1. Steps to mount: Find sd card device with fdisk -l I'm guessing this will usually be /dev/sda1 Format sd card with mkfs.ext4 /dev/sda1 (change /dev/sda1 to wh
×
×
  • Create New...