crashie

I will arrange a "manual" that I put on the github later today. With the instructions. Not that complicated though. The first index.html file goes to the /pineapple folder. The image files goes to the /pineapple/img folder. The .css files goes to the /pineapple/css folder. The module.html file in the module/Dashboard folder in the zip goes to the /pineapple/modules/dashboard folder. You have to replace the old files with the new. And make sure you are on firmware 1.0.5. /crashie

For anyone who want's my "NSA-style" themes you'll find them here now: https://github.com/crashieSWE/nanothemes Will upload any future themes there. Until we have a "theme module" in the NANO :P

Here's my new "light" NSA style theme :P

Lets hope Sebkinne can fix the issue.

That's not an issue with the module but with the Nano itself. Sebkinne is working on a solution. Since if you try to download a file let's say 40MB through SFTP or SSH the same error occurs. But seb will solve it soon enough.

I already have them :P Just not in this picture :P

Green on black :P

I've actually played around with it and yeah.. I might actually go for it :P My current changes :P

You could always mod the CSS on your own :)

Yeah, interesting at least :) Looking forward to have it fixed so I can download those big pcaps without a hassle :) I have faith in you.

The issue is taken care of by sebkinne. He's looking into it since he could also reproduce the same issue. Probably solved soon enough.

1. Samsung S4 2. 5.0.1 3. Stock 4. No, not working on the S4 for some reason.. 5. Yes 6. Yes Other than that I'm running it with my Macbook Air and I also have a Alfa AWUS036NEH attached to it from time to time :P See my pic :)

To add to the issue, I've now tried four different microSD-cards. And the same issue with all of them. Are all SD-cards faulty or is it the NANO who's acting up? Can write to the SD on the NANO but the problem starts when reading a large file (downloading) from it through either the webinterface or sftp etc.

Nice ideas but why not use PineAP and allow association? That will show them what really can be done and that they don't actively have to "choose" the right network SSID :P And that it can happen to them anywhere.. At the office premises, at the restaurant, at the pub, at the train etc. They should always pay attention to networks they are connecting to and don't allow their devices to automatically connect to known wireless networks etc.. Just my 2 cents. /crashie

Some more data: Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.760000] br-lan: port 3(wlan0-1) entered disabled state Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.760000] device wlan0-1 left promiscuous mode Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.770000] br-lan: port 3(wlan0-1) entered disabled state Wed Feb 17 21:15:42 2016 daemon.notice netifd: Network device 'wlan0-1' link is down Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.910000] device wlan0 left promiscuous mode Wed Feb 17 21:15:42 2016 kern.info kernel: [ 118.910000] br-lan: port 2(wlan0) entered disabled state Wed Feb 17 21:15:42 2016 daemon.notice netifd: Network device 'wlan0' link is down Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.570000] Buffer I/O error on dev sda1, logical block 2655233, lost sync page write Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.570000] JBD2: Error -5 detected when updating journal superblock for sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.580000] Aborting journal on device sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.580000] Buffer I/O error on dev sda1, logical block 2655233, lost sync page write Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.590000] JBD2: Error -5 detected when updating journal superblock for sda1-8. Wed Feb 17 21:15:42 2016 kern.err kernel: [ 119.620000] EXT4-fs (sdb1): couldn't mount as ext3 due to feature incompatibilities Wed Feb 17 21:15:43 2016 kern.err kernel: [ 119.650000] EXT4-fs (sdb1): couldn't mount as ext2 due to feature incompatibilities Wed Feb 17 21:15:43 2016 daemon.notice netifd: radio1 (2255): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Wed Feb 17 21:15:43 2016 daemon.notice netifd: Network device 'eth0' link is down Wed Feb 17 21:15:43 2016 kern.info kernel: [ 119.970000] eth0: link down Wed Feb 17 21:15:43 2016 kern.info kernel: [ 119.970000] br-lan: port 1(eth0) entered disabled state Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.180000] EXT4-fs (sdb1): recovery complete Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.180000] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.360000] usb 1-1.2: USB disconnect, device number 5 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.370000] scsi 1:0:0:0: rejecting I/O to offline device Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.370000] scsi 1:0:0:0: [sdb] killing request Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.370000] scsi 1:0:0:0: [sdb] Wed Feb 17 21:15:43 2016 kern.warn kernel: [ 120.380000] Result: hostbyte=0x01 driverbyte=0x00 Wed Feb 17 21:15:43 2016 kern.info kernel: [ 120.380000] scsi 1:0:0:0: [sdb] CDB: Wed Feb 17 21:15:43 2016 kern.warn kernel: [ 120.390000] cdb[0]=0x28: 28 00 00 00 00 b7 00 00 08 00 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.390000] blk_update_request: I/O error, dev sdb, sector 183 Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.400000] Buffer I/O error on dev sdb2, logical block 60, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.400000] Buffer I/O error on dev sdb2, logical block 61, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.410000] Buffer I/O error on dev sdb2, logical block 62, async page read Wed Feb 17 21:15:43 2016 kern.err kernel: [ 120.420000] Buffer I/O error on dev sdb2, logical block 63, async page read Wed Feb 17 21:15:44 2016 kern.info kernel: [ 120.970000] eth0: link up (100Mbps/Full duplex) Wed Feb 17 21:15:44 2016 kern.info kernel: [ 120.970000] br-lan: port 1(eth0) entered forwarding state