Jump to content

Recommended Posts

Hi Guys,

Just got my MK4 a few days ago.

I have set it up with version 2.0. and made it route to the Internet via my Laptop.

Routing works just fine. I have started Karma.

I was able to manually add a wireless AP RandomNonExisten3876 and connect to it on my Android smarthone.

The Pineapple answered 'Ja' and the smartphone routed it's data via the Pineapple.

However:

1) I'm unable to find any clients that would connect to my pineapple. This is very strange - I'm located in a very Wifi dense place (More then 10 APs around me). Any ideas o n what's going on?

2) When I connected via ssh and run airodump-ng -i mon.wlan0 i see that the pineapple is locked on channel 11 and not doing any channel hopping.

So i'm thinking maybe the channel lock causes my pineapple not to pick up client requests?

What do you think?

P.

Link to post
Share on other sites

Hi Guys,

Just got my MK4 a few days ago.

I have set it up with version 2.0. and made it route to the Internet via my Laptop.

Routing works just fine. I have started Karma.

I was able to manually add a wireless AP RandomNonExisten3876 and connect to it on my Android smarthone.

The Pineapple answered 'Ja' and the smartphone routed it's data via the Pineapple.

However:

1) I'm unable to find any clients that would connect to my pineapple. This is very strange - I'm located in a very Wifi dense place (More then 10 APs around me). Any ideas o n what's going on?

2) When I connected via ssh and run airodump-ng -i mon.wlan0 i see that the pineapple is locked on channel 11 and not doing any channel hopping.

So i'm thinking maybe the channel lock causes my pineapple not to pick up client requests?

What do you think?

P.

Have you connected to 172.16.42.1/pineapple ? and turned on karma? the feature that is the special sauce.

channel hopping is a known thing to change channels you have to bring down the interface and back up but when you do that karma and wifi will most likely not be functioning anymore.

I am waiting until someone figures how to get a usb wifi card working on the pineapple:-)

Link to post
Share on other sites
Have you connected to 172.16.42.1/pineapple ? and turned on karma? the feature that is the special sauce.

Sure.

channel hopping is a known thing to change channels you have to bring down the interface and back up but when you do that karma and wifi will most likely not be functioning anymore.

Is the channel hopping what's stopping Karma from working?

How do I fix it exactly?

I am waiting until someone figures how to get a usb wifi card working on the pineapple:-)

It's kind disappointing you need a usb wifi card on pineapple, the whole idea is to have small evil packed box :)

Link to post
Share on other sites

Got an offtopic question (sorry though, tried so hard to figure it out on my own!)

My question is the following; By using macchanger -r wlan0/mon.wlan0 I can change the MAC adress. (First needing to put the interfaces down, ifconfig wlan0/mon.wlan0 down). However this doesn't work with KARMA on. Any idea's>?

And can I use a startup script that will change the MAC adress randomly on each startup>?

Link to post
Share on other sites

Sure.

Is the channel hopping what's stopping Karma from working?

How do I fix it exactly?

It's kind disappointing you need a usb wifi card on pineapple, the whole idea is to have small evil packed box :)

the pineapple is a great package it does a great job, but if you need stuff like deauthing for now we have to use external methods having a usb wifi adapter would be a great addition

thing is if we start scanning and deauthing that would take time from karma and might have bad results.

I would try going to a new location to test the pineapple like a cafe. a reflash can sometimes help

In my opinion the newest karma is programmed into hostapd the way it is implemented may be why this channel thing is happening.

give it another shot:-)

Link to post
Share on other sites

I went to another location today. Again no luck.

Do you think that the channel hopping issues is related?

How do I resolve it?

iwconfig:

wlan0     IEEE 802.11bgn  Mode:Master  Frequency:2.462 GHz  Tx-Power=18 dBm
          RTS thr:off   Fragment thr:off
          Power Management:on

mon.wlan0  IEEE 802.11bgn  Mode:Monitor  Frequency:2.462 GHz  Tx-Power=18 dBm
          RTS thr:off   Fragment thr:off
          Power Management:on

airmon-ng


root@Pineapple:~# airmon-ng


Interface       Chipset         Driver

