Ven0mRat Posted September 18, 2019 Share Posted September 18, 2019 Device: Wifi pineapple tetra [latest firmware] I cant even capture handshake with recon or Site Survey, deauth works but I dont get handshake anytime (tested on my devices and network) so this device dont have a sense now, pineapple dont see my usb external storage, dwall dont work (when I click enable and start listening I only see loading logo anytime and nothing is happen) I have this more. Please FIX that or tell me how to do that because for now I use that as my new router. Link to comment Share on other sites More sharing options...
INFOTRACE Posted September 18, 2019 Share Posted September 18, 2019 40 minutes ago, Ven0mRat said: Device: Wifi pineapple tetra [latest firmware] I cant even capture handshake with recon or Site Survey, deauth works but I dont get handshake anytime (tested on my devices and network) so this device dont have a sense now, pineapple dont see my usb external storage, dwall dont work (when I click enable and start listening I only see loading logo anytime and nothing is happen) I have this more. Please FIX that or tell me how to do that because for now I use that as my new router. Same..........so I went back by reset as though new...........it seems to be taking some time to find a solution. Hope this helps.......🙏 Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 18, 2019 Share Posted September 18, 2019 Do a firmware recovery on the tetra. This will get you to where most modules will work until they are updated for the 2.6.x firmware. Firmware recovery will take you to version 2.4.1 which has been reported to work with most modules or after a recovery manual upgrade to 2.5.4 as one of those two should work with most modules. Instructions for firmware recovery: https://docs.hak5.org/hc/en-us/articles/360010471774-Firmware-Recovery BE SURE to use the firmware recovery bin file to do a firmware recovery. Also, just because you are not capturing handshakes, doesn't mean its not working. There are many factors involved with a successful handshake capture. If you are not familar with how the 4-way handshake works, I'd recommend some reading on the topic. Recon should be working and when dong some testing earlier SiteSurvey was working with 2.6.x firmware (extensive testing was not done on SiteSurvey so it is possible that an issue still exists). Link to comment Share on other sites More sharing options...
Newbier Posted September 19, 2019 Share Posted September 19, 2019 9 hours ago, Cap_Sig said: Do a firmware recovery on the tetra. This will get you to where most modules will work until they are updated for the 2.6.x firmware. Firmware recovery will take you to version 2.4.1 which has been reported to work with most modules or after a recovery manual upgrade to 2.5.4 as one of those two should work with most modules. Instructions for firmware recovery: https://docs.hak5.org/hc/en-us/articles/360010471774-Firmware-Recovery BE SURE to use the firmware recovery bin file to do a firmware recovery. Also, just because you are not capturing handshakes, doesn't mean its not working. There are many factors involved with a successful handshake capture. If you are not familar with how the 4-way handshake works, I'd recommend some reading on the topic. Recon should be working and when dong some testing earlier SiteSurvey was working with 2.6.x firmware (extensive testing was not done on SiteSurvey so it is possible that an issue still exists). why should have to do this it should just work and do the thing but mums the word hak5 should front up and say we follow the lead of apple and what they do with phones Link to comment Share on other sites More sharing options...
Irukandji Posted September 19, 2019 Share Posted September 19, 2019 There was a major upgrade with the openwrt. So need to wait for the 3rd party developers to update their packages. Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 19, 2019 Author Share Posted September 19, 2019 15 hours ago, Cap_Sig said: Do a firmware recovery on the tetra. This will get you to where most modules will work until they are updated for the 2.6.x firmware. Firmware recovery will take you to version 2.4.1 which has been reported to work with most modules or after a recovery manual upgrade to 2.5.4 as one of those two should work with most modules. Instructions for firmware recovery: https://docs.hak5.org/hc/en-us/articles/360010471774-Firmware-Recovery BE SURE to use the firmware recovery bin file to do a firmware recovery. Also, just because you are not capturing handshakes, doesn't mean its not working. There are many factors involved with a successful handshake capture. If you are not familar with how the 4-way handshake works, I'd recommend some reading on the topic. Recon should be working and when dong some testing earlier SiteSurvey was working with 2.6.x firmware (extensive testing was not done on SiteSurvey so it is possible that an issue still exists). Thanks for your reply I will downgrade my firmware and check the result. I know how to capture handshake and I do that before with my laptop with kali linux system,but I buy this device for do that also. Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 19, 2019 Share Posted September 19, 2019 6 hours ago, Newbier said: why should have to do this it should just work and do the thing but mums the word hak5 should front up and say we follow the lead of apple and what they do with phones I'm curious how you are comparing them to Apple? They aren't trying to push a new wifi pineapple currently so its not like they are provoking sales of a new model. Most of this issue is users not understanding that "community" modules are exactly that. They are not guaranteed and are not a major advertised selling point of the product. They should be viewed as a bonus feature of the pineapple. The issue is with outdated community modules that have now lost compatibility with the 2.6.x firmware. @Foxtrot has said in another thread he is working to fix community modules as time allows. To me that is a sign that they understand users want current available community modules and are doing what they can to help fix them. It does suck that you currently can't run the latest firmware AND use all the community modules,. but is it really that big of deal? Its a simple as a downgrade that takes usually no more than 10 minutes to get them back working until things are fixed for the latest firmware. Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 19, 2019 Author Share Posted September 19, 2019 I have a problem with this recovery. Quote For example, in Linux run ifconfig eth1 192.168.1.2 netmask 255.255.255.0 up (where eth1 is the interface name of the WiFi Pineapple). From the host PC, browse to http://192.168.1.1 192.168.1.1 this is my router web page,when I type another ip (example 192.168.0.2) dont work And I dont have eth1 but enx001337a76f4f but this is normal for my linux system, he was always be weird Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 19, 2019 Share Posted September 19, 2019 1 hour ago, Ven0mRat said: 192.168.1.1 this is my router web page,when I type another ip (example 192.168.0.2) dont work Disconnect from your local network before doing so. You have to connect to it for recovery using 192.168.1.1 as this is the default IP. 1 hour ago, Ven0mRat said: And I dont have eth1 but enx001337a76f4f but this is normal for my linux system, he was always be weird Then you will want to use "enx001337a76f4f" as your adapter. The name of the adapter can change depending on your OS, current number of adapters, etc. You can also do this from a windows machine by just changing the settings in network settings. Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 19, 2019 Author Share Posted September 19, 2019 35 minutes ago, Cap_Sig said: Disconnect from your local network before doing so. You have to connect to it for recovery using 192.168.1.1 as this is the default IP. Then you will want to use "enx001337a76f4f" as your adapter. The name of the adapter can change depending on your OS, current number of adapters, etc. You can also do this from a windows machine by just changing the settings in network settings. ahh yes I'm stupid,I off my network connection now is work,I will test modules soon. Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 20, 2019 Author Share Posted September 20, 2019 Can you tell me how to do manual firmware update? because in pineapple (advanced->upgrade) I find link in which the instruction appears to be but when I open page I see only recovery instruction and automatic upgrade. ,, For recovry or manual upgrade instructions and help visit Https://wifipineapple.com/?flashing" But I dont see something like manual upgrade here. Link to comment Share on other sites More sharing options...
Irukandji Posted September 20, 2019 Share Posted September 20, 2019 It's more fun.... no jokes, here https://docs.hak5.org/hc/en-us/articles/360025819673-Manual-Firmware-Installation Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 20, 2019 Author Share Posted September 20, 2019 23 minutes ago, Jtyle6 said: It's more fun.... no jokes, here https://docs.hak5.org/hc/en-us/articles/360025819673-Manual-Firmware-Installation Thanks mate Link to comment Share on other sites More sharing options...
Newbier Posted September 21, 2019 Share Posted September 21, 2019 On 9/19/2019 at 11:57 PM, Cap_Sig said: I'm curious how you are comparing them to Apple? They aren't trying to push a new wifi pineapple currently so its not like they are provoking sales of a new model. Most of this issue is users not understanding that "community" modules are exactly that. They are not guaranteed and are not a major advertised selling point of the product. They should be viewed as a bonus feature of the pineapple. The issue is with outdated community modules that have now lost compatibility with the 2.6.x firmware. @Foxtrot has said in another thread he is working to fix community modules as time allows. To me that is a sign that they understand users want current available community modules and are doing what they can to help fix them. It does suck that you currently can't run the latest firmware AND use all the community modules,. but is it really that big of deal? Its a simple as a downgrade that takes usually no more than 10 minutes to get them back working until things are fixed for the latest firmware. because that version of firmware has come and gone, imagine having to downgrade your mobile just to get those third party apps in the app store to work hak5 should create their modules and also include user created modules as a bonus Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 21, 2019 Share Posted September 21, 2019 21 hours ago, Jtyle6 said: It's more fun.... no jokes, here https://docs.hak5.org/hc/en-us/articles/360025819673-Manual-Firmware-Installation 👍 Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 21, 2019 Share Posted September 21, 2019 4 hours ago, Newbier said: because that version of firmware has come and gone, imagine having to downgrade your mobile just to get those third party apps in the app store to work hak5 should create their modules and also include user created modules as a bonus I see where you are coming from. I'm sure part of it is having the time, resources, people, etc to maintain a large list of modules. And if they were to do this it could potentially drive product price up as they would have more invested in it. At least with the current method using community modules for additions past the base firmware modules helps keep product price affordable and the community involved with development of the devices. Funny story, actually did have that happen to me with Apple devices (iPads and iPhones) that auto updated to the latest iOS version and a custom tailored business app developer refused to update for compatibility. Long story short, the company using the app had to downgrade all devices or spend a very LARGE sum of money to have the app remade by another dev. Link to comment Share on other sites More sharing options...
Foxtrot Posted September 21, 2019 Share Posted September 21, 2019 15 hours ago, Newbier said: because that version of firmware has come and gone, imagine having to downgrade your mobile just to get those third party apps in the app store to work hak5 should create their modules and also include user created modules as a bonus This is literally exactly the current scenario... the modules you receive as part of the firmware are authored by Hak5, modules available on the Module Manager are the "bonus" user created modules, to put it the same way you did. The comparison to Apple is nonsensical. We are not a large enough team to manage 20+ modules that we did not author. They will be updated when we can, or when the module authors do. Link to comment Share on other sites More sharing options...
Ven0mRat Posted September 22, 2019 Author Share Posted September 22, 2019 14 hours ago, Foxtrot said: This is literally exactly the current scenario... the modules you receive as part of the firmware are authored by Hak5, modules available on the Module Manager are the "bonus" user created modules, to put it the same way you did. The comparison to Apple is nonsensical. We are not a large enough team to manage 20+ modules that we did not author. They will be updated when we can, or when the module authors do. So,we wait for this. But you have to admit that the latest update just made this device worthless. Even the handshake cannot be captured, 70% of the modules do not work when the downgrade device to version 2.5.4 already has the handshake working but some useful modules do not work either (including dwall). Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 22, 2019 Share Posted September 22, 2019 14 hours ago, Foxtrot said: This is literally exactly the current scenario... the modules you receive as part of the firmware are authored by Hak5, modules available on the Module Manager are the "bonus" user created modules, to put it the same way you did. The comparison to Apple is nonsensical. We are not a large enough team to manage 20+ modules that we did not author. They will be updated when we can, or when the module authors do. 👍 Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 22, 2019 Share Posted September 22, 2019 5 minutes ago, Ven0mRat said: So,we wait for this. But you have to admit that the latest update just made this device worthless. Even the handshake cannot be captured, 70% of the modules do not work when the downgrade device to version 2.5.4 already has the handshake working but some useful modules do not work either (including dwall). Its a tough spot to be in. Hak5 could just never release updates for the device and the community modules continue to work without being updated, but then how would you feel if new features/improvements never got offered over the life of the device..? The biggest hope is module creators of past/present/future continue to update/improve there modules to work with the latest Hak5 firmware. Link to comment Share on other sites More sharing options...
Newbier Posted September 23, 2019 Share Posted September 23, 2019 On 9/22/2019 at 9:28 AM, Foxtrot said: This is literally exactly the current scenario... the modules you receive as part of the firmware are authored by Hak5, modules available on the Module Manager are the "bonus" user created modules, to put it the same way you did. The comparison to Apple is nonsensical. We are not a large enough team to manage 20+ modules that we did not author. They will be updated when we can, or when the module authors do. of the comparsion to apple is nonsensical dude cause release is new Link to comment Share on other sites More sharing options...
skifire Posted September 27, 2019 Share Posted September 27, 2019 I just wanted to add some data... Received a new Tetra yesterday and immediately upgraded to 2.6.1 before doing anything else. Recon was dead -- no matter what I changed, recon would not provide any results, though Site Survey would give some information. I just downgraded to 2.4.1 and it;s working as expected. I have added my sys log from when I was having the issue in case it's helpful. Quote Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.000000] Linux version 4.14.134 (@4708b150a871) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r0+10558-a2cbcfcdff)) #0 Sat Aug 31 00:30:39 2019 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] bootconsole [early0] enabled Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] CPU0 revision is: 0001974c (MIPS 74Kc) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] SoC: Atheros AR9344 rev 3 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Determined physical RAM map: Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] memory: 08000000 @ 00000000 (usable) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Initrd not found or empty - disabling initrd Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Zone ranges: Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Normal [mem 0x0000000000000000-0x0000000007ffffff] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Movable zone start for each node Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Early memory node ranges Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000007ffffff] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff] Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] On node 0 totalpages: 32768 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat 8054e210, node_mem_map 81000020 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] Normal zone: 256 pages used for memmap Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] Normal zone: 0 pages reserved Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] Normal zone: 32768 pages, LIFO batch:7 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0x90/0x478 with crng_init=0 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 32512 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.000000] Kernel command line: board=PINEAPPLE-TETRA console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,256k(u-boot-env),256k(caldata),-(mb0);ar934x-nfc:2048k(kernel),-(ubi) rootfstype=squashfs noinitrd Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Writing ErrCtl register=00000000 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Readback ErrCtl register=00000000 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Memory: 124044K/131072K available (3980K kernel code, 171K rwdata, 900K rodata, 188K init, 205K bss, 7028K reserved, 0K cma-reserved) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] NR_IRQS: 51 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000MHz Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6825930166 ns Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.000009] sched_clock: 32 bits at 280MHz, resolution 3ns, wraps every 7669584382ns Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.008311] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.084935] pid_max: default: 32768 minimum: 301 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.090070] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.097127] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.106904] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.117415] futex hash table entries: 256 (order: -1, 3072 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.124408] NET: Registered protocol family 16 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.130532] MIPS: machine is Hak5 WiFi Pineapple TETRA Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.136289] ar71xx: using random MAC address for eth0 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.369471] ar71xx: using random MAC address for eth1 Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 0.613872] registering PCI controller with io_map_base unset Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.636301] PCI host bridge to bus 0000:00 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.640728] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.648043] pci_bus 0000:00: root bus resource [io 0x0000] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.653987] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.661207] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff] Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.669686] pci 0000:00:00.0: [168c:abcd] type 00 class 0x020000 Thu Sep 26 20:51:37 2019 kern.err kernel: [ 0.669703] pci 0000:00:00.0: invalid calibration data Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.675206] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit] Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.675262] pci 0000:00:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref] Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.675344] pci 0000:00:00.0: supports D1 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.675356] pci 0000:00:00.0: PME# supported from D0 D1 D3hot Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.675572] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.675603] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.683436] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.691778] clocksource: Switched to clocksource MIPS Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.698262] NET: Registered protocol family 2 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.703712] TCP established hash table entries: 1024 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.711143] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.717969] TCP: Hash tables configured (established 1024 bind 1024) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.724876] UDP hash table entries: 256 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.731111] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.738089] NET: Registered protocol family 1 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 0.742806] PCI: CLS 0 bytes, default 32 Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 0.747702] Crashlog allocated RAM at address 0x3f00000 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.754657] workingset: timestamp_bits=30 max_order=15 bucket_order=0 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.766600] squashfs: version 4.0 (2009/01/31) Phillip Lougher Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.772848] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.793760] io scheduler noop registered Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.797937] io scheduler deadline registered (default) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.803826] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.810968] console [ttyS0] disabled Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.834875] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.844072] console [ttyS0] enabled Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.851488] bootconsole [early0] disabled Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 0.863770] m25p80 spi0.0: found s25fl008k, expected m25p80 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.878958] m25p80 spi0.0: s25fl008k (1024 Kbytes) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.883875] 4 cmdlinepart partitions found on MTD device spi0.0 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.889882] Creating 4 MTD partitions on "spi0.0": Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.894769] 0x000000000000-0x000000040000 : "u-boot" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.901529] 0x000000040000-0x000000080000 : "u-boot-env" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.908374] 0x000000080000-0x0000000c0000 : "caldata" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.915600] 0x0000000c0000-0x000000100000 : "mb0" Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.923350] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x48 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.929803] nand: Micron MT29F16G08ABABAWP 2GiB 3.3V 8-bit Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.935410] nand: 2048 MiB, SLC, erase size: 512 KiB, page size: 4096, OOB size: 224 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 0.943334] Scanning device for bad blocks Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 0.952974] random: fast init done Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 1.218578] 2 cmdlinepart partitions found on MTD device ar934x-nfc Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 1.224949] Creating 2 MTD partitions on "ar934x-nfc": Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 1.230174] 0x000000000000-0x000000200000 : "kernel" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 1.236623] 0x000000200000-0x000080000000 : "ubi" Thu Sep 26 20:51:37 2019 kern.info kernel: [ 1.246907] libphy: Fixed MDIO Bus: probed Thu Sep 26 20:51:37 2019 kern.info kernel: [ 1.262848] libphy: ag71xx_mdio: probed Thu Sep 26 20:51:37 2019 kern.info kernel: [ 1.893662] ag71xx-mdio.1: Found an AR934X built-in switch Thu Sep 26 20:51:37 2019 kern.info kernel: [ 1.945836] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.583754] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY] Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.593653] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.601524] NET: Registered protocol family 10 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.610680] Segment Routing with IPv6 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.614572] NET: Registered protocol family 17 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 2.619704] 8021q: 802.1Q VLAN Support v1.8 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 2.628241] UBI: auto-attach mtd5 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 2.631639] ubi0: attaching mtd5 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 4.103813] random: crng init done Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.204363] ubi0: scanning is finished Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.232456] ubi0: attached mtd5 (name "ubi", size 2046 MiB) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.238120] ubi0: PEB size: 524288 bytes (512 KiB), LEB size: 516096 bytes Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.245145] ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.252044] ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.259105] ubi0: good PEBs: 4092, bad PEBs: 0, corrupted PEBs: 0 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.265295] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.272637] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 858528783 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.281821] ubi0: available PEBs: 0, total reserved PEBs: 4092, PEBs reserved for bad PEB handling: 80 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.291310] ubi0: background thread "ubi_bgt0d" started, PID 294 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 15.299304] block ubiblock0_0: created from ubi0:0(rootfs) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 15.304940] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem Thu Sep 26 20:51:37 2019 kern.info kernel: [ 15.320535] VFS: Mounted root (squashfs filesystem) readonly on device 254:0. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 15.328818] Freeing unused kernel memory: 188K Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 15.333365] This architecture does not have kernel memory protection. Thu Sep 26 20:51:37 2019 user.info kernel: [ 15.924194] init: Console is alive Thu Sep 26 20:51:37 2019 user.info kernel: [ 15.927879] init: - watchdog - Thu Sep 26 20:51:37 2019 user.info kernel: [ 17.823700] kmodloader: loading kernel modules from /etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.015552] usbcore: registered new interface driver usbfs Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.021224] usbcore: registered new interface driver hub Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.026756] usbcore: registered new device driver usb Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.071228] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 18.088380] SCSI subsystem initialized Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.097863] ehci-platform: EHCI generic platform driver Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.103324] ehci-platform ehci-platform: EHCI Host Controller Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.109180] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.119314] ehci-platform ehci-platform: TX-TX IDP fix enabled Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.125281] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.151841] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.159020] hub 1-0:1.0: USB hub found Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.163292] hub 1-0:1.0: 1 port detected Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.170984] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.179044] ohci-platform: OHCI generic platform driver Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.187145] uhci_hcd: USB Universal Host Controller Interface driver Thu Sep 26 20:51:37 2019 kern.info kernel: [ 18.198606] usbcore: registered new interface driver usb-storage Thu Sep 26 20:51:37 2019 user.info kernel: [ 18.205493] kmodloader: done loading kernel modules from /etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 user.info kernel: [ 18.215414] init: - preinit - Thu Sep 26 20:51:37 2019 kern.info kernel: [ 19.297091] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Thu Sep 26 20:51:37 2019 user.info kernel: [ 19.531644] mount_root: loading kmods from internal overlay Thu Sep 26 20:51:37 2019 user.info kernel: [ 19.584626] kmodloader: loading kernel modules from //etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 user.info kernel: [ 19.597077] kmodloader: done loading kernel modules from //etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 19.863825] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 401 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 20.277080] UBIFS (ubi0:1): recovery needed Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.081522] UBIFS (ubi0:1): recovery completed Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.086194] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.094164] UBIFS (ubi0:1): LEB size: 516096 bytes (504 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.104236] UBIFS (ubi0:1): FS size: 2048901120 bytes (1953 MiB, 3970 LEBs), journal size 33546240 bytes (31 MiB, 65 LEBs) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.115448] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.122177] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 877633FE-E56F-4E00-BC99-3A62992971B4, small LPT model Thu Sep 26 20:51:37 2019 user.info kernel: [ 21.136895] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab Thu Sep 26 20:51:37 2019 user.info kernel: [ 21.164648] block: extroot: not configured Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.169053] UBIFS (ubi0:1): un-mount UBI device 0 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.173900] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.186432] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 404 Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.954280] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data" Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.962279] UBIFS (ubi0:1): LEB size: 516096 bytes (504 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.972367] UBIFS (ubi0:1): FS size: 2048901120 bytes (1953 MiB, 3970 LEBs), journal size 33546240 bytes (31 MiB, 65 LEBs) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.983579] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB) Thu Sep 26 20:51:37 2019 kern.notice kernel: [ 21.990294] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 877633FE-E56F-4E00-BC99-3A62992971B4, small LPT model Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.013879] mount_root: loading kmods from internal overlay Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.065210] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.077609] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/* Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.266053] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.286876] block: extroot: not configured Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.296682] mount_root: switching to ubifs overlay Thu Sep 26 20:51:37 2019 user.warn kernel: [ 22.370603] urandom-seed: Seeding with /etc/urandom.seed Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.459531] procd: - early - Thu Sep 26 20:51:37 2019 user.info kernel: [ 22.462642] procd: - watchdog - Thu Sep 26 20:51:37 2019 user.info kernel: [ 23.211864] procd: - watchdog - Thu Sep 26 20:51:37 2019 user.info kernel: [ 23.215378] procd: - ubus - Thu Sep 26 20:51:37 2019 user.info kernel: [ 23.661702] procd: - init - Thu Sep 26 20:51:37 2019 user.info kernel: [ 24.893556] kmodloader: loading kernel modules from /etc/modules.d/* Thu Sep 26 20:51:37 2019 kern.info kernel: [ 24.929980] Loading modules backported from Linux version v4.19.32-0-g3a2156c839c7 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 24.937731] Backport generated by backports.git v4.19.32-1-0-g1c4f7569 Thu Sep 26 20:51:37 2019 user.info kernel: [ 25.081688] urngd: v1.0.0 started. Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220162] ath: EEPROM regdomain: 0x0 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220171] ath: EEPROM indicates default country code should be used Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220175] ath: doing EEPROM country->regdmn map search Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220192] ath: country maps to regdmn code: 0x3a Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220198] ath: Country alpha2 being used: US Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.220202] ath: Regpair used: 0x3a Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.234565] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.236636] ieee80211 phy0: Atheros AR9340 Rev:3 mem=0xb8100000, irq=47 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.243624] pci 0000:00:00.0: using irq 40 for pin 1 Thu Sep 26 20:51:37 2019 kern.warn kernel: [ 25.248680] PCI: Enabling device 0000:00:00.0 (0000 -> 0002) Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347327] ath: EEPROM regdomain: 0x0 Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347336] ath: EEPROM indicates default country code should be used Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347341] ath: doing EEPROM country->regdmn map search Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347357] ath: country maps to regdmn code: 0x3a Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347364] ath: Country alpha2 being used: US Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.347368] ath: Regpair used: 0x3a Thu Sep 26 20:51:37 2019 kern.debug kernel: [ 25.358835] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.360955] ieee80211 phy1: Atheros AR9300 Rev:4 mem=0xb0000000, irq=40 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.656470] usbcore: registered new interface driver ath9k_htc Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.684071] RPC: Registered named UNIX socket transport module. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.690086] RPC: Registered udp transport module. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.694907] RPC: Registered tcp transport module. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.699677] RPC: Registered tcp NFSv4.1 backchannel transport module. Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.786753] usbcore: registered new interface driver mt76x2u Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.844256] usbcore: registered new interface driver rt2800usb Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.866190] usbcore: registered new interface driver rtl8187 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.914321] usbcore: registered new interface driver rtl8192cu Thu Sep 26 20:51:37 2019 kern.info kernel: [ 25.995174] ip6_tables: (C) 2000-2006 Netfilter Core Team Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.038122] usbcore: registered new interface driver cdc_acm Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.043937] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.073924] usbcore: registered new interface driver cdc_wdm Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.096436] ip_tables: (C) 2000-2006 Netfilter Core Team Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.132944] nf_conntrack version 0.5.0 (2048 buckets, 8192 max) Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.340758] usbcore: registered new interface driver ums-alauda Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.349559] usbcore: registered new interface driver ums-cypress Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.358582] usbcore: registered new interface driver ums-datafab Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.367345] usbcore: registered new interface driver ums-freecom Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.376344] usbcore: registered new interface driver ums-isd200 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.385368] usbcore: registered new interface driver ums-jumpshot Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.394266] usbcore: registered new interface driver ums-karma Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.421747] usbcore: registered new interface driver ums-sddr09 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.450129] usbcore: registered new interface driver ums-sddr55 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.469373] usbcore: registered new interface driver ums-usbat Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.508795] usbcore: registered new interface driver usbserial Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.514882] usbcore: registered new interface driver usbserial_generic Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.521587] usbserial: USB Serial support registered for generic Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.588730] xt_time: kernel timezone is -0000 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.602281] usbcore: registered new interface driver asix Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.618586] usbcore: registered new interface driver ax88179_178a Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.644724] usbcore: registered new interface driver cdc_ether Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.671139] usbcore: registered new interface driver pl2303 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.676950] usbserial: USB Serial support registered for pl2303 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.697731] PPP generic driver version 2.4.2 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.718776] NET: Registered protocol family 24 Thu Sep 26 20:51:37 2019 kern.info kernel: [ 26.734994] usbcore: registered new interface driver rndis_host Thu Sep 26 20:51:37 2019 user.info kernel: [ 26.762229] kmodloader: done loading kernel modules from /etc/modules.d/* Thu Sep 26 20:51:37 2019 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses! Thu Sep 26 20:51:37 2019 user.notice dnsmasq: Allowing 127.0.0.0/8 responses Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: started, version 2.80 cachesize 150 Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: DNS service limited to local subnets Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain test Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain onion Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain localhost Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain local Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain invalid Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain bind Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: using local addresses only for domain lan Thu Sep 26 20:51:38 2019 daemon.warn dnsmasq[939]: no servers found in /tmp/resolv.conf.auto, will retry Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: read /etc/hosts - 4 addresses Thu Sep 26 20:51:38 2019 daemon.info dnsmasq[939]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: 8021ad Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: 8021q Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: macvlan Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: veth Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: bridge Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: Network device Thu Sep 26 20:51:40 2019 user.notice : Added device handler type: tunnel Thu Sep 26 20:51:40 2019 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom Thu Sep 26 20:51:40 2019 daemon.err block: /dev/ubi0_1 is already mounted on /overlay Thu Sep 26 20:51:44 2019 kern.info kernel: [ 36.005583] br-lan: port 1(eth1) entered blocking state Thu Sep 26 20:51:44 2019 kern.info kernel: [ 36.010923] br-lan: port 1(eth1) entered disabled state Thu Sep 26 20:51:44 2019 kern.info kernel: [ 36.016569] device eth1 entered promiscuous mode Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'lan' is enabled Thu Sep 26 20:51:44 2019 kern.info kernel: [ 36.123314] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'lan' is setting up now Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'lan' is now up Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: reading /tmp/resolv.conf.auto Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain test Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain onion Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain localhost Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain local Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain invalid Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain bind Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using local addresses only for domain lan Thu Sep 26 20:51:44 2019 daemon.info dnsmasq[939]: using nameserver 8.8.4.4#53 Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'loopback' is enabled Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'loopback' is setting up now Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'loopback' is now up Thu Sep 26 20:51:44 2019 kern.info kernel: [ 36.236874] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'wan' is enabled Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'wan6' is enabled Thu Sep 26 20:51:44 2019 daemon.notice netifd: Network device 'lo' link is up Thu Sep 26 20:51:44 2019 daemon.notice netifd: Interface 'loopback' has link connectivity Thu Sep 26 20:51:45 2019 user.notice firewall: Reloading firewall due to ifup of lan (br-lan) Thu Sep 26 20:51:46 2019 kern.info kernel: [ 38.124088] eth1: link up (100Mbps/Full duplex) Thu Sep 26 20:51:46 2019 kern.info kernel: [ 38.128732] br-lan: port 1(eth1) entered blocking state Thu Sep 26 20:51:46 2019 kern.info kernel: [ 38.134080] br-lan: port 1(eth1) entered forwarding state Thu Sep 26 20:51:46 2019 daemon.notice netifd: Network device 'eth1' link is up Thu Sep 26 20:51:46 2019 daemon.notice netifd: bridge 'br-lan' link is up Thu Sep 26 20:51:46 2019 daemon.notice netifd: Interface 'lan' has link connectivity Thu Sep 26 20:51:46 2019 kern.info kernel: [ 38.188207] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready Thu Sep 26 20:51:48 2019 kern.info kernel: [ 39.645597] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready Thu Sep 26 20:51:48 2019 daemon.notice netifd: radio1 (1096): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Thu Sep 26 20:51:49 2019 daemon.notice netifd: radio0 (1095): Configuration file: /var/run/hostapd-phy0.conf Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.623401] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.744249] br-lan: port 2(wlan0) entered blocking state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.749653] br-lan: port 2(wlan0) entered disabled state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.755423] device wlan0 entered promiscuous mode Thu Sep 26 20:51:50 2019 daemon.notice netifd: radio0 (1095): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Thu Sep 26 20:51:50 2019 daemon.notice netifd: radio0 (1095): Using interface wlan0 with hwaddr 00:13:37:a7:76:8c and ssid "Wifi_768C" Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.783697] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.790425] br-lan: port 2(wlan0) entered blocking state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.795885] br-lan: port 2(wlan0) entered forwarding state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.808258] br-lan: port 3(wlan0-1) entered blocking state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.814166] br-lan: port 3(wlan0-1) entered disabled state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.820061] device wlan0-1 entered promiscuous mode Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.846325] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.852591] br-lan: port 3(wlan0-1) entered blocking state Thu Sep 26 20:51:50 2019 kern.info kernel: [ 41.858157] br-lan: port 3(wlan0-1) entered forwarding state Thu Sep 26 20:51:50 2019 daemon.notice netifd: radio0 (1095): Using interface wlan0-1 with hwaddr 02:13:37:a7:76:8c and ssid "HP-1140 Wi-Fi" Thu Sep 26 20:51:51 2019 kern.info kernel: [ 42.681864] br-lan: port 3(wlan0-1) entered disabled state Thu Sep 26 20:51:51 2019 kern.info kernel: [ 42.792436] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready Thu Sep 26 20:51:51 2019 kern.info kernel: [ 42.799262] br-lan: port 3(wlan0-1) entered blocking state Thu Sep 26 20:51:51 2019 kern.info kernel: [ 42.804893] br-lan: port 3(wlan0-1) entered forwarding state Thu Sep 26 20:51:51 2019 daemon.notice netifd: radio0 (1095): wlan0: interface state COUNTRY_UPDATE->ENABLED Thu Sep 26 20:51:51 2019 daemon.notice netifd: radio0 (1095): wlan0: AP-ENABLED Thu Sep 26 20:51:53 2019 auth.info sshd[1385]: Server listening on 0.0.0.0 port 22. Thu Sep 26 20:51:53 2019 auth.info sshd[1385]: Server listening on :: port 22. Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[939]: exiting on receipt of SIGTERM Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: started, version 2.80 cachesize 150 Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: DNS service limited to local subnets Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile Thu Sep 26 20:51:53 2019 daemon.info dnsmasq-dhcp[1451]: DHCP, IP range 172.16.42.100 -- 172.16.42.249, lease time 12h Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain test Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain onion Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain localhost Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain local Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain invalid Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain bind Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain lan Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: reading /tmp/resolv.conf.auto Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain test Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain onion Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain localhost Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain local Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain invalid Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain bind Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using local addresses only for domain lan Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: read /etc/hosts - 4 addresses Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses Thu Sep 26 20:51:53 2019 daemon.info dnsmasq-dhcp[1451]: read /etc/ethers - 0 addresses Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: read /etc/hosts - 4 addresses Thu Sep 26 20:51:53 2019 daemon.info dnsmasq[1451]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses Thu Sep 26 20:51:53 2019 daemon.info dnsmasq-dhcp[1451]: read /etc/ethers - 0 addresses Thu Sep 26 20:51:54 2019 daemon.notice netifd: radio0 (1095): OK Thu Sep 26 20:51:54 2019 daemon.notice netifd: radio0 (1095): OK Thu Sep 26 20:51:54 2019 daemon.notice netifd: radio0 (1095): OK Thu Sep 26 20:51:54 2019 daemon.notice netifd: radio0 (1095): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Thu Sep 26 20:51:54 2019 daemon.notice netifd: radio0 (1095): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Thu Sep 26 20:51:54 2019 daemon.notice netifd: Network device 'wlan0' link is up Thu Sep 26 20:51:54 2019 daemon.notice netifd: Network device 'wlan0-1' link is up Thu Sep 26 20:51:55 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led eth0 Thu Sep 26 20:51:55 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led wlan0 Thu Sep 26 20:51:55 2019 daemon.notice procd: /etc/rc.d/S96led: setting up led wlan1 Thu Sep 26 20:51:55 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.106 00:13:37:a7:76:8f Thu Sep 26 20:51:55 2019 daemon.warn dnsmasq-dhcp[1451]: Ignoring domain MLTS.LOCAL for DHCP host name MLTS-WS98 Thu Sep 26 20:51:55 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.106 00:13:37:a7:76:8f MLTS-WS98 Thu Sep 26 20:51:56 2019 daemon.info dnsmasq[1451]: read /etc/hosts - 4 addresses Thu Sep 26 20:51:56 2019 daemon.info dnsmasq[1451]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses Thu Sep 26 20:51:56 2019 daemon.info dnsmasq-dhcp[1451]: read /etc/ethers - 0 addresses Thu Sep 26 20:51:58 2019 daemon.notice procd: /etc/rc.d/S99pineapd: [!! 26-09-2019 20:51:58] [INTERFACE] Failed to create capture handle for wlan1mon: wlan1mon: No such device exists (SIOCGIFHWADDR: No such device) Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:51:59 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:52:00 2019 daemon.info modinfo: Usage: modinfo module Thu Sep 26 20:52:02 2019 user.notice root: =========== PineAP ============== Thu Sep 26 20:52:02 2019 daemon.info procd: - init complete - Fri Sep 27 02:30:40 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: authenticated Fri Sep 27 02:30:40 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: associated (aid 1) Fri Sep 27 02:30:40 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a RADIUS: starting accounting session E50CBE9D1760F5A3 Fri Sep 27 02:30:40 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a WPA: pairwise key handshake completed (RSN) Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPDISCOVER(br-lan) 58:cb:52:15:48:0a Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPOFFER(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPDISCOVER(br-lan) 58:cb:52:15:48:0a Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPOFFER(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:30:43 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:34:22 2019 kern.info kernel: [ 340.465738] device wlan0 left promiscuous mode Fri Sep 27 02:34:22 2019 kern.info kernel: [ 340.470384] br-lan: port 2(wlan0) entered disabled state Fri Sep 27 02:34:22 2019 kern.info kernel: [ 340.480442] device wlan0-1 left promiscuous mode Fri Sep 27 02:34:22 2019 kern.info kernel: [ 340.485312] br-lan: port 3(wlan0-1) entered disabled state Fri Sep 27 02:34:25 2019 kern.info kernel: [ 343.307372] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready Fri Sep 27 02:34:25 2019 daemon.notice netifd: radio1 (2276): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Fri Sep 27 02:34:26 2019 daemon.notice netifd: radio0 (2295): Configuration file: /var/run/hostapd-phy0.conf Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.368297] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.385515] br-lan: port 2(wlan0) entered blocking state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.390919] br-lan: port 2(wlan0) entered disabled state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.396770] device wlan0 entered promiscuous mode Fri Sep 27 02:34:26 2019 daemon.notice netifd: radio0 (2295): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Fri Sep 27 02:34:26 2019 daemon.notice netifd: radio0 (2295): Using interface wlan0 with hwaddr 00:13:37:a7:76:8c and ssid "Wifi_768C" Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.433008] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.439668] br-lan: port 2(wlan0) entered blocking state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.445131] br-lan: port 2(wlan0) entered forwarding state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.462672] br-lan: port 3(wlan0-1) entered blocking state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.468288] br-lan: port 3(wlan0-1) entered disabled state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.474245] device wlan0-1 entered promiscuous mode Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.503269] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.509601] br-lan: port 3(wlan0-1) entered blocking state Fri Sep 27 02:34:26 2019 kern.info kernel: [ 344.515235] br-lan: port 3(wlan0-1) entered forwarding state Fri Sep 27 02:34:26 2019 daemon.notice netifd: radio0 (2295): Using interface wlan0-1 with hwaddr 02:13:37:a7:76:8c and ssid "HP-1140 Wi-Fi" Fri Sep 27 02:34:27 2019 kern.info kernel: [ 345.401870] br-lan: port 3(wlan0-1) entered disabled state Fri Sep 27 02:34:27 2019 kern.info kernel: [ 345.594469] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready Fri Sep 27 02:34:27 2019 kern.info kernel: [ 345.601303] br-lan: port 3(wlan0-1) entered blocking state Fri Sep 27 02:34:27 2019 kern.info kernel: [ 345.606956] br-lan: port 3(wlan0-1) entered forwarding state Fri Sep 27 02:34:27 2019 daemon.notice netifd: radio0 (2295): wlan0: interface state COUNTRY_UPDATE->ENABLED Fri Sep 27 02:34:27 2019 daemon.notice netifd: radio0 (2295): wlan0: AP-ENABLED Fri Sep 27 02:34:29 2019 daemon.notice netifd: radio0 (2295): OK Fri Sep 27 02:34:29 2019 daemon.notice netifd: radio0 (2295): OK Fri Sep 27 02:34:29 2019 daemon.notice netifd: radio0 (2295): OK Fri Sep 27 02:34:29 2019 daemon.notice netifd: radio0 (2295): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Fri Sep 27 02:34:29 2019 daemon.notice netifd: radio0 (2295): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Fri Sep 27 02:34:29 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: authenticated Fri Sep 27 02:34:29 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: associated (aid 1) Fri Sep 27 02:34:29 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a RADIUS: starting accounting session 89CB53DC44A7B53B Fri Sep 27 02:34:29 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a WPA: pairwise key handshake completed (RSN) Fri Sep 27 02:34:30 2019 daemon.info dnsmasq-dhcp[1451]: DHCPDISCOVER(br-lan) 58:cb:52:15:48:0a Fri Sep 27 02:34:30 2019 daemon.info dnsmasq-dhcp[1451]: DHCPOFFER(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:34:30 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:34:30 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 02:34:30 2019 daemon.notice netifd: Network device 'wlan0' link is up Fri Sep 27 02:34:30 2019 daemon.notice netifd: Network device 'wlan0-1' link is up Fri Sep 27 02:35:54 2019 kern.info kernel: [ 433.043096] eth0: link up (1000Mbps/Full duplex) Fri Sep 27 02:35:54 2019 kern.info kernel: [ 433.047889] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Fri Sep 27 02:35:54 2019 daemon.notice netifd: Network device 'eth0' link is up Fri Sep 27 02:35:54 2019 daemon.notice netifd: Interface 'wan' has link connectivity Fri Sep 27 02:35:54 2019 daemon.notice netifd: Interface 'wan' is setting up now Fri Sep 27 02:35:54 2019 daemon.notice netifd: Interface 'wan6' has link connectivity Fri Sep 27 02:35:54 2019 daemon.notice netifd: Interface 'wan6' is setting up now Fri Sep 27 02:35:54 2019 daemon.notice netifd: Interface 'wan6' is now up Fri Sep 27 02:35:55 2019 daemon.notice netifd: wan (2759): udhcpc: started, v1.30.1 Fri Sep 27 02:35:55 2019 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0) Fri Sep 27 02:35:55 2019 daemon.notice netifd: wan (2759): udhcpc: sending discover Fri Sep 27 02:35:56 2019 daemon.notice netifd: wan (2759): udhcpc: sending select for 172.16.10.151 Fri Sep 27 02:35:56 2019 daemon.notice netifd: wan (2759): udhcpc: lease of 172.16.10.151 obtained, lease time 86400 Fri Sep 27 02:35:57 2019 daemon.notice netifd: Interface 'wan' is now up Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: reading /tmp/resolv.conf.auto Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain test Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain onion Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain localhost Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain local Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain invalid Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain bind Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using local addresses only for domain lan Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Fri Sep 27 02:35:57 2019 daemon.info dnsmasq[1451]: using nameserver 172.16.10.1#53 Fri Sep 27 02:35:58 2019 user.notice firewall: Reloading firewall due to ifup of wan (eth0) Fri Sep 27 02:34:15 2019 daemon.warn dnsmasq[1451]: nameserver 8.8.4.4 refused to do a recursive query Fri Sep 27 02:44:03 2019 daemon.warn dnsmasq[1451]: nameserver 172.16.10.1 refused to do a recursive query Fri Sep 27 03:41:28 2019 kern.info kernel: [ 4474.962008] eth1: link down Fri Sep 27 03:41:28 2019 kern.info kernel: [ 4474.965765] br-lan: port 1(eth1) entered disabled state Fri Sep 27 03:41:28 2019 daemon.notice netifd: Network device 'eth1' link is down Fri Sep 27 03:41:29 2019 kern.info kernel: [ 4476.003252] eth1: link up (10Mbps/Full duplex) Fri Sep 27 03:41:29 2019 kern.info kernel: [ 4476.008487] br-lan: port 1(eth1) entered blocking state Fri Sep 27 03:41:29 2019 kern.info kernel: [ 4476.013846] br-lan: port 1(eth1) entered forwarding state Fri Sep 27 03:41:29 2019 daemon.notice netifd: Network device 'eth1' link is up Fri Sep 27 08:32:11 2019 kern.info kernel: [21918.482619] eth1: link down Fri Sep 27 08:32:11 2019 kern.info kernel: [21918.486337] br-lan: port 1(eth1) entered disabled state Fri Sep 27 08:32:11 2019 daemon.notice netifd: Network device 'eth1' link is down Fri Sep 27 08:32:12 2019 kern.info kernel: [21919.523855] eth1: link up (100Mbps/Full duplex) Fri Sep 27 08:32:12 2019 kern.info kernel: [21919.528635] br-lan: port 1(eth1) entered blocking state Fri Sep 27 08:32:12 2019 kern.info kernel: [21919.534016] br-lan: port 1(eth1) entered forwarding state Fri Sep 27 08:32:12 2019 daemon.notice netifd: Network device 'eth1' link is up Fri Sep 27 08:32:17 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.106 00:13:37:a7:76:8f Fri Sep 27 08:32:17 2019 daemon.warn dnsmasq-dhcp[1451]: Ignoring domain MLTS.LOCAL for DHCP host name MLTS-WS98 Fri Sep 27 08:32:17 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.106 00:13:37:a7:76:8f MLTS-WS98 Fri Sep 27 08:32:41 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 08:32:41 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 08:34:37 2019 kern.info kernel: [22064.079196] eth1: link down Fri Sep 27 08:34:37 2019 kern.info kernel: [22064.082901] br-lan: port 1(eth1) entered disabled state Fri Sep 27 08:34:37 2019 daemon.notice netifd: Network device 'eth1' link is down Fri Sep 27 08:34:38 2019 kern.info kernel: [22065.120444] eth1: link up (10Mbps/Full duplex) Fri Sep 27 08:34:38 2019 kern.info kernel: [22065.125319] br-lan: port 1(eth1) entered blocking state Fri Sep 27 08:34:38 2019 kern.info kernel: [22065.130694] br-lan: port 1(eth1) entered forwarding state Fri Sep 27 08:34:38 2019 daemon.notice netifd: Network device 'eth1' link is up Fri Sep 27 12:12:45 2019 kern.info kernel: [35152.168595] eth1: link up (100Mbps/Full duplex) Fri Sep 27 12:12:46 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.106 00:13:37:a7:76:8f Fri Sep 27 12:12:46 2019 daemon.warn dnsmasq-dhcp[1451]: Ignoring domain MLTS.LOCAL for DHCP host name MLTS-WS98 Fri Sep 27 12:12:46 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.106 00:13:37:a7:76:8f MLTS-WS98 Fri Sep 27 12:58:28 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: authenticated Fri Sep 27 12:58:28 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: associated (aid 1) Fri Sep 27 12:58:28 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a RADIUS: starting accounting session 19F05E583D4D3AE3 Fri Sep 27 12:58:28 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a WPA: pairwise key handshake completed (RSN) Fri Sep 27 12:58:28 2019 daemon.info dnsmasq-dhcp[1451]: DHCPDISCOVER(br-lan) 58:cb:52:15:48:0a Fri Sep 27 12:58:28 2019 daemon.info dnsmasq-dhcp[1451]: DHCPOFFER(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 12:58:28 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 12:58:28 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.110 58:cb:52:15:48:0a Fri Sep 27 13:04:46 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: disassociated due to inactivity Fri Sep 27 13:04:47 2019 daemon.info hostapd: wlan0-1: STA 58:cb:52:15:48:0a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Fri Sep 27 13:23:39 2019 kern.info kernel: [39405.664144] eth1: link up (10Mbps/Full duplex) Fri Sep 27 14:34:07 2019 daemon.notice netifd: wan (2759): udhcpc: sending renew to 172.16.10.1 Fri Sep 27 14:34:07 2019 daemon.notice netifd: wan (2759): udhcpc: lease of 172.16.10.151 obtained, lease time 86400 Fri Sep 27 15:31:48 2019 kern.info kernel: [47094.197031] eth1: link up (100Mbps/Full duplex) Fri Sep 27 15:31:48 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.106 00:13:37:a7:76:8f Fri Sep 27 15:31:48 2019 daemon.warn dnsmasq-dhcp[1451]: Ignoring domain MLTS.LOCAL for DHCP host name MLTS-WS98 Fri Sep 27 15:31:48 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.106 00:13:37:a7:76:8f MLTS-WS98 Fri Sep 27 16:32:12 2019 kern.info kernel: [50718.509477] eth1: link down Fri Sep 27 16:32:12 2019 kern.info kernel: [50718.513222] br-lan: port 1(eth1) entered disabled state Fri Sep 27 16:32:12 2019 daemon.notice netifd: Network device 'eth1' link is down Fri Sep 27 16:32:13 2019 kern.info kernel: [50719.550715] eth1: link up (10Mbps/Full duplex) Fri Sep 27 16:32:13 2019 kern.info kernel: [50719.555435] br-lan: port 1(eth1) entered blocking state Fri Sep 27 16:32:13 2019 kern.info kernel: [50719.560793] br-lan: port 1(eth1) entered forwarding state Fri Sep 27 16:32:13 2019 daemon.notice netifd: Network device 'eth1' link is up Fri Sep 27 16:53:56 2019 kern.info kernel: [52022.638574] eth1: link up (100Mbps/Full duplex) Fri Sep 27 16:53:56 2019 daemon.info dnsmasq-dhcp[1451]: DHCPREQUEST(br-lan) 172.16.42.106 00:13:37:a7:76:8f Fri Sep 27 16:53:56 2019 daemon.warn dnsmasq-dhcp[1451]: Ignoring domain MLTS.LOCAL for DHCP host name MLTS-WS98 Fri Sep 27 16:53:56 2019 daemon.info dnsmasq-dhcp[1451]: DHCPACK(br-lan) 172.16.42.106 00:13:37:a7:76:8f MLTS-WS98 Fri Sep 27 17:18:33 2019 kern.info kernel: [53498.940580] usb 1-1: new high-speed USB device number 2 using ehci-platform Fri Sep 27 17:18:33 2019 kern.info kernel: [53499.330577] usb 1-1: reset high-speed USB device number 2 using ehci-platform Fri Sep 27 17:18:33 2019 kern.info kernel: [53499.551992] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3071, rev 021c detected Fri Sep 27 17:18:33 2019 kern.info kernel: [53499.650848] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 0008 detected Fri Sep 27 17:18:33 2019 kern.debug kernel: [53499.695470] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' Fri Sep 27 17:18:52 2019 kern.info kernel: [53517.909061] usb 1-1: USB disconnect, device number 2 Fri Sep 27 17:19:00 2019 kern.info kernel: [53525.829937] usb 1-1: new high-speed USB device number 3 using ehci-platform Fri Sep 27 17:19:00 2019 kern.info kernel: [53526.219993] usb 1-1: reset high-speed USB device number 3 using ehci-platform Fri Sep 27 17:19:00 2019 kern.info kernel: [53526.441350] ieee80211 phy3: rt2x00_set_rt: Info - RT chipset 3071, rev 021c detected Fri Sep 27 17:19:00 2019 kern.info kernel: [53526.535272] ieee80211 phy3: rt2x00_set_rf: Info - RF chipset 0008 detected Fri Sep 27 17:19:00 2019 kern.debug kernel: [53526.571056] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' Fri Sep 27 17:19:06 2019 kern.info kernel: [53531.854654] ieee80211 phy3: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' Fri Sep 27 17:19:06 2019 kern.info kernel: [53532.227924] ieee80211 phy3: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 Fri Sep 27 17:19:07 2019 kern.info kernel: [53532.814044] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready Fri Sep 27 17:19:26 2019 kern.info kernel: [53552.242090] device wlan0 left promiscuous mode Fri Sep 27 17:19:26 2019 kern.info kernel: [53552.246731] br-lan: port 2(wlan0) entered disabled state Fri Sep 27 17:19:26 2019 kern.info kernel: [53552.302126] device wlan0-1 left promiscuous mode Fri Sep 27 17:19:26 2019 kern.info kernel: [53552.307075] br-lan: port 3(wlan0-1) entered disabled state Fri Sep 27 17:19:28 2019 daemon.notice netifd: radio2 (4605): command failed: Not supported (-122) Fri Sep 27 17:19:29 2019 daemon.notice netifd: radio2 (4605): command failed: Too many open files in system (-23) Fri Sep 27 17:19:29 2019 kern.info kernel: [53555.310654] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready Fri Sep 27 17:19:29 2019 daemon.notice netifd: radio1 (4646): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Fri Sep 27 17:19:30 2019 kern.info kernel: [53555.942298] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready Fri Sep 27 17:19:30 2019 daemon.notice netifd: radio2 (4605): Successfully initialized wpa_supplicant Fri Sep 27 17:19:31 2019 daemon.notice netifd: radio0 (4729): Configuration file: /var/run/hostapd-phy0.conf Fri Sep 27 17:19:31 2019 kern.info kernel: [53556.956052] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.086975] br-lan: port 2(wlan0) entered blocking state Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.092532] br-lan: port 2(wlan0) entered disabled state Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.098240] device wlan0 entered promiscuous mode Fri Sep 27 17:19:31 2019 daemon.notice netifd: radio0 (4729): Using interface wlan0 with hwaddr 00:13:37:a7:76:8c and ssid "Pineapple_768C" Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.200539] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.207188] br-lan: port 2(wlan0) entered blocking state Fri Sep 27 17:19:31 2019 kern.info kernel: [53557.212645] br-lan: port 2(wlan0) entered forwarding state Fri Sep 27 17:19:31 2019 daemon.notice netifd: radio0 (4729): wlan0: interface state UNINITIALIZED->ENABLED Fri Sep 27 17:19:31 2019 daemon.notice netifd: radio0 (4729): wlan0: AP-ENABLED Fri Sep 27 17:19:32 2019 daemon.notice netifd: radio2 (4605): Interface 1 setup failed: BRIDGE_NOT_ALLOWED Fri Sep 27 17:19:33 2019 kern.info kernel: [53558.873734] wlan2: authenticate with fc:ec:da:a4:ad:3c Fri Sep 27 17:19:33 2019 kern.info kernel: [53558.984617] wlan2: send auth to fc:ec:da:a4:ad:3c (try 1/3) Fri Sep 27 17:19:33 2019 kern.info kernel: [53558.998033] wlan2: authenticated Fri Sep 27 17:19:33 2019 kern.info kernel: [53559.009190] wlan2: associate with fc:ec:da:a4:ad:3c (try 1/3) Fri Sep 27 17:19:33 2019 kern.info kernel: [53559.026687] wlan2: RX AssocResp from fc:ec:da:a4:ad:3c (capab=0x431 status=0 aid=5) Fri Sep 27 17:19:33 2019 kern.info kernel: [53559.047231] wlan2: associated Fri Sep 27 17:19:33 2019 kern.info kernel: [53559.062593] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready Fri Sep 27 17:19:33 2019 daemon.notice netifd: radio0 (4729): OK Fri Sep 27 17:19:33 2019 daemon.notice netifd: radio0 (4729): OK Fri Sep 27 17:19:33 2019 daemon.notice netifd: radio0 (4729): OK Fri Sep 27 17:19:33 2019 daemon.notice netifd: radio0 (4729): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Fri Sep 27 17:19:33 2019 daemon.notice netifd: radio0 (4729): Failed to connect to hostapd - wpa_ctrl_open: No such file or directory Fri Sep 27 17:19:33 2019 daemon.notice netifd: Network device 'wlan0' link is up Fri Sep 27 17:19:41 2019 daemon.notice netifd: Network device 'eth0' link is down Fri Sep 27 17:19:41 2019 daemon.notice netifd: Interface 'wan' has link connectivity loss Fri Sep 27 17:19:41 2019 daemon.notice netifd: Interface 'wan6' has link connectivity loss Fri Sep 27 17:19:41 2019 daemon.notice netifd: Interface 'wan6' is now down Fri Sep 27 17:19:41 2019 kern.info kernel: [53566.859687] eth0: link down Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: reading /tmp/resolv.conf.auto Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain test Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain onion Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain localhost Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain local Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain invalid Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain bind Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using local addresses only for domain lan Fri Sep 27 17:19:41 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Fri Sep 27 17:19:41 2019 daemon.notice netifd: wan (2759): udhcpc: received SIGTERM Fri Sep 27 17:19:41 2019 daemon.notice netifd: Interface 'wan' is now down Fri Sep 27 17:19:42 2019 kern.info kernel: [53568.070857] wlan2: deauthenticating from fc:ec:da:a4:ad:3c by local choice (Reason: 3=DEAUTH_LEAVING) Fri Sep 27 17:19:43 2019 daemon.notice netifd: radio2 (4942): command failed: Not supported (-122) Fri Sep 27 17:19:44 2019 daemon.notice netifd: radio2 (4942): command failed: Too many open files in system (-23) Fri Sep 27 17:19:45 2019 kern.info kernel: [53570.921461] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready Fri Sep 27 17:19:45 2019 daemon.notice netifd: radio2 (4942): Successfully initialized wpa_supplicant Fri Sep 27 17:19:47 2019 daemon.notice netifd: radio2 (4942): Interface 1 setup failed: BRIDGE_NOT_ALLOWED Fri Sep 27 17:19:47 2019 daemon.notice netifd: Interface 'wwan' is enabled Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.794487] wlan2: authenticate with fc:ec:da:a4:ad:3c Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.914117] wlan2: send auth to fc:ec:da:a4:ad:3c (try 1/3) Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.923163] wlan2: authenticated Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.929145] wlan2: associate with fc:ec:da:a4:ad:3c (try 1/3) Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.939204] wlan2: RX AssocResp from fc:ec:da:a4:ad:3c (capab=0x431 status=0 aid=5) Fri Sep 27 17:19:48 2019 kern.info kernel: [53573.973611] wlan2: associated Fri Sep 27 17:19:48 2019 daemon.notice netifd: Network device 'wlan2' link is up Fri Sep 27 17:19:48 2019 daemon.notice netifd: Interface 'wwan' has link connectivity Fri Sep 27 17:19:48 2019 daemon.notice netifd: Interface 'wwan' is setting up now Fri Sep 27 17:19:48 2019 daemon.notice netifd: wwan (5077): udhcpc: started, v1.30.1 Fri Sep 27 17:19:48 2019 daemon.notice netifd: wwan (5077): udhcpc: sending discover Fri Sep 27 17:19:49 2019 kern.info kernel: [53574.953470] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready Fri Sep 27 17:19:51 2019 daemon.notice netifd: wwan (5077): udhcpc: sending discover Fri Sep 27 17:19:54 2019 daemon.notice netifd: wwan (5077): udhcpc: sending discover Fri Sep 27 17:19:57 2019 daemon.notice netifd: wwan (5077): udhcpc: sending select for 172.16.99.142 Fri Sep 27 17:19:58 2019 daemon.notice netifd: wwan (5077): udhcpc: lease of 172.16.99.142 obtained, lease time 86400 Fri Sep 27 17:19:58 2019 daemon.notice netifd: Interface 'wwan' is now up Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: reading /tmp/resolv.conf.auto Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain test Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain onion Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain localhost Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain local Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain invalid Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain bind Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using local addresses only for domain lan Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using nameserver 8.8.4.4#53 Fri Sep 27 17:19:58 2019 daemon.info dnsmasq[1451]: using nameserver 172.16.99.1#53 Fri Sep 27 17:19:59 2019 user.notice firewall: Reloading firewall due to ifup of wwan (wlan2) Fri Sep 27 17:20:32 2019 kern.info kernel: [53618.147326] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. Fri Sep 27 17:26:50 2019 daemon.warn dnsmasq-dhcp[1451]: no address range available for DHCP request via wlan2 Link to comment Share on other sites More sharing options...
Cap_Sig Posted September 28, 2019 Share Posted September 28, 2019 16 hours ago, skifire said: I just downgraded to 2.4.1 and it;s working as expected. I have added my sys log from when I was having the issue in case it's helpful. Thanks for info. 2.4.1 has been reporting working and some modules in that version as well. If you updated to 2.6.1 with OTA it has been noted to cause some issues. To try version 2.6.1 recommend doing a manual upgrade: https://docs.hak5.org/hc/en-us/articles/360025819673-Manual-Firmware-Installation (modules still not all functional in firmware 2.6.1) Link to comment Share on other sites More sharing options...
ki2k Posted December 4, 2019 Share Posted December 4, 2019 I know Hak5 is a "small company", that comes up often and I appreciate it. But as a long-time Pineapple user, I do wish that Hak5 would actually test the community modules that by now are defacto standard parts of the Pineapple experience and be very transparent about what breaks with each new release. To blame the functional gaps on the original module authors not keeping up may be arguably valid, but it does feel like a cop out sometimes. I'm not trying to pick a fight or raise the ire of the Hak5 fan club- but am suggesting that by now in the Pineapple evolution, the more common modules have come to be so deeply associated with the Pineapple they should be somehow either integrated as part of the code build and therefor made good before upgrade, or at least thoroughly tested by Hak5 with a big red warning shown next to the new release notes. Something like "WARNING- THESE MODULES ARE NOT YET WORKING/RELIABLE ON THIS NEW CODE VERSION: xxxx, yyyyy, zzzz" rather than have us all find out after the upgrade. One man's opinion, meant constructively, after finding that 2.6.1 renders the device extremely frustrating/darn near useless. Link to comment Share on other sites More sharing options...
Newbier Posted December 5, 2019 Share Posted December 5, 2019 On 9/19/2019 at 6:07 AM, Ven0mRat said: Device: Wifi pineapple tetra [latest firmware] I cant even capture handshake with recon or Site Survey, deauth works but I dont get handshake anytime (tested on my devices and network) so this device dont have a sense now, pineapple dont see my usb external storage, dwall dont work (when I click enable and start listening I only see loading logo anytime and nothing is happen) I have this more. Please FIX that or tell me how to do that because for now I use that as my new router. You wasted your money buying their hardware i done the same the hardware in hak5 store can be replicated with other hardware and opensource software Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.