Jump to content

Coroner

Active Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Posts posted by Coroner

    will beta 3.0 go stable later on?

    in WiFi Pineapple Mark V

    Posted

    i have also had this problem, as far as i can see when i try to run or view modules that are installed on sdcard it seems to bottleneck.. taking sd card out sometimes fixed the problem .. other times when i went to manage modules there would be a blank module on my installed list with a remove button and on the download list the button would say update.. however update didnt do anything and formatting the sdcard was all i could really do

    [BETA Release] Firmware 3.0

    in WiFi Pineapple Mark V

    Posted

    i have been trying to use the pineapple app to use while mobile, but when teathering thru usb to the markV i get no response to the android phone, does the markV not supply power thru the usb? would love to get this app goign as i am struggling to share a internet signal while mobile, id prefer not to buy a 4g usb modem

     

    cheers

    error in log 3.0.0

    in WiFi Pineapple Mark V

    Posted · Edited by Coroner

    1 hour ago, Sebkinne said:

    You'll probably need to reformat your sdcard. 

    i have tried multiple ways of formatting the card, i loaded the 2.4 firmware and formatted the card, upgraded the system to 3.0.0 and before doing anything i format the sd card.. i put the sdcard into a windows machine as i know windows/dos terminal commands alot more than linux..  checking the partition on a 2gb sd card i noticed it is only allocating 867mb to the sd drive and has 1.2gb unallocated.. i let the pineapple format the sdcard to make sure i have the right config

    i am now getting this

      

    [ 1678.190000] Write-error on swap-device (8:0:48)
[ 1678.220000] Write-error on swap-device (8:0:56)
[ 1678.220000] Write-error on swap-device (8:0:64)
[ 1678.220000] Write-error on swap-device (8:0:72)
[ 1678.330000] Write-error on swap-device (8:0:80)
[ 1678.330000] Write-error on swap-device (8:0:88)
[ 1678.330000] Write-error on swap-device (8:0:96)
[ 1678.340000] Write-error on swap-device (8:0:104)
[ 1678.340000] Write-error on swap-device (8:0:112)
[ 1678.450000] Write-error on swap-device (8:0:120)
[ 1678.460000] Write-error on swap-device (8:0:128)
[ 1678.470000] Write-error on swap-device (8:0:136)
[ 1678.480000] Write-error on swap-device (8:0:144)
[ 1678.480000] Write-error on swap-device (8:0:152)
[ 1678.500000] Write-error on swap-device (8:0:160)
[ 1678.500000] Write-error on swap-device (8:0:168)
[ 1685.580000] Write-error on swap-device (8:0:176)
[ 1685.640000] Write-error on swap-device (8:0:184)
[ 1685.640000] Write-error on swap-device (8:0:192)
[ 1685.660000] Write-error on swap-device (8:0:200)
[ 1685.660000] Write-error on swap-device (8:0:208)
[ 1685.660000] Write-error on swap-device (8:0:216)
[ 1685.680000] Write-error on swap-device (8:0:224)
[ 1685.680000] Write-error on swap-device (8:0:232)
[ 1685.680000] Write-error on swap-device (8:0:240)
[ 1685.710000] Write-error on swap-device (8:0:248)
[ 1686.920000] Write-error on swap-device (8:0:256)
[ 1687.020000] Write-error on swap-device (8:0:264)
[ 1687.030000] Write-error on swap-device (8:0:272)
[ 1687.040000] Write-error on swap-device (8:0:280)
[ 1687.040000] Write-error on swap-device (8:0:288)
[ 1687.050000] Write-error on swap-device (8:0:296)
[ 1687.050000] Write-error on swap-device (8:0:304)
[ 1688.950000] Write-error on swap-device (8:0:312)
[ 1688.970000] Write-error on swap-device (8:0:320)
[ 1688.970000] Write-error on swap-device (8:0:328)
[ 1688.970000] Write-error on swap-device (8:0:336)
[ 1688.990000] Write-error on swap-device (8:0:344)
[ 1688.990000] Write-error on swap-device (8:0:352)
[ 1690.010000] Write-error on swap-device (8:0:360)
[ 1690.010000] Write-error on swap-device (8:0:368)
[ 1690.030000] Write-error on swap-device (8:0:376)
[ 1690.030000] Write-error on swap-device (8:0:384)

     

    edited ** seems to be fine now, no more error messages in the logs.. 30second powercycle did the trick

    [BETA Release] Firmware 3.0

    in WiFi Pineapple Mark V

    Posted

    On 05/08/2016 at 3:26 PM, Sebkinne said:

    No, wlan0 is used to run the AP and is required for normal operation. Wlan1 is used for pineap or clientmode (not both). If you want pineap and wireless clientmode, you'll have to plug in a third supported radio. 

     

    i have tried using a tplink usb nic on the old firmware and never had luck getting the drivers to make it work, is their a special brand i need or does this firmware support more usb nic's? i'd test it out but my dongle is in a pc at a dif location

    error in log 3.0.0

    in WiFi Pineapple Mark V

    Posted

    hello legends..

    loving the new ported interface, i am aware its a beta, i am meganoob when it comes to linux.. i notice a error in my logs and i was wondering what is happening, it appears to be with my storage

    any advice would be much appreciated 

    Sat Aug 13 19:36:26 2016 kern.err kernel: [  720.410000] Buffer I/O error on device sda1, logical block 35325
