Jump to content

Recon mode troubles

sbb

By sbb
in WiFi Pineapple NANO

 Share

Recommended Posts

sbb Newbie

sbb

Posted
Posted

When I first got my nano, I was using windows and everything worked great. I was able to use recon mode along with all the modules I was trying.

Last night, I installed Kali on my machine and hooked up the nano to that. I have an ethernet cable plugged into the laptop and wifi turned off.

When I run the wp6 shell script, it runs me through the the steps and it connects without issues. I can get to the Internet, the pineapple, and load bulletins just fine.

 

The issue I am running into now is when I try and run "Recon Scan". I just keep getting "There was an error starting Recon. Please try again."

 

Am I doing something wrong or have I forgot to do something in linux that is different than windows?

 

Before I run the wp6 command: 

root@kali:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.65  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::12e7:8a31:87f0:f5c9  prefixlen 64  scopeid 0x20<link>
        ether 78:45:c4:bc:6f:eb  txqueuelen 1000  (Ethernet)
        RX packets 726  bytes 57522 (56.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 47  bytes 3680 (3.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:c0:ca:91:53:64  txqueuelen 1000  (Ethernet)
        RX packets 33  bytes 1608 (1.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 57  bytes 10218 (9.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 18  bytes 1058 (1.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18  bytes 1058 (1.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@kali:~#

 

After I run the wp6 command: 

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.65  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::12e7:8a31:87f0:f5c9  prefixlen 64  scopeid 0x20<link>
        ether 78:45:c4:bc:6f:eb  txqueuelen 1000  (Ethernet)
        RX packets 1546  bytes 162801 (158.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 266  bytes 24704 (24.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.16.42.42  netmask 255.255.255.0  broadcast 172.16.42.255
        inet6 fe80::5ede:e6bd:c566:e226  prefixlen 64  scopeid 0x20<link>
        ether 00:c0:ca:91:53:64  txqueuelen 1000  (Ethernet)
        RX packets 848  bytes 584236 (570.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 778  bytes 163026 (159.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 20  bytes 1156 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 20  bytes 1156 (1.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@kali:~#

 

The networking section of the pineapple that is connected to the internet: 

br-lan    Link encap:Ethernet  HWaddr 00:C0:CA:91:3E:3B
          inet addr:172.16.42.1  Bcast:172.16.42.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:713 errors:0 dropped:7 overruns:0 frame:0
          TX packets:789 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:135862 (132.6 KiB)  TX bytes:580516 (566.9 KiB)

eth0      Link encap:Ethernet  HWaddr 00:C0:CA:91:3E:3B
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:713 errors:0 dropped:0 overruns:0 frame:0
          TX packets:793 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:145844 (142.4 KiB)  TX bytes:580700 (567.0 KiB)
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3555 (3.4 KiB)  TX bytes:3555 (3.4 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:C0:CA:91:0E:92
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:3014 (2.9 KiB)

wlan0-1   Link encap:Ethernet  HWaddr 02:C0:CA:91:0E:92
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:2154 (2.1 KiB)

wlan1mon  Link encap:UNSPEC  HWaddr 00-C0-CA-91-26-B2-00-44-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3894 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:940047 (918.0 KiB)  TX bytes:0 (0.0 B)

 

I went through the same steps when setting it up and can access the webui just fine. It seems though like an interface is being used or hasn't been started like it should have which is why recon mode isn't starting?

Link to comment
Share on other sites
sbb Newbie

sbb

Posted
  • Author
Posted

The reason I noticed this was because I had PineAP running for about 2 hours before I tried to actually connect to one of the rebroadcast SSID's and it wouldn't let me connect to any of them which leads me to think there is an interface issue somewhere.

Link to comment
Share on other sites
b0N3z Rookie

b0N3z

Posted
Posted

How are you powering the Nano.  A lot of problems with the nano lead back to not enough power?  If you laptop usb is only putting out 5v1a then you will run into things that wont work because the power is just not enough.

Link to comment
Share on other sites
sbb Newbie

sbb

Posted
  • Author
Posted

Wouldn't the power be the same regardless of the OS? I have both male USB ends plugged into two USB slots on the laptop on the Y adapter. The other female end is connected to the nano itself.

This setup worked fine when running it in Windows but it sounds like you are saying that a laptop in general cant put out enough power even when having both cables hooked up?

Link to comment
Share on other sites
Just_a_User Newbie

Just_a_User

Posted
Posted

I think what b0N3z is saying is that the symptoms you describe sound similar to having power issues. From what you describe it could also be something to do with the Micro SD card.

Does the problem persist over reboots? Have you tried a factory reset? Reformatted the SD from the Pineapple GUI?

Some more detail might help narrow it down to the root cause.

Link to comment
Share on other sites
b0N3z Rookie

b0N3z

Posted
Posted

@Just_a_User that is correct the problem sounds like a power issue that is why I suggested that.  Also you didnt specify how you powered it so it was just one idea on getting it work and does it persist with a reboot?

Link to comment
Share on other sites
sbb Newbie

sbb

Posted
  • Author
Posted

Thanks both, I didn't mean to sound hostile, was just trying to question the response for my own sanity :)

I left the SD card intact and just reset the nano back to factory. It appears to be working now without issue. Seems like the golden fix with these things is just to factory reset when any issues arise.

Issue resolved.

Link to comment
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.

×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...