JediMasterX Posted June 11, 2018 Share Posted June 11, 2018 ok, after 2 tries: 1.i thought my rl 5070 wireless adpater is dead, so i just switched to the second one i had. nope, Still the client mode isnt working. did a factory reset.. thenn a full blown firmware rest... the point is, its working for the first time i fire up the device, i setup everything and when i tried to connect to a newtwork it just froze, and doesnt work since. plugged to 2 usb ports aswell. br-lan Link encap:Ethernet HWaddr 00:C0:CA:8F:9A:AE inet addr:172.16.42.1 Bcast:172.16.42.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:38464 errors:0 dropped:0 overruns:0 frame:0 TX packets:32059 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9897922 (9.4 MiB) TX bytes:30964976 (29.5 MiB) eth0 Link encap:Ethernet HWaddr 00:C0:CA:8F:9A:AE UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:33461 errors:0 dropped:0 overruns:0 frame:0 TX packets:31580 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9694506 (9.2 MiB) TX bytes:30682155 (29.2 MiB) Interrupt:4 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:111 errors:0 dropped:0 overruns:0 frame:0 TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8332 (8.1 KiB) TX bytes:8332 (8.1 KiB) wlan0 Link encap:Ethernet HWaddr 00:C0:CA:8F:69:31 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:2002 (1.9 KiB) wlan1 Link encap:Ethernet HWaddr 00:C0:CA:8F:84:8C UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) [ 0.000000] Linux version 3.18.84 (@f818d65006a1) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 unknown) ) #91 Fri May 25 03:59:51 UTC 2018 [ 0.000000] MyLoader: sysp=8a14b024, boardp=44b65156, parts=b69f8d32 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU0 revision is: 00019374 (MIPS 24Kc) [ 0.000000] SoC: Atheros AR9330 rev 1 [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 04000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x03ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x03ffffff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x03ffffff] [ 0.000000] On node 0 totalpages: 16384 [ 0.000000] free_area_init_node: node 0, pgdat 80365cf0, node_mem_map 81000000 [ 0.000000] Normal zone: 128 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 16384 pages, LIFO batch:3 [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [ 0.000000] Kernel command line: board=PINEAPPLE-NANO console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd [ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes) [ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Writing ErrCtl register=00000000 [ 0.000000] Readback ErrCtl register=00000000 [ 0.000000] Memory: 60880K/65536K available (2524K kernel code, 143K rwdata, 540K rodata, 240K init, 188K bss, 4656K reserved, 0K cma-reserved) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz [ 0.000000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) [ 0.080000] pid_max: default: 32768 minimum: 301 [ 0.080000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.100000] NET: Registered protocol family 16 [ 0.100000] MIPS: machine is WiFi Pineapple NANO [ 0.380000] Switched to clocksource MIPS [ 0.380000] NET: Registered protocol family 2 [ 0.390000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.390000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 0.400000] TCP: Hash tables configured (established 1024 bind 1024) [ 0.400000] TCP: reno registered [ 0.410000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.410000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.420000] NET: Registered protocol family 1 [ 0.420000] PCI: CLS 0 bytes, default 32 [ 0.420000] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.440000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.440000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.450000] msgmni has been set to 118 [ 0.460000] io scheduler noop registered [ 0.460000] io scheduler deadline registered (default) [ 0.470000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled [ 0.470000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a AR933X UART [ 0.480000] console [ttyATH0] enabled [ 0.490000] bootconsole [early0] disabled [ 0.500000] m25p80 spi0.0: found mx25l12805d, expected m25p80 [ 0.500000] m25p80 spi0.0: mx25l12805d (16384 Kbytes) [ 0.520000] 5 tp-link partitions found on MTD device spi0.0 [ 0.520000] Creating 5 MTD partitions on "spi0.0": [ 0.520000] 0x000000000000-0x000000020000 : "u-boot" [ 0.530000] 0x000000020000-0x00000013af6c : "kernel" [ 0.540000] 0x00000013af6c-0x000000ff0000 : "rootfs" [ 0.540000] mtd: device 2 (rootfs) set to be root filesystem [ 0.540000] 1 squashfs-split partitions found on MTD device rootfs [ 0.550000] 0x000000d80000-0x000000ff0000 : "rootfs_data" [ 0.560000] 0x000000ff0000-0x000001000000 : "art" [ 0.560000] 0x000000020000-0x000000ff0000 : "firmware" [ 0.590000] libphy: ag71xx_mdio: probed [ 1.190000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY] [ 1.200000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII [ 1.200000] TCP: cubic registered [ 1.200000] NET: Registered protocol family 17 [ 1.210000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 1.220000] 8021q: 802.1Q VLAN Support v1.8 [ 1.230000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 1.240000] Freeing unused kernel memory: 240K [ 2.820000] init: Console is alive [ 2.820000] init: - watchdog - [ 5.520000] usbcore: registered new interface driver usbfs [ 5.520000] usbcore: registered new interface driver hub [ 5.530000] usbcore: registered new device driver usb [ 5.580000] SCSI subsystem initialized [ 5.590000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.600000] ehci-platform: EHCI generic platform driver [ 5.600000] ehci-platform ehci-platform: EHCI Host Controller [ 5.610000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 5.620000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 [ 5.640000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 [ 5.640000] hub 1-0:1.0: USB hub found [ 5.640000] hub 1-0:1.0: 1 port detected [ 5.650000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.660000] ohci-platform: OHCI generic platform driver [ 5.670000] uhci_hcd: USB Universal Host Controller Interface driver [ 5.680000] usbcore: registered new interface driver usb-storage [ 5.920000] init: - preinit - [ 6.030000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 6.520000] hub 1-1:1.0: USB hub found [ 6.520000] hub 1-1:1.0: 4 ports detected [ 6.700000] random: procd urandom read with 11 bits of entropy available [ 6.960000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform [ 6.980000] mount_root: loading kmods from internal overlay [ 7.280000] usb 1-1.2: new high-speed USB device number 4 using ehci-platform [ 7.310000] jffs2: notice: (327) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 2 of xref (0 dead, 0 orphan) found. [ 7.320000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 7.340000] block: extroot: not configured [ 7.380000] jffs2: notice: (324) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 2 of xref (0 dead, 0 orphan) found. [ 7.410000] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 7.420000] scsi host0: usb-storage 1-1.2:1.0 [ 7.520000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab [ 7.530000] block: extroot: not configured [ 7.540000] mount_root: switching to jffs2 overlay [ 7.600000] procd: - early - [ 7.600000] procd: - watchdog - [ 8.420000] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 8.580000] procd: - ubus - [ 8.950000] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ 8.950000] sd 0:0:0:0: [sda] Write Protect is off [ 8.960000] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ 8.970000] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 8.980000] sda: sda1 sda2 [ 9.000000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 9.600000] procd: - init - [ 12.110000] EXT4-fs (sda1): recovery complete [ 12.130000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: [ 12.460000] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities [ 12.520000] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities [ 12.570000] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 13.000000] Adding 1004024k swap on /dev/sdcard/sd2. Priority:-1 extents:1 across:1004024k [ 14.110000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68 [ 14.110000] Backport generated by backports.git backports-20151218-0-g2f58d9d [ 14.270000] ath: EEPROM regdomain: 0x0 [ 14.270000] ath: EEPROM indicates default country code should be used [ 14.270000] ath: doing EEPROM country->regdmn map search [ 14.270000] ath: country maps to regdmn code: 0x3a [ 14.270000] ath: Country alpha2 being used: US [ 14.270000] ath: Regpair used: 0x3a [ 14.280000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 14.280000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2 [ 14.310000] usb 1-1.1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested [ 14.320000] usbcore: registered new interface driver ath9k_htc [ 14.450000] RPC: Registered named UNIX socket transport module. [ 14.450000] RPC: Registered udp transport module. [ 14.450000] RPC: Registered tcp transport module. [ 14.460000] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 14.490000] tun: Universal TUN/TAP device driver, 1.6 [ 14.490000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 14.540000] usbcore: registered new interface driver rt2800usb [ 14.560000] usbcore: registered new interface driver rtl8187 [ 14.620000] usbcore: registered new interface driver rtl8192cu [ 14.670000] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 14.690000] usbcore: registered new interface driver cdc_acm [ 14.700000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 14.710000] usbcore: registered new interface driver cdc_wdm [ 14.740000] nf_conntrack version 0.5.0 (955 buckets, 3820 max) [ 14.810000] usbcore: registered new interface driver ums-alauda [ 14.820000] usbcore: registered new interface driver ums-cypress [ 14.830000] usbcore: registered new interface driver ums-datafab [ 14.840000] usbcore: registered new interface driver ums-freecom [ 14.850000] usbcore: registered new interface driver ums-isd200 [ 14.850000] usbcore: registered new interface driver ums-jumpshot [ 14.860000] usbcore: registered new interface driver ums-karma [ 14.870000] usbcore: registered new interface driver ums-sddr09 [ 14.880000] usbcore: registered new interface driver ums-sddr55 [ 14.890000] usbcore: registered new interface driver ums-usbat [ 14.910000] usbcore: registered new interface driver usbserial [ 14.910000] usbcore: registered new interface driver usbserial_generic [ 14.920000] usbserial: USB Serial support registered for generic [ 14.980000] xt_time: kernel timezone is -0000 [ 14.980000] usbcore: registered new interface driver asix [ 14.990000] usb 1-1.1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008 [ 15.000000] usbcore: registered new interface driver ax88179_178a [ 15.010000] usbcore: registered new interface driver cdc_ether [ 15.020000] ip_tables: (C) 2000-2006 Netfilter Core Team [ 15.050000] usbcore: registered new interface driver pl2303 [ 15.050000] usbserial: USB Serial support registered for pl2303 [ 15.060000] PPP generic driver version 2.4.2 [ 15.070000] NET: Registered protocol family 24 [ 15.080000] usbcore: registered new interface driver qmi_wwan [ 15.090000] usbcore: registered new interface driver rndis_host [ 15.100000] usbcore: registered new interface driver sierra_net [ 15.110000] usbcore: registered new interface driver option [ 15.110000] usbserial: USB Serial support registered for GSM modem (1-port) [ 15.230000] ath9k_htc 1-1.1:1.0: ath9k_htc: HTC initialized with 33 credits [ 15.480000] ath9k_htc 1-1.1:1.0: ath9k_htc: FW Version: 1.4 [ 15.480000] ath9k_htc 1-1.1:1.0: FW RMW support: On [ 15.480000] ath: EEPROM regdomain: 0x0 [ 15.480000] ath: EEPROM indicates default country code should be used [ 15.480000] ath: doing EEPROM country->regdmn map search [ 15.480000] ath: country maps to regdmn code: 0x3a [ 15.480000] ath: Country alpha2 being used: US [ 15.480000] ath: Regpair used: 0x3a [ 15.490000] ieee80211 phy1: Atheros AR9271 Rev:1 [ 16.620000] random: nonblocking pool is initialized [ 26.050000] device eth0 entered promiscuous mode [ 28.360000] eth0: link up (100Mbps/Full duplex) [ 28.360000] br-lan: port 1(eth0) entered forwarding state [ 28.370000] br-lan: port 1(eth0) entered forwarding state [ 30.370000] br-lan: port 1(eth0) entered forwarding state [ 31.580000] device wlan0 entered promiscuous mode [ 31.630000] br-lan: port 2(wlan0) entered forwarding state [ 31.640000] br-lan: port 2(wlan0) entered forwarding state [ 31.690000] device wlan0-1 entered promiscuous mode [ 31.700000] br-lan: port 3(wlan0-1) entered forwarding state [ 31.700000] br-lan: port 3(wlan0-1) entered forwarding state [ 32.720000] br-lan: port 3(wlan0-1) entered disabled state [ 33.630000] br-lan: port 3(wlan0-1) entered forwarding state [ 33.640000] br-lan: port 3(wlan0-1) entered forwarding state [ 33.640000] br-lan: port 2(wlan0) entered forwarding state [ 35.640000] br-lan: port 3(wlan0-1) entered forwarding state [ 41.550000] device br-lan entered promiscuous mode [ 1637.320000] br-lan: port 3(wlan0-1) entered disabled state [ 1637.330000] device wlan0-1 left promiscuous mode [ 1637.330000] br-lan: port 3(wlan0-1) entered disabled state [ 1637.580000] device wlan0 left promiscuous mode [ 1637.590000] br-lan: port 2(wlan0) entered disabled state [ 1640.710000] device wlan0 entered promiscuous mode [ 1640.760000] br-lan: port 2(wlan0) entered forwarding state [ 1640.760000] br-lan: port 2(wlan0) entered forwarding state [ 1640.850000] device wlan0-1 entered promiscuous mode [ 1640.860000] br-lan: port 3(wlan0-1) entered forwarding state [ 1640.870000] br-lan: port 3(wlan0-1) entered forwarding state [ 1641.680000] br-lan: port 3(wlan0-1) entered disabled state [ 1642.760000] br-lan: port 2(wlan0) entered forwarding state [ 1643.160000] br-lan: port 3(wlan0-1) entered forwarding state [ 1643.160000] br-lan: port 3(wlan0-1) entered forwarding state [ 1645.160000] br-lan: port 3(wlan0-1) entered forwarding state [ 1647.540000] br-lan: port 3(wlan0-1) entered disabled state [ 1649.160000] device wlan0-1 left promiscuous mode [ 1649.170000] br-lan: port 3(wlan0-1) entered disabled state [ 1649.470000] device wlan0 left promiscuous mode [ 1649.470000] br-lan: port 2(wlan0) entered disabled state [ 1656.500000] device wlan0 entered promiscuous mode [ 1656.800000] br-lan: port 2(wlan0) entered forwarding state [ 1656.810000] br-lan: port 2(wlan0) entered forwarding state [ 1657.030000] device wlan0-1 entered promiscuous mode [ 1657.090000] br-lan: port 3(wlan0-1) entered forwarding state [ 1657.090000] br-lan: port 3(wlan0-1) entered forwarding state [ 1657.180000] br-lan: port 3(wlan0-1) entered disabled state [ 1658.810000] br-lan: port 2(wlan0) entered forwarding state [ 1662.590000] br-lan: port 2(wlan0) entered disabled state [ 1662.690000] device wlan0 left promiscuous mode [ 1662.690000] br-lan: port 2(wlan0) entered disabled state [ 1662.750000] br-lan: port 3(wlan0-1) entered disabled state [ 1662.880000] device wlan0-1 left promiscuous mode [ 1662.880000] br-lan: port 3(wlan0-1) entered disabled state [ 1663.950000] eth0: link down [ 1664.220000] br-lan: port 1(eth0) entered disabled state [ 1664.950000] eth0: link up (100Mbps/Full duplex) [ 1664.950000] br-lan: port 1(eth0) entered forwarding state [ 1664.960000] br-lan: port 1(eth0) entered forwarding state [ 1666.960000] br-lan: port 1(eth0) entered forwarding state [ 3175.200000] device wlan0 entered promiscuous mode [ 3175.200000] br-lan: port 2(wlan0) entered forwarding state [ 3175.210000] br-lan: port 2(wlan0) entered forwarding state [ 3177.210000] br-lan: port 2(wlan0) entered forwarding state [ 3326.020000] device wlan0 left promiscuous mode [ 3326.030000] br-lan: port 2(wlan0) entered disabled state [ 3327.020000] eth0: link down [ 3327.040000] br-lan: port 1(eth0) entered disabled state [ 3327.670000] device wlan0 entered promiscuous mode [ 3327.670000] br-lan: port 2(wlan0) entered forwarding state [ 3327.680000] br-lan: port 2(wlan0) entered forwarding state [ 3328.020000] eth0: link up (100Mbps/Full duplex) [ 3328.020000] br-lan: port 1(eth0) entered forwarding state [ 3328.030000] br-lan: port 1(eth0) entered forwarding state [ 3329.680000] br-lan: port 2(wlan0) entered forwarding state [ 3330.030000] br-lan: port 1(eth0) entered forwarding state [ 3342.020000] device wlan0 left promiscuous mode [ 3342.030000] br-lan: port 2(wlan0) entered disabled state [ 3343.910000] device wlan0 entered promiscuous mode [ 3343.910000] br-lan: port 2(wlan0) entered forwarding state [ 3343.920000] br-lan: port 2(wlan0) entered forwarding state [ 3344.020000] eth0: link down [ 3344.670000] br-lan: port 1(eth0) entered disabled state [ 3345.920000] br-lan: port 2(wlan0) entered forwarding state [ 3346.020000] eth0: link up (100Mbps/Full duplex) [ 3346.020000] br-lan: port 1(eth0) entered forwarding state [ 3346.030000] br-lan: port 1(eth0) entered forwarding state [ 3348.030000] br-lan: port 1(eth0) entered forwarding state [ 3356.460000] device wlan0 left promiscuous mode [ 3356.460000] br-lan: port 2(wlan0) entered disabled state [ 3357.270000] device wlan0 entered promiscuous mode [ 3357.270000] br-lan: port 2(wlan0) entered forwarding state [ 3357.280000] br-lan: port 2(wlan0) entered forwarding state [ 3358.020000] eth0: link down [ 3358.020000] br-lan: port 1(eth0) entered disabled state [ 3359.020000] eth0: link up (100Mbps/Full duplex) [ 3359.020000] br-lan: port 1(eth0) entered forwarding state [ 3359.030000] br-lan: port 1(eth0) entered forwarding state [ 3359.280000] br-lan: port 2(wlan0) entered forwarding state [ 3361.030000] br-lan: port 1(eth0) entered forwarding state help me fix it Sebb :) thanks for the hard work btw, JMX Link to comment Share on other sites More sharing options...
Just_a_User Posted June 11, 2018 Share Posted June 11, 2018 11 minutes ago, JediMasterX said: help me fix it how are you powering your Nano? Link to comment Share on other sites More sharing options...
JediMasterX Posted June 12, 2018 Share Posted June 12, 2018 7 hours ago, Just_a_User said: how are you powering your Nano? When i connect to my laptop- its 2 usb ports. On the go- 10,000mAh juice pack with quick charge. *both of these ways worked in the past firmware JMX Link to comment Share on other sites More sharing options...
Just_a_User Posted June 12, 2018 Share Posted June 12, 2018 3 hours ago, JediMasterX said: *both of these ways worked in the past firmware Not saying thats the issue, its just a good place to start checking. From your logs it looks as though the dongle isnt recognized by the pineapple as it hasn't populated wlan2 in ifconfig or dmesg. So either its not powering up (check on another machine) or its driver isnt present on the pineapples? from the wiki - " Compatible chipsets include RaLink RT2800 devices, as well as some Atheros and RealTek devices. Wireless adapters from HakShop.com are certified to work with the WiFi Pineapple" My RT chipset 5390 and RT chipset 3070 are working well on NANO/TETRA - both seem to use the driver for rt2870. Link to comment Share on other sites More sharing options...
JediMasterX Posted June 12, 2018 Share Posted June 12, 2018 37 minutes ago, Just_a_User said: Not saying thats the issue, its just a good place to start checking. From your logs it looks as though the dongle isnt recognized by the pineapple as it hasn't populated wlan2 in ifconfig or dmesg. So either its not powering up (check on another machine) or its driver isnt present on the pineapples? from the wiki - " Compatible chipsets include RaLink RT2800 devices, as well as some Atheros and RealTek devices. Wireless adapters from HakShop.com are certified to work with the WiFi Pineapple" My RT chipset 5390 and RT chipset 3070 are working well on NANO/TETRA - both seem to use the driver for rt2870. Hi man, thanks for the replay. Both plugs work on my laptop when i plug them in. It seems like the drivers..? How do i reinstall them? Thanks a bunch. JMX Link to comment Share on other sites More sharing options...
Just_a_User Posted June 12, 2018 Share Posted June 12, 2018 9 hours ago, JediMasterX said: How do i reinstall them? Thanks a bunch. I haven't successfully managed that myself. I would contact the DEV team to see if they can assist you. Are you 100% sure those adapters used to work on the older firmware? If so maybe it was removed for a reason. I dont have one so cant play. I would say your path of least resistance is to use different (compatible) adapters. Link to comment Share on other sites More sharing options...
JediMasterX Posted June 12, 2018 Share Posted June 12, 2018 9 hours ago, Just_a_User said: Not saying thats the issue, its just a good place to start checking. From your logs it looks as though the dongle isnt recognized by the pineapple as it hasn't populated wlan2 in ifconfig or dmesg. So either its not powering up (check on another machine) or its driver isnt present on the pineapples? from the wiki - " Compatible chipsets include RaLink RT2800 devices, as well as some Atheros and RealTek devices. Wireless adapters from HakShop.com are certified to work with the WiFi Pineapple" My RT chipset 5390 and RT chipset 3070 are working well on NANO/TETRA - both seem to use the driver for rt2870. ok - now live testing': Bus 001 Device 006: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Bus 001 Device 005: ID 05e3:0745 Genesys Logic, Inc. Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 1-thats after rest, and the wlan2 is now connected. 2-rying reset ( no moduls installed and anything) still here and working 3 installing - updated pineap and notes. ConnectedClients 1.4 Connected Clients is an infusion for the Wifi Pineapple that gives information about connected clients 32.0K r3dfish GUI DNSMasq Spoof 1.0 Forge replies to arbitrary DNS queries using DNSMasq 25.5K Whistle Master GUI DNSspoof 1.3 Forge replies to arbitrary DNS queries using DNSspoof 31.5K Whistle Master GUI Deauth 1.5 Deauthentication attacks of all devices connected to APs nearby 72.0K Whistle Master GUI Evil Portal 2.1 An Evil Captive Portal. 141.0K newbi3 GUI Log Manager 1.2 Manage all modules logs 32.0K Whistle Master GUI Online Hash Crack 1.3 Submit Hash and WPA Handshake to www.onlinehashcrack.com web service 56.0K Whistle Master GUI Themes 1.0 Create, download, and share custom themes. 312.0K trashbo4t GUI nmap 1.6 GUI for security scanner nmap 33.0K Whistle Master GUI reset device - still here installing dependencis on sd. resetting still working pushed via cli evil portals set dnspoof and evilportal to run on startup (dnsspoof is set to br-lan) reset aaand... no wlan2. WTF. disable auto start at boot for both reset its BACK AGAIN.. DNSMaskSpoof is auto + Evilportal auto on boot. reset Both working and With CLINT MODE wlan2 is still active... initiating PineAP wlan1 all WORKING. now, please share with me (noob) what and why this is? whats the diffrence between the two? both seems to work same same and DNSspoof is the issue... again, i changed it to br--lan interface JMX Link to comment Share on other sites More sharing options...
Just_a_User Posted June 12, 2018 Share Posted June 12, 2018 45 minutes ago, JediMasterX said: now, please share with me (noob) what and why this is? whats the diffrence between the two? both seems to work same same and DNSspoof is the issue... I dont know - all i would say is this. Its not a driver issue ? thats good news! At the moment the firmware has overtaken most of the community module development. A lot of the community modules (not all) have been slightly borked by the latest firmware and it could well be tied to that, not sure how/why - yet and i may never know ? So in short if you cant get wlan2 to freak out and go AWOL when no community modules are installed then its not likely a firmware issue. I will install DNS spoof now and give it go and see if i can get that to kill my wlan2 and maybe we can pin it down to a specific action then we can investigate the module code and see if there are more clues. Link to comment Share on other sites More sharing options...
JediMasterX Posted June 12, 2018 Share Posted June 12, 2018 Cool. Hope its not Noobcity action going all over. Thanks, JMX Link to comment Share on other sites More sharing options...
Just_a_User Posted June 12, 2018 Share Posted June 12, 2018 23 minutes ago, JediMasterX said: Cool. Hope its not Noobcity action going all over. Just doing some (very) quick basic things with DNSspoof and my wlan2 seems solid... You installed so many modules and set a fair few things which introduced many variables - that makes it much harder to pin it down. I would try and do things one by one and keep an eye on wlan2 while watching logread and dmesg output. Maybe you can get lucky and catch it when its happening/just happened. I cant spend much more time on it for now, sorry. Link to comment Share on other sites More sharing options...
Just_a_User Posted June 14, 2018 Share Posted June 14, 2018 NOTES - when adding notes to connected clients the notes enter into AP (BSSID) notes on the notes page of the UI. Link to comment Share on other sites More sharing options...
aethernaut Posted June 20, 2018 Share Posted June 20, 2018 Hi all, FW 2.1.0 with sys updates from Module Manager. Only one module downloaded which is SiteSurvey With reference to: and other posts thereafter... Summary: SiteSurvey does not appear to work with the new firmware or the new firmware does not appear to allow SiteSurvey to work Does anyone know if: The new Pineapple firmware needs to be fixed to support the Site Survey module? The Site Survey module needs to be fixed to work with the new Pineapple firmware? If either of the above are happening / will happen / may happen? As this question applies to the firmware as well as the module I have posted it here rather than both here and the SiteSurvey area. Many thanks... Link to comment Share on other sites More sharing options...
Just_a_User Posted June 20, 2018 Share Posted June 20, 2018 19 minutes ago, aethernaut said: The new Pineapple firmware needs to be fixed to support the Site Survey module? No AFAIK the Firmware takes the lead and community modules follow. 19 minutes ago, aethernaut said: The Site Survey module needs to be fixed to work with the new Pineapple firmware? Yes, a fair few of @Whistle Master's modules need tweaking to work 100% with the latest firmware. Some just need tweaks some need a deeper look. Hopefully whistle master picks them up and brings them up to date, or another developer steps in. These are community modules not official modules from the HAK5 dev team. 19 minutes ago, aethernaut said: If either of the above are happening / will happen / may happen? Fingers crossed, although to be honest as they are community modules its not guaranteed. But it could be new modules are born and old ones are left to die ? a lot of functions are still possible from terminal if you know the tools but aren't as convenient as the GUI. Link to comment Share on other sites More sharing options...
aethernaut Posted June 21, 2018 Share Posted June 21, 2018 @Just_a_User Thanks for the reply. On 6/20/2018 at 8:57 PM, Just_a_User said: a lot of functions are still possible from terminal if you know the tools but aren't as convenient as the GUI. The ability to operate the Nano in a more "tactical" manner through the management interface using a phone or tablet was what attracted me to the device more than anything else. If I am going to use tools via a terminal then I'll use a laptop with an decent wifi adapter (decent compared to the wifi in the laptop - I'm not making snarky comments about the Nano!). I can see that the Nano is primarily a MITM device but it was useful to have a basic packet capturing ability as provided by Site Survey. On 6/20/2018 at 8:57 PM, Just_a_User said: Fingers crossed, although to be honest as they are community modules its not guaranteed. But it could be new modules are born and old ones are left to die Sad but true. I'll just have to wait and see ... Link to comment Share on other sites More sharing options...
Just_a_User Posted June 21, 2018 Share Posted June 21, 2018 1 hour ago, aethernaut said: The ability to operate the Nano in a more "tactical" manner through the management interface using a phone or tablet was what attracted me to the device more than anything else I do use mine in this way for both official modules but also using a terminal emulator on my mobile. you can obviously script more common/repetative tasks to streamline things a little. Its still more stealthy than a laptop and wifi adapter if a little awkward. But as you say the pineapples are great for MITM, especially when combined with a laptop. If you share Internet through the laptop you can easily monitor packets live with wireshark, run bettercap etc.. but thats not the stealthiest option. If you just need to capture packets you can always use tcpdump on the pineapple itself. Or if you need to capture handshakes you could use the aircrack-ng suite or maybe wifite2 would help. Hope this gives you something to try while waiting to see if some of the community modules are tweaked. Link to comment Share on other sites More sharing options...
Sebkinne Posted June 22, 2018 Author Share Posted June 22, 2018 Hi everyone, We have just released firmware v2.1.1 with a whole bunch of bugfixes. Please see the first post of this thread for more details. Link to comment Share on other sites More sharing options...
kleo Posted June 22, 2018 Share Posted June 22, 2018 Master Seb I'm still on 2.0.2, can I flash 2.1.1 straight away? Link to comment Share on other sites More sharing options...
b0N3z Posted June 22, 2018 Share Posted June 22, 2018 2 hours ago, kbeflo said: Master Seb I'm still on 2.0.2, can I flash 2.1.1 straight away? move the new firmware upgrade file to /tmp and run $sysupgrade -n /tmp/upgrade2.1.1.bin Link to comment Share on other sites More sharing options...
Just_a_User Posted June 22, 2018 Share Posted June 22, 2018 I upgraded from 2.1.0 to 2.1.1 and im getting issues with PineAP - I just want to gather SSID's but it wont start without checking allowing associations. Logs reflect the same. When i get a min i will re flash and try again. Link to comment Share on other sites More sharing options...
Sebkinne Posted June 22, 2018 Author Share Posted June 22, 2018 7 hours ago, kbeflo said: Master Seb I'm still on 2.0.2, can I flash 2.1.1 straight away? Yup, you can flash straight from the GUI, no sysupgrade needed. Link to comment Share on other sites More sharing options...
Sebkinne Posted June 22, 2018 Author Share Posted June 22, 2018 2 hours ago, Just_a_User said: I upgraded from 2.1.0 to 2.1.1 and im getting issues with PineAP - I just want to gather SSID's but it wont start without checking allowing associations. Logs reflect the same. When i get a min i will re flash and try again. What were your filters set to? Filters now also prevent logging and SSID harvesting, so if your filters are set to allow (the default), it'll only log the allowed MACs. Link to comment Share on other sites More sharing options...
Just_a_User Posted June 22, 2018 Share Posted June 22, 2018 2 minutes ago, Sebkinne said: What were your filters set to? Filters now also prevent logging and SSID harvesting, so if your filters are set to allow (the default), it'll only log the allowed MACs. Good point, just removed my devices MAC's and set to deny for test. still doesn't harvest ssid's unless i have allow associations checked. It persisted across a reboot and factory reset for me. Tomorrow i will firmware recover and update and see if it sorts it out. Link to comment Share on other sites More sharing options...
Sebkinne Posted June 22, 2018 Author Share Posted June 22, 2018 Hi everyone, Thanks to @Just_a_User, we were able to catch a bug with firmware 2.1.1 early on, and have decided to release 2.1.2 in it's place, containing the fix. My apologies for this. Link to comment Share on other sites More sharing options...
theUNK0WN Posted June 23, 2018 Share Posted June 23, 2018 Not sure if someone has posted already about this issue ( haven't looked yet; in Q&A) but there's a problem with the management AP and open ssid being "filtered" for the owner. After flashing to the update '2.1.2', I've set the management AP and open ssid name during setup (while having wireless disabled) and saved my progress. When I logged into my pineapple, I see the management AP and open ssid is set to 'Hidden' but still appears on wireless network list. I un/re-check both boxes in attempting to save the 'hidden' state, no change. I immediately went to Filters and saw it was on 'Allow' Mode. I changed it to 'Deny' and found both my management AP and open ssid are now hidden. HOWEVER, when i try connecting to my management AP on my mobile, it tells me it can't be found ? I change the filer back to allow and my mobile is "allowed" to connect while publicly displaying both AP's. I'm pretty sure this is a bug between hiding the management / open ssid AP and filters. I can't seem to find a fix/work-around yet, I have not re-flashed the upgrade yet but I have a feeling it won't matter. Think I'll downgrade back to 2.0.2, which worked good so far for me except for the time zone not sticking issue. Link to comment Share on other sites More sharing options...
Couchfault Posted June 23, 2018 Share Posted June 23, 2018 1 hour ago, _0NiTy said: Not sure if someone has posted already about this issue ( haven't looked yet; in Q&A) but there's a problem with the management AP and open ssid being "filtered" for the owner. After flashing to the update '2.1.2', I've set the management AP and open ssid name during setup (while having wireless disabled) and saved my progress. When I logged into my pineapple, I see the management AP and open ssid is set to 'Hidden' but still appears on wireless network list. I un/re-check both boxes in attempting to save the 'hidden' state, no change. I immediately went to Filters and saw it was on 'Allow' Mode. I changed it to 'Deny' and found both my management AP and open ssid are now hidden. HOWEVER, when i try connecting to my management AP on my mobile, it tells me it can't be found ? I change the filer back to allow and my mobile is "allowed" to connect while publicly displaying both AP's. I'm pretty sure this is a bug between hiding the management / open ssid AP and filters. I can't seem to find a fix/work-around yet, I have not re-flashed the upgrade yet but I have a feeling it won't matter. Think I'll downgrade back to 2.0.2, which worked good so far for me except for the time zone not sticking issue. Hi @_0NiTy, I'm sorry you're experiencing issues with the WiFi Pineapple. Which device are you using? The NANO or the TETRA? Could you also generate a debug file using the help module after reproducing the issue and email it to henry [at] hak5.org? Best Regards, Henry Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.