abbie100
-
Posts
9 -
Joined
-
Last visited
Posts posted by abbie100
-
-
IIRC it's in /www/pineapple, but it's been a few days since I was mucking about with it.
Look there, I'll confirm tonight and stop back here.
thank you for replying to my query hfam you are a legend
Using your post of www/pineapple I finally found it but let me tell you something I never even thought of looking in the www folder as I thought it would never be there because it is a program.
you saved me after days of searching now I can finally clean ngrep.sh log
thanks mate
-
I feel like I can conquer the world!! I FIXED IT!!!!!!!!
However, it appears that there is a process that needs to be addressed and this could reoccur.
The problem was that the "ngrep.sh" file, just like the Karma issue, somehow wound up with a "control-N" at the end of each line!!!!
Before I went in with VI to attempt a fix, I copied it to ngrepold.sh (to make sure I could get back to square one), opened ngrep.sh in VI, removed every "control-N" from the end of each line, commented all "ngrep" command lines but left the SECOND one uncommented (utilizes a .pcap file), then I saved it, and rebooted the MK3.
WINNING!! Fired up the droid, opened some browsers which require logins, and VOILA!! COOKIE INFO!!
So, there is definitely something that's buggy and needs to be fixed with regard to editing the files. I'm going to suspect it's whatever the web interface uses on that Configuration page that injects the "control-N" at the end of each line.
I'm learning SOOOO much with this thing, getting back into linux is awesome...like riding a bike! :)
Hope this helps anyone else with the problem that may arise.
Darren? Is this an issue with the editing process that the web interface uses? that's where my trouble started, by editing the "ngrep" conf commenting in that interface.
Anyhow, I'm so glad this is resolved!!!
NOW back to what appears to be my device stopping/rebooting every 10-15 minutes once I start the ngrep process.
hi
I was wondering the location of the ngrep.sh in the pineapple after you ssh into it.
I tried looking in the etc, bin directory but cannot find it.
can you please specify the location
thanks
abbie
-
Oh man, thanks everyone for the assist, and thank you wcs SO much for posting this follow up, AND for posting the "linux n00bz" vi piece in there!!!
Just got my pineapple today, ran the 1.0.2 update before doing anything, and sure enough karma wouldn't start.
God I love you guys, this is going to be a helluva lot of fun!
Thanks again to all!!
thank you
finally got it working like you said "this is going to be a helluva lot of fun"
-
If I understand what your issues are...
I will post the Karma config settings from my Pineapple (MK3).
That way you can be sure you have the right stuff.
# config file to use with the Karma'd version of hostapd
# created by Robin Wood - robin@digininja.org - www.digininja.org
interface=wlan0
driver=nl80211
ssid=internet
channel=1
# both open and shared auth
auth_algs=3
# no SSID cloaking
ignore_broadcast_ssid=0
logger_syslog=-1
logger_stdout=-1
logger_syslog_level=2
logger_stdout_level=2
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
Now what will happen once you paste this in your Karma.conf file using the Pineapple Interface (in Configuration menu) and click the update button the settings will be written to the karma.conf file.
Problem is, that there is a bug that appends ^M to ever line in the conf file.
You can't see this in the Pineapple User Interface (UI) you need to terminal in to the pineapple.
Terminal to the pineapple using putty.exe or something else.
Connect using ssh
login root
password pineapplesareyummy
Then follow the directions as stated a few posts before this one.
In the end you want to delete all the ^M and save
yah I did I did after five days I finally got karma working
thanks for all your help
-
If I understand what your issues are...
I will post the Karma config settings from my Pineapple (MK3).
That way you can be sure you have the right stuff.
# config file to use with the Karma'd version of hostapd
# created by Robin Wood - robin@digininja.org - www.digininja.org
interface=wlan0
driver=nl80211
ssid=internet
channel=1
# both open and shared auth
auth_algs=3
# no SSID cloaking
ignore_broadcast_ssid=0
logger_syslog=-1
logger_stdout=-1
logger_syslog_level=2
logger_stdout_level=2
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
Now what will happen once you paste this in your Karma.conf file using the Pineapple Interface (in Configuration menu) and click the update button the settings will be written to the karma.conf file.
Problem is, that there is a bug that appends ^M to ever line in the conf file.
You can't see this in the Pineapple User Interface (UI) you need to terminal in to the pineapple.
Terminal to the pineapple using putty.exe or something else.
Connect using ssh
login root
password pineapplesareyummy
Then follow the directions as stated a few posts before this one.
In the end you want to delete all the ^M and save
Executing: grep -v -e random /tmp/karma.log
Configuration file: /etc/hostapd/karma.conf
Line 1: invalid line ‘ config file to use with the Karma’d version of hostapd
‘
Line 3: invalid line ‘
‘
Line 5: invalid/unknown driver ‘nl80211
‘
Line 8: invalid line ‘
‘
Line 9: invalid line ‘both open and shared auth
‘
Line 11: invalid line ‘
‘
Line 12: invalid line ‘ no SSID cloaking
‘
Line 14: invalid line ‘
‘
Line 15: unknown configuration item ‘ -1 ‘
Line 18: invalid line ‘
‘
Line 19: unknown configuration item ’2 ‘
Line 22: invalid line ‘
‘
Line 23: invalid line ‘ Dump file for state information (on SIGUSR1)
‘
Line 27: Invalid group ’0
Line 28: invalid line ‘
Line 29: unknown configuration item ‘ 0 ‘
Line 31: invalid line ‘
‘
MAC list file ‘/etc/hostapd/hostapd.accept
‘ not found.
Line 33: Failed to read accept_mac_file ‘/etc/hostapd/hostapd.accept
‘
MAC list file ‘/etc/hostapd/hostapd.deny
‘ not found.
Line 34: Failed to read deny_mac_file ‘/etc/hostapd/hostapd.deny
‘
Line 35: invalid line ‘
‘
KARMA: Enabled
20 errors found in configuration file ‘/etc/hostapd/karma.conf
—————————————————————————
hi
I just like to add that this was my problem before even after updating it in the web interface but using your method and the karma code plus your how to guide I will ssh into pineapple and config it there. Thank you I was really stomped and was thinking of giving up and then post the outcome.
again thank you
-
If I understand what your issues are...
I will post the Karma config settings from my Pineapple (MK3).
That way you can be sure you have the right stuff.
# config file to use with the Karma'd version of hostapd
# created by Robin Wood - robin@digininja.org - www.digininja.org
interface=wlan0
driver=nl80211
ssid=internet
channel=1
# both open and shared auth
auth_algs=3
# no SSID cloaking
ignore_broadcast_ssid=0
logger_syslog=-1
logger_stdout=-1
logger_syslog_level=2
logger_stdout_level=2
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
Now what will happen once you paste this in your Karma.conf file using the Pineapple Interface (in Configuration menu) and click the update button the settings will be written to the karma.conf file.
Problem is, that there is a bug that appends ^M to ever line in the conf file.
You can't see this in the Pineapple User Interface (UI) you need to terminal in to the pineapple.
Terminal to the pineapple using putty.exe or something else.
Connect using ssh
login root
password pineapplesareyummy
Then follow the directions as stated a few posts before this one.
In the end you want to delete all the ^M and save
I just like to thank you for taking the time to reply to my post expecially (hfam and wcs) and as well for posting your Karma code and along with instructions of how to config the karma.comf files. You guys are awesome. Being a linux newbie I still learning how linux works and having a lot of trouble trying to reinstate the karma code. I will definetly use the methods stated above as well as the karma code above to get it working and then post the results.
-
hi darren
I was wondering if you could help me
yeah when I accidently deleted the karma code I was in a panicking and instead of refresh the factory settings I went to google and I pasted in what I thought was a karma code before hitting update. Now when I hit factory settings it seems to go back to the one I pasted.
After days of fustrating I discovered the site called digninja and I pasted in a sample karma
==============================================================================
# config file to use with the Karma’d version of hostapd
# created by Robin Wood – robin@digininja.org – http://www.digininja.org
interface=wlan0
driver=nl80211
ssid=FreeInternet
channel=1
# Both open and shared auth
auth_algs=3
# no SSID cloaking
ignore_broadcast_ssid=0
# -1 = log all messages
logger_syslog=-1
logger_stdout=-1
# 2 = informational messages
logger_syslog_level=2
logger_stdout_level=2
# Dump file for state information (on SIGUSR1)
# example: kill -USR1
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
# Finally, enable Karma
enable_karma=1
===============================================================================
hoping that this would fix the problem I then hit update followed by grep -v -e random /tmp/karma.log to see what the problem might entail and to my suprise
I found this error log
============================================================================
Executing: grep -v -e random /tmp/karma.log
Configuration file: /etc/hostapd/karma.conf
Line 1: invalid line ‘ config file to use with the Karma’d version of hostapd
‘
Line 3: invalid line ‘
‘
Line 5: invalid/unknown driver ‘nl80211
‘
Line 8: invalid line ‘
‘
Line 9: invalid line ‘both open and shared auth
‘
Line 11: invalid line ‘
‘
Line 12: invalid line ‘ no SSID cloaking
‘
Line 14: invalid line ‘
‘
Line 15: unknown configuration item ‘ -1 ‘
Line 18: invalid line ‘
‘
Line 19: unknown configuration item ’2 ‘
Line 22: invalid line ‘
‘
Line 23: invalid line ‘ Dump file for state information (on SIGUSR1)
‘
Line 27: Invalid group ’0
Line 28: invalid line ‘
Line 29: unknown configuration item ‘ 0 ‘
Line 31: invalid line ‘
‘
MAC list file ‘/etc/hostapd/hostapd.accept
‘ not found.
Line 33: Failed to read accept_mac_file ‘/etc/hostapd/hostapd.accept
‘
MAC list file ‘/etc/hostapd/hostapd.deny
‘ not found.
Line 34: Failed to read deny_mac_file ‘/etc/hostapd/hostapd.deny
‘
Line 35: invalid line ‘
‘
KARMA: Enabled
20 errors found in configuration file ‘/etc/hostapd/karma.conf
—————————————————————————
seeing these errors I know understand why my karma is disable. My only chance is to replace the files using the files from the site digninja
but I don’t know how
I also read in hak5.org/forums about a guy who had problems with Karma but was able to replace his entire files using something called WINSCP but unfortunetaly he did not leave details how he did it.
sorry for going on a bit but I am still learning how linux works. is there a chance you can point where I am going wrong
cheers
abbie
ps any help will do
Mark Iii - Url Snarf + Other Questions
in WiFi Pineapples Mark I, II, III
Posted