Jump to content

Mr.miYagi

Active Members
 View Profile  See their activity

  • Posts

    94

  • Joined

  • Last visited

 Content Type 

Posts posted by Mr.miYagi

    The disassociation problem

    in WiFi Pineapple Mark V

    Posted

    BeNe

    your ac:22:0b:5c:ef:13 are running under CYANOGENMOD ?

    It could theoretically be, that i dont own this device . But surely i have a permission to the test this on these.

    No idea on what for a OS it runs. But must be a Asus (MAC AC:22:0B AsustekC)

    But somethimes my HTC and Sony Phones are going crazy like this one.

    One has a modded ROM and the sony is on stock.

    The disassociation problem

    in WiFi Pineapple Mark V

    Posted

    HI all

    I have here a extreme example. Normally the client can reconnect. But this time the mkv kicks him off again:

    Oct 20 09:59:35 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:35 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:35 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:34 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:32 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:32 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:32 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:28 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:23 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:22 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:22 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:22 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:20 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:20 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:20 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:20 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:20 Pineapple daemon.notice hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: did not acknowledge authentication response
Oct 20 09:59:19 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:18 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:18 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:17 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:15 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:14 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:13 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:13 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:13 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:12 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:11 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:11 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:11 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:09 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:08 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:08 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:08 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:06 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:05 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:05 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:05 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:04 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:59:03 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:59:03 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:02 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:59:00 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:59:00 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:58:59 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:58:58 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:58:58 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:58:58 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated
Oct 20 09:58:57 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Oct 20 09:58:56 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: disassociated
Oct 20 09:58:55 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: associated (aid 5)
Oct 20 09:58:55 Pineapple daemon.info hostapd: wlan0: STA 08:fd:0e:42:56:0e IEEE 802.11: authenticated

    Other clints get randomly kicked, and reconnects.

    Got PineAP(not pineapple) questions? Let me answer them!

    in WiFi Pineapple Mark V

    Posted

    Thanks Seb

    We had a thread about that. Where Darren statet the same problem on his device:

    https://forums.hak5.org/index.php?/topic/31047-hostapd-deauthenticated-due-to-inactivity-timer-deauthremove/#entry251626

    Now we have a new one:

    https://forums.hak5.org/index.php?/topic/33901-the-disassociation-problem/#entry252423

    I have 3 Mkv5 here. You want some special tests?

    I let run them over night, and post the logs. I can give you also ssh access.

    Got PineAP(not pineapple) questions? Let me answer them!

    in WiFi Pineapple Mark V

    Posted

    Hi Seb

    Maybe i never looked at this, but i noticed that when i start dogma and beacon response, the pineapple start to deauthenticate clients. Even the device that are using the web interface, so its not really a timeout.

    Saw others have this problem. And as far asi tested, it happens only with dogma/beaconer. Karma alone works.

    https://forums.hak5.org/index.php?/topic/31047-hostapd-deauthenticated-due-to-inactivity-timer-deauthremove/

    Oct 13 13:19:24 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: authenticatedOct 13 13:19:20 Pineapple daemon.notice hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: did not acknowledge authentication responseOct 13 13:19:15 Pineapple daemon.notice hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: did not acknowledge authentication responseOct 13 13:19:14 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)Oct 13 13:19:13 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: disassociatedOct 13 13:19:13 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: associated (aid 5)Oct 13 13:19:13 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: authenticatedOct 13 13:19:11 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: associated (aid 5)Oct 13 13:19:11 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: authenticatedOct 13 13:19:09 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)Oct 13 13:19:08 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: disassociatedOct 13 13:19:08 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: authenticatedOct 13 13:19:07 Pineapple daemon.info hostapd: wlan0: STA 00:ee:bd:9f:cb:ec IEEE 802.11: authenticated

    hostapd: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

    in WiFi Pineapple Mark V

    Posted

    I added the lines:

    killall hostapd

    echo "ap_max_inactivity=99999" >> /var/run/hostapd-phy0.conf

    /usr/sbin/hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf

    With no success. The AP is still kicking and reassoc. the clients.

    Some ideas?

    Sep 29 15:28:52 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: associated (aid 1)

    Sep 29 15:28:52 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: authenticated

    Sep 29 15:28:05 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

    Sep 29 15:28:04 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: disassociated

    Sep 29 15:28:04 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: associated (aid 1)

    Sep 29 15:28:04 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: authenticated

    Sep 29 15:28:01 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

    Sep 29 15:28:00 Pineapple daemon.info hostapd: wlan0: STA 44:74:6c:3f:xx:xx IEEE 802.11: disassociated

    Reverse SSH pain

    in WiFi Pineapple Mark V

    Posted

    Thanks a lot!

    ssh -i /root/.ssh/id_rsa -N -T -R 1471:localhost:1471 -R 3322:localhost:22 tunneluser@miyagipi.org -p 3333

    This command worked well for ssh and http.

    And im not sure, but i think not using the "standard" ports, sometime is more secure...

    Reverse SSH pain

    in WiFi Pineapple Mark V

    Posted

    On the most examples here, on the wiki etc. its explained with this method, so i dont want to reinvent the wheel and i keep trying that way. Also it exits a infusion with support, and it seems to work.

    On my local network i can acces my Pineapple on port 22 and my Raspberry on 3333 with ssh., So it seems to work.

    With my PIneapple attached on 3g i can reach my Router/Raspberry too.

    Pineapple 3g Router RaspberryPi

    ssh port 3333 ---------------->port forward 3333,1471 to 192.168.0.16 ----------------->192.168.0.16

    ssh -p 3333 root@80.218.xx.xx

    This works.

    Now i want to login to the RaspberryPi and connect back to the Pineapple and forward the web UI, like described in many threads and wikis:

    https://forums.hak5.org/index.php?/topic/31135-tutorial-relay-server-setup-remote-management/

    https://forums.hak5.org/index.php?/topic/27305-reverse-ssh-tunnel-pineapple-webinterface-forwarding/

    https://help.ubuntu.com/community/SSH/OpenSSH/PortForwarding

    etc.

    I would love to use the Infusion but would be also happy with a command...

    Settings used in the Infusion:
    Host: root@80.218.xx.xx

    Port:1471

    Listen Port:1471

    It shows connected.

    Then i can ssh in the raspberry and again ssh to localhost:1471 with no luck....

    command used:

    ssh root@host -L 1471:localhost:1471

    Reverse SSH pain

    in WiFi Pineapple Mark V

    Posted

    Hi all

    After watching the episodes from Hak5 and chriswhat i still dont get my reverse ssl shell working...

    Can somebody help out?

    On my PIneapple (3g connection) i use:

    ssh -p 3333 root@80.218.xx.xx 1471:localhost:1471

    On my home router 80.218.xx.xx i opended the ports 3333 and 1471 to a raspberryPi with raspian loaded.

    On my Raspian i added the Pinapple as trusted device, so it connects without password promt.

    I changed the standart ssh port to 3333.

    After the pineapple connects i use this on my Pi:

    ssh -p 1471 root@localhost

    and gets:

    socket: Address family not supported by protocol
    ssh: connect to host localhost port 1471: Address family not supported by protocol
    I have some mixup i think....

    Sslsniff doesent work anymore

    in WiFi Pineapple Mark V

    Posted

    Hi all

    Before the upgrade on 2.xx i was intercepting imaps connections with following lines:

    echo 1 > /proc/sys/net/ipv4/ip_forward

    iptables -t nat -A PREROUTING -p tcp --destination-port 993 -j REDIRECT --to-ports 666

    iptables -t nat -A PREROUTING -p tcp --destination-port 995 -j REDIRECT --to-ports 666

    Sslsniff -c /sd/certs/wildcard -p 666

    Now after the upgrade sslsniff starts and seems to get the connection, but spits put this error:

    root@Pineapple:~# sslsniff -c /sd/sslsniff-master/leafcert.pem -p 666

    sslsniff 0.5 [sHA1 Mode] initialized and listening on 666...

    ASSERT - c getpeername failed.: Transport endpoint is not connected

    I don't remember that i used other settings to get it running.

    All other services are running fine.

    Some idea?

    TX-Power on newer FW

    in WiFi Pineapple Mark V

    Posted

    Thx Darren. At least a explanation. So i hope the Mark VI will have some other chipset, with more power...

    I love the pineapple because of the size. Messing with bigger/directional antennas is a no go for me.

    Thank you and Seb for all your work. The Mark V is a great piece of hardware and software exept this 18dBm limit.

    But let see what the new firmware brings to us.

    TX-Power on newer FW

    in WiFi Pineapple Mark V

    Posted

    Hey i had this Idea long time ago ;)

    Airbase seems to work better with android and Iphone Devices.

    But nobody could help....

    https://forums.hak5.org/index.php?/topic/33031-airbase-ng-works-an-newer-devices/

    https://forums.hak5.org/index.php?/topic/32942-karma-alternative-more-clients/#entry246141

    https://forums.hak5.org/index.php?/topic/32349-set-the-correct-routes-for-at0-bounty-for-solution/#entry241646

    I use

    airbase-ng -E /root/essids -P -C 30 -c 11 wlan1

    ifconfig at0 up

    brctl addif at0

    AP is showing. But Clients dont connect/get a IP.

    I think is something whit ip forwarding..

    TX-Power on newer FW

    in WiFi Pineapple Mark V

    Posted

    Yes im asking why wlan0 cant go up to 24dBm as advertised and as many from us reached out of the box.

    Sebkinne statet that "it can be" a false readout from SW.

    But the last answer from Darren was:

    Just noticed this. Will get confirmation from hardware and get back here ASAP. Sorry for the delay.

    So for me isnt official till now that we cant.

    Would be nice to hear if there is a workaround, or we have some very poor powered radios in our pineapples...

    TX-Power on newer FW

    in WiFi Pineapple Mark V

    Posted

    @m40295

    Of you follow the link you will see they are talkin about radio1/wlan1 and high throughput/ connection speed.

    Here we are asking why WLAN0 reach only 18dBm, after initially 24dBm. And its also advertised on the website and from Darren. And in the episode metioned before, Darren approve the 24dBi and its written black on white that the adapter can reach that. So im reading something wrong, or your link has nothing to do with that.

    TX-Power on newer FW

    in WiFi Pineapple Mark V

    Posted · Edited by Mr.miYagi

    Hi Darren and co.

    It would be nice to hear something official about that.

    In the Episode "how-to-build-a-wifi-link" you describe that the wlan0 can go up to 24dbm.

    And this is in the description:

    What's really nice with the WiFi Pineapple Mark V is that these commands can be put together as a boot mode using the DIP switches. What's more since the Mark V has two radios on one board we're able to have the best of both worlds. Our Radio0 can be set to 24 dBm and attached to a 24 dBi gain antenna for the point-to-point link, while our Radio1 interface can be set to 30 dBm with a 6 dBi gain antenna for point-to-multipoint.

    So it would be nice to hear why so many peoples are not able to reach this.

    Thanks

    Karma works

    in WiFi Pineapple Mark V

    Posted

    Hi

    As far as i know, the pineapple wil see also probes for WPA/WPA2 requests. But KARMA and co. cant emulate the AP since it haven't the key.

    So i assume and hope your home AP is WPA2 protected. No chance for the pinapple to emulate them.

    Try this:

    Connect your laptop to a open AP (you can create one on your Phone or Pineapple for example)

    Turn the AP off and turn KARMA on.

    Now KARMA should make the magic.

    Airbase-ng works an newer devices

    in WiFi Pineapple Mark V

    Posted

    Hi guys

    Tried to find the answer here many times but without luck. This ist my last shot.

    I know that the wlan1 is not intended for that, but PRO's:

    Wlan1 can go up to 30dBm while wlan0 is locked on 18dbm

    Airbase-ng gets more clients as Karma (iphones, androids)

    procedure:

    i edited wlan1 from "manaed" to "monitor" /etc/configuration/wireless

    i start airbase-ng: airbase-ng -E /listofessids -P -C 30 -c 11 wlan1 (creates the interface at0)

    And till here all works. Phones are seeing the AP, Airbase assiociate the phone with the AP.

    But dnsmask arent seeing the phone. As i understand with the pineapple configuration, dnsmasq are serving dhcp to all interfaces in the "lan" domain.

    logs:

    phone -> wlan0: hostapd shows association, dnsmasq gives ip to br-lan

    phone -> at0: airbase shows association. dnsmask is doing nothing

    In /etc/configuration/wireless i can only define on which domain phy1/wlan1 is ->lan

    But since at0 is "emulated" by airmon-ng i cant set the domain in /etc/configuration/wireless.

    Also by adding at0 to the br-lan bridge it doesent help.

    dnsmasq are not "seeing" the devices on at0

    Maybe thats not the error, if someone has an idea, plz share it.

    the script looks like this. You can try it and see the difference :)

    pineapplekarma start

    airbase-ng -E /root/essids -P -C 30 -c 11 wlan1

    ifconfig at0 up

    brctl addif at0

    PS:

    A workaround is to start airbase-ng with the mac from the wla0. So the phone can see the AP of at0, but connects to wla0 where dhcp works

    What i else tried:
    add at0 to a new interface in /e/c/network

    edited in /e/c/dhcp that the new interface get dhcp

    maybe i messed up, but it didnt work

    Ifconfig at0 xxx.xxx.xxx.xxx netmask 255.255.255.0 (i entered different IP's 172.16.42.1/2/100)

    And hell yea, im desperate :)

    Karma alternative / More clients

    in WiFi Pineapple Mark V

    Posted

    Hi all

    Since the ar9331 chipset seems locked @18dBm, and newer devices doesent are affected from pineapple KARMA im trying to get em with another tool.

    I aready had a setup an my laptop, but i messed it up and i dont get it running again...

    My idea on the Pineapple is quite simple:

    - With airbase-ng i get more client than over KARMA (also Iphonies, and androids)

    - The wlan1 chipset can go up to 30dBm

    - We can jam with the wlan0

    I already tried to get it working on the pineapple. But i dont get a IP for my clients, or no internet.

    Someone has a idea?

    Here my old post:

    https://forums.hak5.org/index.php?/topic/32341-ics-to-at0/

    Here my steps:

    airmon-ng start wlan1

    airbase-ng -E /root/essids -P -C 30 -c 9 mon0

    iptables -t nat -a POSTROUTING -o 3g-wan2 -j MASQUERADE

    ifconfig at0 up 172.16.42.2 netmask 255.255.255.0

    ifconfig at0 mtu 1400

    But dnsmasq dont assign a IP to the clients.

    It would be a good workaround for the por txrate from wlan0 and to get the anti-KARMA devices.

    (PS if you have a solution, you still can claim the bounty ;)

×
×
  • Create New...