Sat Aug 13 19:36:26 2016 kern.warn kernel: [  720.410000] EXT4-fs warning (device sda1): ext4_end_bio:317: I/O error -5 writing to inode 157 (offset 0 size 4096 starting block 286583)
Sat Aug 13 19:36:26 2016 kern.err kernel: [  720.570000] Aborting journal on device sda1-8.
Sat Aug 13 19:36:26 2016 kern.err kernel: [  720.570000] JBD2: Error -5 detected when updating journal superblock for sda1-8.
Sat Aug 13 19:36:27 2016 kern.crit kernel: [  721.700000] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
Sat Aug 13 19:36:27 2016 kern.crit kernel: [  721.710000] EXT4-fs (sda1): Remounting filesystem read-only
Sat Aug 13 19:36:27 2016 kern.err kernel: [  721.710000] EXT4-fs (sda1): previous I/O error to superblock detected
Sat Aug 13 19:37:00 2016 kern.alert kernel: [  754.040000] Write-error on swap-device (8:0:121)
Sat Aug 13 19:42:10 2016 kern.crit kernel: [ 1064.520000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #23: comm nginx: reading directory lblock 0
Sat Aug 13 19:42:10 2016 kern.err kernel: [ 1064.530000] EXT4-fs (sda1): previous I/O error to superblock detected
Sat Aug 13 19:42:21 2016 kern.crit kernel: [ 1075.700000] EXT4-fs error (device sda1): ext4_find_entry:1289: inode #121: comm nginx: reading directory lblock 0
Sat Aug 13 19:42:21 2016 kern.err kernel: [ 1075.710000] EXT4-fs (sda1): previous I/O error to superblock detected
Sat Aug 13 19:45:02 2016 daemon.info hostapd: wlan0-1: STA 90:e7:c4:68:14:0a WPA: group key handshake completed (RSN)

    adding another wlan connection

    in WiFi Pineapple Mark V

    Posted

    sorry, i am just learning..

    is there a way to add another wlan connection using a usb wifi nic? i have one plugged in an under attached usb devices it shows up, but i dont know how to access it thru network tab on the pineapple gui

    Attached USB devices:

    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
    Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
    Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
    Bus 001 Device 007: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

    it is device 007 .. hopefully i can get another network connection to the pineapple

    Cheers

    Coroner

    infusion that collects stored SSID passwords

    in WiFi Pineapple Mark V

    Posted

    In order to take in WPA clients you must already know the key, defeating the purpose of having such an infusion - if I understand correctly.

    when pineAP clones the SSID's that the phones are probing for, once they probe again and find the SSID made by the pineapple, i would of thought that they would hand over the SSID password fairly easily??

    infusion that collects stored SSID passwords

    in WiFi Pineapple Mark V

    Posted

    Hello,

    so i live opposite a school and during drop off and pick up

    day 1.. pineapple harvested a ton of SSID's from mobile phones probing

    day 2.. had alot of connected clients connected to the SSID's pineAP made

    when the mobile phones connect to the SSID would they automatically give up the WPA stored password upon login? and if so is there an infusion that will siphon the password to a log file?

    they may only give up the password if wpa security is set to on.. maybe someone could make an infusion that acts like wpa is turned on and is requestiong a password while we are connected to the client and logging the information they give up

    Cheers

    Coroner

    mdk3 and other error

    in WiFi Pineapple Mark V

    Posted

    root@Pineapple:~# opkg install mdk3

    Installing mdk3 (v6-1) to root...


    wget: server returned error: HTTP/1.1 404 Not Found

    Collected errors:

    * opkg_download: Failed to download http://cloud.wifipineapple.com/mk5/packages/mdk3_v6-1_ar71xx.ipk, wget returned 1.

    * opkg_install_pkg: Failed to download mdk3. Perhaps you need to run 'opkg update'?

    * opkg_install_cmd: Cannot install package mdk3.



    i cant install these packages after a opkg update, also other pacls that get evil portal working


    any suggestions? im a noob hope this is right place to post this

×
×
  • Create New...