wlan0           Atheros         ath9k - [phy0]
mon.wlan0               Atheros         ath9k - [phy0]
IEEE            Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
802.11bgn               Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Mode:Monitor            Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Frequency:2.462         Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
GHz             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Tx-Power=18             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
dBm             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)

Ideas?

Link to post
Share on other sites

I went to another location today. Again no luck.

Do you think that the channel hopping issues is related?

How do I resolve it?

iwconfig:

wlan0     IEEE 802.11bgn  Mode:Master  Frequency:2.462 GHz  Tx-Power=18 dBm
          RTS thr:off   Fragment thr:off
          Power Management:on

mon.wlan0  IEEE 802.11bgn  Mode:Monitor  Frequency:2.462 GHz  Tx-Power=18 dBm
          RTS thr:off   Fragment thr:off
          Power Management:on

airmon-ng


root@Pineapple:~# airmon-ng


Interface       Chipset         Driver

wlan0           Atheros         ath9k - [phy0]
mon.wlan0               Atheros         ath9k - [phy0]
IEEE            Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
802.11bgn               Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Mode:Monitor            Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Frequency:2.462         Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
GHz             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
Tx-Power=18             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)
dBm             Unknown         Unknown (MONITOR MODE NOT SUPPORTED)

Ideas?

The pineapple has no need to channel hop for Karma to work.

Actually, hopping channels would kick clients connected.

You can change the channel from 11 to anything else by editing /etc/config/wireless

Beware, editing these settings has caused people soft bricks.

Best,

Sebkinne

Link to post
Share on other sites

Ok so I decided to run hostapd manually to better understand whats actually going on.

hostapd -dd -t -K /etc/hostapd/karma.conf.old

The /etc/hostapd/karma.conf.old looks like:

# config file to use with the Karma'd version of hostapd
# created by Robin Wood - robin@digininja.org - www.digininja.org
# This file is currently outdated but may become useful in the future

interface=wlan0
driver=nl80211
ssid=internet
channel=1
hw_mode=g

# both open and shared auth
auth_algs=3

# no SSID cloaking
ignore_broadcast_ssid=0

logger_syslog=-1
logger_stdout=-1
logger_syslog_level=3
logger_stdout_level=3
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0

# 0 = accept unless in deny list
macaddr_acl=0

# only used if you want to do filter by MAC address
#accept_mac_file=/etc/hostapd/hostapd.accept
#deny_mac_file=/etc/hostapd/hostapd.deny

# enable karma
enable_karma=1

So now I can see that Pineapple actually sees a lot of probes:

1336372606.882698: KARMA CTRL_IFACE Requested ESSID is PTC_Wifi
1336372606.882747: KARMA: Probe Request from 40:30:04:15:10:04 for SSID 'PTC_Wifi'
1336372606.882938: KARMA ssid malloc'd so free it

1336372606.884085: KARMA CTRL_IFACE Karam is enabled for handling probe request

1336372606.884192: KARMA CTRL_IFACE Requested ESSID is Bezeq-n_512A
1336372606.884247: KARMA: Probe Request from 40:30:04:15:10:04 for SSID 'Bezeq-n_512A'
1336372606.884459: KARMA ssid malloc'd so free it

1336372606.885472: KARMA CTRL_IFACE Karam is enabled for handling probe request

1336372606.885577: KARMA CTRL_IFACE Requested ESSID is Helix
1336372606.885627: KARMA: Probe Request from 40:30:04:15:10:04 for SSID 'Helix'
1336372606.885988: KARMA ssid malloc'd so free it

1336372606.886355: KARMA CTRL_IFACE Karam is enabled for handling probe request

1336372606.886421: KARMA CTRL_IFACE Requested ESSID is Aroma.co.il
1336372606.886470: KARMA: Probe Request from 40:30:04:15:10:04 for SSID 'Aroma.co.il'
1336372606.886659: KARMA ssid malloc'd so free it

1336372606.887549: KARMA CTRL_IFACE Karam is enabled for handling probe request

However none of those clients is connected to the Pineapple.

How do I know that answers are actually sent??

Where do I get the source of hostapd with karma module?

Link to post
Share on other sites

Your setup seems to be working as expected though. Have a look at those threads (1) and (2).

Moreover, if you can connect with your android phone, your setup should be fine. You should see the connected clients on the status page normally and your android phone also.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...