Jump to content

yonomas

Active Members
  • Posts

    50
  • Joined

  • Last visited

Everything posted by yonomas

  1. These are the issues so far Sometimes i get all at the same time, sometimes is just the SD issue, sometimes the clients don't have internet and so on 1)Broadcast SSID Pool : It suppose to work all the time right? For some reason mine, works for a few minutes, then i have to turn on again 2)SD card In order to make it work, from time to time i have to remove and put it back again, modules don’t work because are installed on the SD card Tested with 3 microSd cards so far, same issue with all of them. I use the format tool on the pineapple menu 3)WiFi Client Mode why the clients are not getting internet most of the time? I have to reboot the nano a few times, then it works. I’m using the Wlan that comes with the tactical elite and connect to a router with internet access, 4)Is there a way to bypass the Browser warning? I have sslsplit and dwall installed, but when a client try to access to facebook or gmail or any other https website, they get the warning that the website is not secure. So basically, is useless. I've been testing at home the last 48 hs and... i'm totally regretting 5)How do i enable PineAP and all the modules on boot? I have to start from scratch every time, even when i select the option "Start on boot"
  2. tested with 3 different micro SD cards so far
  3. This is the last log file http://pastebin.com/XReW48st
  4. Fri Oct 7 08:30:31 2016 user.info autossh[11567]: starting ssh (count 1) Fri Oct 7 08:30:31 2016 user.info autossh[11567]: ssh child pid is 11568 Fri Oct 7 08:30:32 2016 user.err autossh[11567]: ssh exited prematurely with status 255; autossh exiting Fri Oct 7 08:30:32 2016 user.notice firewall: Reloading firewall due to ifup of wan (wlan2) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.790000] Write-error on swap-device (8:0:720) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.790000] Write-error on swap-device (8:0:728) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.790000] Write-error on swap-device (8:0:736) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.810000] Write-error on swap-device (8:0:744) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.810000] Write-error on swap-device (8:0:752) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.820000] Write-error on swap-device (8:0:760) Fri Oct 7 08:31:07 2016 kern.alert kernel: [ 2128.820000] Write-error on swap-device (8:0:768) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.850000] Write-error on swap-device (8:0:776) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.850000] Write-error on swap-device (8:0:784) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.860000] Write-error on swap-device (8:0:792) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.870000] Write-error on swap-device (8:0:800) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.880000] Write-error on swap-device (8:0:808) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.880000] Write-error on swap-device (8:0:816) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.880000] Write-error on swap-device (8:0:824) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.890000] Write-error on swap-device (8:0:832) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.900000] Write-error on swap-device (8:0:840) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.900000] Write-error on swap-device (8:0:848) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.910000] Write-error on swap-device (8:0:856) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.910000] Write-error on swap-device (8:0:864) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.920000] Write-error on swap-device (8:0:872) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.930000] Write-error on swap-device (8:0:880) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.930000] Write-error on swap-device (8:0:888) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.930000] Write-error on swap-device (8:0:896) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.950000] Write-error on swap-device (8:0:904) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.950000] Write-error on swap-device (8:0:912) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2130.960000] Write-error on swap-device (8:0:920) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.050000] Write-error on swap-device (8:0:928) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.050000] Write-error on swap-device (8:0:936) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.060000] Write-error on swap-device (8:0:944) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.060000] Write-error on swap-device (8:0:952) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.070000] Write-error on swap-device (8:0:960) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.070000] Write-error on swap-device (8:0:968) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.090000] Write-error on swap-device (8:0:976) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.090000] Write-error on swap-device (8:0:984) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.100000] Write-error on swap-device (8:0:992) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.100000] Write-error on swap-device (8:0:1000) Fri Oct 7 08:31:09 2016 kern.alert kernel: [ 2131.220000] Write-error on swap-device (8:0:1008) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.490000] Write-error on swap-device (8:0:1016) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.490000] Write-error on swap-device (8:0:1024) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.510000] Write-error on swap-device (8:0:1032) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.510000] Write-error on swap-device (8:0:1040) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.520000] Write-error on swap-device (8:0:1048) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.520000] Write-error on swap-device (8:0:1056) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.530000] Write-error on swap-device (8:0:1064) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.540000] Write-error on swap-device (8:0:1072) Fri Oct 7 08:31:10 2016 kern.alert kernel: [ 2131.540000] Write-error on swap-device (8:0:1080) Fri Oct 7 08:31:11 2016 daemon.notice netifd: Network device 'wlan2' link is down Fri Oct 7 08:31:11 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss Fri Oct 7 08:31:11 2016 daemon.notice netifd: wan (11507): Received SIGTERM
  5. Broadcast SSID Pool doesn't work either, i think i made a mistake buying this pineapple
  6. I'ts been like 4 hours and there is no way to make this work, dwall worked, but when i enable sslsplit, it doesn't work anymore But even running sslsplit alone... it doesnt work its says "starting", but never starts
  7. Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.140000] sd 6:0:0:0: [sda] Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.140000] Result: hostbyte=0x07 driverbyte=0x00 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.140000] sd 6:0:0:0: [sda] CDB: Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.150000] cdb[0]=0x28: 28 00 00 00 25 e0 00 00 7e 00 Thu Oct 6 14:23:17 2016 kern.err kernel: [ 1515.150000] blk_update_request: I/O error, dev sda, sector 9696 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.160000] usb 1-1.2: USB disconnect, device number 4 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.180000] sd 6:0:0:0: [sda] Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.180000] Result: hostbyte=0x01 driverbyte=0x00 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.180000] sd 6:0:0:0: [sda] CDB: Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.190000] cdb[0]=0x28: 28 00 00 00 25 e1 00 00 7d 00 Thu Oct 6 14:23:17 2016 kern.err kernel: [ 1515.190000] blk_update_request: I/O error, dev sda, sector 9697 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.200000] sd 6:0:0:0: [sda] Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.200000] Result: hostbyte=0x01 driverbyte=0x00 Thu Oct 6 14:23:17 2016 kern.info kernel: [ 1515.200000] sd 6:0:0:0: [sda] CDB: Thu Oct 6 14:23:17 2016 kern.warn kernel: [ 1515.210000] cdb[0]=0x28: 28 00 00 00 25 e0 00 00 01 00 Thu Oct 6 14:23:17 2016 kern.err kernel: [ 1515.210000] blk_update_request: I/O error, dev sda, sector 9696 Thu Oct 6 14:23:17 2016 kern.err kernel: [ 1515.220000] FAT-fs (sda1): FAT read failed (blocknr 1504) Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.850000] FAT-fs (sda1): Directory bread(block 16640) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.850000] FAT-fs (sda1): Directory bread(block 16641) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.860000] FAT-fs (sda1): Directory bread(block 16642) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.860000] FAT-fs (sda1): Directory bread(block 16643) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.870000] FAT-fs (sda1): Directory bread(block 16644) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.880000] FAT-fs (sda1): Directory bread(block 16645) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.880000] FAT-fs (sda1): Directory bread(block 16646) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.890000] FAT-fs (sda1): Directory bread(block 16647) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.890000] FAT-fs (sda1): Directory bread(block 16648) failed Thu Oct 6 14:23:18 2016 kern.err kernel: [ 1515.900000] FAT-fs (sda1): Directory bread(block 16649) failed Thu Oct 6 14:23:20 2016 kern.info kernel: [ 1518.320000] usb 1-1.2: new high-speed USB device number 6 using ehci-platform
  8. SD card works sometimes, sometimes you need to remove it and put it back in order to make it work, also the recon get me " "No scan results." Even when i have 3 routers running next to me ( 2.4Gz) How do i fix that? I already did the factory reset 3 times!!
  9. http://amzn.to/2d69ckm it says 22000mAh, that would be....... 10 hours using the nano? Not sure if fits in the tatical case for the nano,
  10. Can we do that without damage the battery or the nano? I have the Pineapple juice 4000
  11. oh, i got it, unfortunately will only fit if you are not using the battery, if you want to use the battery, you'll have to screw the antenas after putting on the case, am i right? i tried tu put both nano with antennas and battery and is too tight, will i break it? Another question, the nano will be hot at some point, so, is it safe to put the battery and the nano really tight on the case?
  12. thanks for reply, so, that means that the other antenna that comes with the box (an is tight ) is not suitable to use into the tactical pouch?
  13. why? what's the reason? so far is uncomfortable to move and easy to break, why would i want a loose antena?
  14. Hey guys, for some reason when put the antennas on the device, they are loose, have already adjusted to the maximum possible and they are still loose, How I do to make them straight? Perhaps this pair is defective? I ordered the nano tactical elite that comes with the upgraded antenna, that's the one with the issue.
  15. add parameter or change ports or add anything to the url using MitM
  16. Hey guys, i just got my nano elite a few days ago and i was wondering if this is possible. I'd like to experiment with URL rewrite and add a parameter to every website.com’s request every time you try to access www.website.com/folder1/ it will redirect to www.website.com/folder1/?value=abc123 Basically add ?value=abc123 to every url from a specific domain I'm totally new on this, so, please try to explain like you'll explain to a 6 year old kid Thanks in advance
  17. Well, get the pass using http is also illegal, but that's not the point, what i'm trying to do is for testing purposes only. My question is, can i get the OAuth? If so, what can i do with it?
  18. I'm new here, basically there is no way to get access to the facebook/twitter with their OAuth or whatever info we could get from the user? What if i don't want the user and pass, what if i need only the email address and profile picture from the victim, and maybe post something on his/her wall Is there a way to get that using the wifi pineapple nano?
  19. same question here, any update?
×
×
  • Create New...