What do you mean by:
i can connect to it, but it's non responsive. apps on my phone say cannot connect to network, and i can't surf.
Even though "free" or "top" would be more revealing, nothing in your logs suggests memory exhaustion. Looking at the kernel messages (dmesg/ logread) during the error case might provide deeper insight into your problems.
I noticed you are using a target with mediatek wireless radios. Do you by any change use Apple devices?
Personaly I think you're looking in the wrong direction. I don't think that RAM/CPU usage will affect WiFi this much. I think you're experiencing a driver issue. When WiFI is "dead" can you also post a syslog?
Ps. You can remove stuff like LuCI dropbear. But not both 
. Unless you want to manage your device through a serial ttl connection.
@slh the second log is "top", next time i'll check the kernel messages, but i think i set it to show only warning and above.
[ 0.000000] Linux version 4.4.92 (buildbot@debian8) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3560-79f57e422d) ) #0 Tue Oct 17 17:46:20 2017
[ 0.000000] SoC Type: Ralink RT3883 ver:1 eco:5
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[ 0.000000] MIPS: machine is D-Link DIR-645
[ 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 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] On node 0 totalpages: 16384
[ 0.000000] free_area_init_node: node 0, pgdat 803604b0, 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: console=ttyS0,57600 rootfstype=squashfs,jffs2
[ 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: 60896K/65536K available (3026K kernel code, 138K rwdata, 396K rodata, 208K init, 200K bss, 4640K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:256
[ 0.000000] CPU Clock: 500MHz
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041786 ns
[ 0.000011] sched_clock: 32 bits at 250MHz, resolution 4ns, wraps every 8589934590ns
[ 0.015467] Calibrating delay loop... 249.44 BogoMIPS (lpj=1247232)
[ 0.090647] pid_max: default: 32768 minimum: 301
[ 0.099948] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.112987] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.133180] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.152666] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.164821] pinctrl core: initialized pinctrl subsystem
[ 0.176533] NET: Registered protocol family 16
[ 0.190662] Can't analyze schedule() prologue at 8000acdc
[ 0.216090] rt2880_gpio 10000600.gpio: registering 24 gpios
[ 0.227123] rt2880_gpio 10000600.gpio: registering 24 irq handlers
[ 0.239574] rt2880_gpio 10000638.gpio: registering 16 gpios
[ 0.252049] clocksource: Switched to clocksource MIPS
[ 0.263347] NET: Registered protocol family 2
[ 0.273019] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.286804] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.299396] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.312149] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.323655] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.336401] NET: Registered protocol family 1
[ 0.344989] PCI: CLS 0 bytes, default 32
[ 0.349578] rt-timer 10000100.timer: maximum frequency is 5065Hz
[ 0.362421] Crashlog allocated RAM at address 0x3f00000
[ 0.390772] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.402289] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.424723] io scheduler noop registered
[ 0.432427] io scheduler deadline registered (default)
[ 0.442862] ralink-usb-phy usbphy: invalid resource
[ 0.453048] gpio-export gpio_export: 1 gpio(s) exported
[ 0.463566] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.479871] console [ttyS0] disabled
[ 0.486923] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a Palmchip BK-3103
[ 0.506602] console [ttyS0] enabled
[ 0.520415] bootconsole [early0] disabled
[ 0.543442] spi spi0.0: force spi mode3
[ 0.551608] m25p80 spi0.0: mx25l6405d (8192 Kbytes)
[ 0.561441] 6 ofpart partitions found on MTD device spi0.0
[ 0.572385] Creating 6 MTD partitions on "spi0.0":
[ 0.581940] 0x000000000000-0x000000030000 : "uboot"
[ 0.593660] 0x000000030000-0x000000034000 : "uboot-env"
[ 0.606146] 0x000000034000-0x000000038000 : "factory"
[ 0.618258] 0x000000038000-0x000000040000 : "nvram"
[ 0.630014] 0x000000040000-0x000000050000 : "devdata"
[ 0.642182] 0x000000050000-0x000000800000 : "firmware"
[ 1.098421] 2 seama-fw partitions found on MTD device firmware
[ 1.110096] 0x000000050040-0x00000017a000 : "kernel"
[ 1.121660] 0x00000017a000-0x000000800000 : "rootfs"
[ 1.133653] mtd: device 7 (rootfs) set to be root filesystem
[ 1.145087] 1 squashfs-split partitions found on MTD device rootfs
[ 1.157444] 0x00000039c000-0x000000800000 : "rootfs_data"
[ 1.170846] rtl8367b rtl8367b: using GPIO pins 1 (SDA) and 2 (SCK)
[ 1.184387] rtl8367b rtl8367b: RTL8367RB chip found
[ 2.968559] libphy: rtl8367b: probed
[ 2.976873] mtk_soc_eth 10100000.ethernet: using fixed link parameters
[ 2.989950] mtk_soc_eth 10100000.ethernet eth0 (uninitialized): link up (1000Mbps/Full duplex)
[ 3.007960] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
[ 3.025077] rt2880_wdt 10000120.watchdog: Initialized
[ 3.036701] NET: Registered protocol family 10
[ 3.049333] NET: Registered protocol family 17
[ 3.058345] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 3.083499] 8021q: 802.1Q VLAN Support v1.8
[ 3.101030] VFS: Mounted root (squashfs filesystem) readonly on device 31:7.
[ 3.116640] Freeing unused kernel memory: 208K
[ 4.535076] init: Console is alive
[ 4.542159] init: - watchdog -
[ 5.616104] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 5.732662] usbcore: registered new interface driver usbfs
[ 5.743765] usbcore: registered new interface driver hub
[ 5.754507] usbcore: registered new device driver usb
[ 5.771138] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.785990] ehci-platform: EHCI generic platform driver
[ 5.806778] phy phy-usbphy.0: remote usb device wakeup disabled
[ 5.818594] phy phy-usbphy.0: UTMI 16bit 30MHz
[ 5.827496] ehci-platform 101c0000.ehci: EHCI Host Controller
[ 5.838999] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
[ 5.854932] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[ 5.882073] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[ 5.895766] hub 1-0:1.0: USB hub found
[ 5.903713] hub 1-0:1.0: 2 ports detected
[ 5.915223] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.929208] ohci-platform: OHCI generic platform driver
[ 5.939969] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[ 5.953573] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[ 5.969494] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[ 6.037190] hub 2-0:1.0: USB hub found
[ 6.045156] hub 2-0:1.0: 2 ports detected
[ 6.056679] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 6.081620] init: - preinit -
[ 6.668683] mtk_soc_eth 10100000.ethernet eth0: link up (1000Mbps/Full duplex)
[ 6.683961] 8021q: adding VLAN 0 to HW filter on device eth0
[ 6.719313] random: procd: uninitialized urandom read (4 bytes read, 10 bits of entropy available)
[ 10.214401] jffs2: notice: (359) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 10.251110] mount_root: switching to jffs2 overlay
[ 10.274113] urandom-seed: Seeding with /etc/urandom.seed
[ 10.510724] mtk_soc_eth 10100000.ethernet eth0: link down
[ 10.536401] procd: - early -
[ 10.542780] procd: - watchdog -
[ 11.228101] procd: - watchdog -
[ 11.234758] procd: - ubus -
[ 11.354154] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.443007] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.461871] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.479882] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.498258] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.516242] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.534842] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.553045] random: ubusd: uninitialized urandom read (4 bytes read, 18 bits of entropy available)
[ 11.571420] procd: - init -
[ 12.165103] kmodloader: loading kernel modules from /etc/modules.d/*
[ 12.209933] zram: Added device: zram0
[ 12.226199] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[ 12.242225] Backport generated by backports.git backports-20160324-13-g24da7d3c
[ 12.267078] nf_conntrack version 0.5.0 (954 buckets, 3816 max)
[ 12.333866] xt_time: kernel timezone is -0000
[ 12.371454] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 12.435517] PPP generic driver version 2.4.2
[ 12.447799] NET: Registered protocol family 24
[ 12.492413] rt2800_wmac 10180000.wmac: loaded eeprom from mtd device "factory"
[ 12.506852] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3883, rev 0400 detected
[ 12.522314] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3853 detected
[ 12.536790] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 12.732892] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 13.831038] random: jshn: uninitialized urandom read (4 bytes read, 22 bits of entropy available)
[ 22.851594] mtk_soc_eth 10100000.ethernet eth0: link up (1000Mbps/Full duplex)
[ 22.852230] 8021q: adding VLAN 0 to HW filter on device eth0
[ 22.867196] device eth0.1 entered promiscuous mode
[ 22.867225] device eth0 entered promiscuous mode
[ 22.869166] br-lan: port 1(eth0.1) entered listening state
[ 22.869225] br-lan: port 1(eth0.1) entered listening state
[ 22.869327] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 24.619815] pppoe-wan: renamed from ppp0
[ 24.862118] br-lan: port 1(eth0.1) entered learning state
[ 26.862102] br-lan: topology change detected, propagating
[ 26.862161] br-lan: port 1(eth0.1) entered forwarding state
[ 26.894944] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 26.895304] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 26.916457] device wlan0 entered promiscuous mode
[ 34.382173] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 34.382402] br-lan: port 2(wlan0) entered listening state
[ 34.382461] br-lan: port 2(wlan0) entered listening state
[ 36.382077] br-lan: port 2(wlan0) entered learning state
[ 38.382055] br-lan: topology change detected, propagating
[ 38.382094] br-lan: port 2(wlan0) entered forwarding state
[ 47.375002] random: nonblocking pool is initialized
[ 3240.935771] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[ 3240.954241] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[ 3240.972683] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
@Timeless no, i don't have an Apple product, i do have a Chinese phone. ZTE , it has mediatek processor, so i guess the rest is also mediatek.
is there something i need to install for it to run properly? because i have 3 phones like that connecting to the wifi.
as for the syslog,
Fri Nov 3 10:26:47 2017 daemon.info dnsmasq[1059]: read /etc/hosts - 4 addresses
Fri Nov 3 10:26:47 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/odhcpd - 2 addresses
Fri Nov 3 10:26:47 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/dhcp.cfg02411c - 7 addresses
Fri Nov 3 10:26:47 2017 daemon.info dnsmasq-dhcp[1059]: read /etc/ethers - 0 addresses
Fri Nov 3 10:26:50 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:26:54 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:34:30 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:40:16 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:44:12 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:50:35 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 10:54:09 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:00:20 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:10:04 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:19:10 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:24:23 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:33:33 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:43:20 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:46:52 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:55:11 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 11:59:17 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:02:44 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:08:23 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:12:32 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:22:26 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:29:12 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:39:03 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:43:56 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:44:01 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: authenticated
Fri Nov 3 12:44:01 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: associated (aid 1)
Fri Nov 3 12:44:01 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 12:44:01 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a
Fri Nov 3 12:44:01 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a android-3bfd6e97c7abdf1d
Fri Nov 3 12:44:02 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:44:06 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:44:10 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:44:19 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 12:49:04 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 12:56:44 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:04:30 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:09:46 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:22 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: authenticated
Fri Nov 3 13:15:22 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: associated (aid 1)
Fri Nov 3 13:15:22 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:15:23 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b
Fri Nov 3 13:15:23 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b Rotem-Android
Fri Nov 3 13:15:23 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:27 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:31 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:40 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: authenticated
Fri Nov 3 13:15:40 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: associated (aid 2)
Fri Nov 3 13:15:40 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:15:40 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a
Fri Nov 3 13:15:40 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a android-3bfd6e97c7abdf1d
Fri Nov 3 13:15:41 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:45 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:15:48 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:15:49 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:16:18 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:18:35 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:19:05 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: authenticated
Fri Nov 3 13:19:05 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: associated (aid 1)
Fri Nov 3 13:19:05 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:19:05 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b
Fri Nov 3 13:19:05 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b Rotem-Android
Fri Nov 3 13:19:06 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:19:10 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:19:12 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:25:32 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:31:48 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:32:52 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: authenticated
Fri Nov 3 13:32:52 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: associated (aid 1)
Fri Nov 3 13:32:52 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:32:52 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b
Fri Nov 3 13:32:52 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b Rotem-Android
Fri Nov 3 13:32:53 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:32:57 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:33:01 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:33:15 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:33:33 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: authenticated
Fri Nov 3 13:33:33 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: associated (aid 1)
Fri Nov 3 13:33:33 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:33:33 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a
Fri Nov 3 13:33:33 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a android-3bfd6e97c7abdf1d
Fri Nov 3 13:33:34 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:33:38 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:33:42 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:35:02 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: authenticated
Fri Nov 3 13:35:02 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: associated (aid 2)
Fri Nov 3 13:35:02 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:35:03 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b
Fri Nov 3 13:35:03 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b Rotem-Android
Fri Nov 3 13:35:04 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:35:08 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:35:12 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:35:25 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 13:38:09 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:38:55 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:46:03 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:48:24 2017 daemon.notice hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: did not acknowledge authentication response
Fri Nov 3 13:48:26 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: authenticated
Fri Nov 3 13:48:26 2017 daemon.info hostapd: wlan0: STA 4c:16:f1:a3:d0:0a IEEE 802.11: associated (aid 1)
Fri Nov 3 13:48:26 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:48:26 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a
Fri Nov 3 13:48:26 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.235 4c:16:f1:a3:d0:0a android-3bfd6e97c7abdf1d
Fri Nov 3 13:48:31 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:48:35 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:49:35 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:50:36 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 4c:16:f1:a3:d0:0a
Fri Nov 3 13:53:06 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 13:56:48 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:06:07 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:13 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: authenticated
Fri Nov 3 14:08:13 2017 daemon.info hostapd: wlan0: STA d0:5b:a8:75:eb:3b IEEE 802.11: associated (aid 1)
Fri Nov 3 14:08:13 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 14:08:14 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b
Fri Nov 3 14:08:14 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.102 d0:5b:a8:75:eb:3b Rotem-Android
Fri Nov 3 14:08:14 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:18 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:22 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq-dhcp[1059]: DHCPREQUEST(br-lan) 192.168.55.231 90:2b:34:18:cd:91
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq-dhcp[1059]: DHCPACK(br-lan) 192.168.55.231 90:2b:34:18:cd:91 FortScepter
Fri Nov 3 14:08:32 2017 daemon.notice odhcpd[702]: Got DHCPv6 request
Fri Nov 3 14:08:32 2017 daemon.warn odhcpd[702]: DHCPV6 SOLICIT IA_NA from 000100011dbc00c8902b3418cd91 on br-lan: ok fd23:eb6e:b022::203/128
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq[1059]: read /etc/hosts - 4 addresses
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/odhcpd - 1 addresses
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/dhcp.cfg02411c - 7 addresses
Fri Nov 3 14:08:32 2017 daemon.info dnsmasq-dhcp[1059]: read /etc/ethers - 0 addresses
Fri Nov 3 14:08:33 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:33 2017 daemon.notice odhcpd[702]: Got DHCPv6 request
Fri Nov 3 14:08:33 2017 daemon.warn odhcpd[702]: DHCPV6 SOLICIT IA_NA from 000100011dbc00c8902b3418cd91 on br-lan: ok fd23:eb6e:b022::203/128
Fri Nov 3 14:08:34 2017 daemon.notice odhcpd[702]: Got DHCPv6 request
Fri Nov 3 14:08:34 2017 daemon.warn odhcpd[702]: DHCPV6 REQUEST IA_NA from 000100011dbc00c8902b3418cd91 on br-lan: ok fd23:eb6e:b022::203/128
Fri Nov 3 14:08:34 2017 daemon.info dnsmasq[1059]: read /etc/hosts - 4 addresses
Fri Nov 3 14:08:34 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/odhcpd - 2 addresses
Fri Nov 3 14:08:34 2017 daemon.info dnsmasq[1059]: read /tmp/hosts/dhcp.cfg02411c - 7 addresses
Fri Nov 3 14:08:34 2017 daemon.info dnsmasq-dhcp[1059]: read /etc/ethers - 0 addresses
Fri Nov 3 14:08:37 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:08:40 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED d0:5b:a8:75:eb:3b
Fri Nov 3 14:08:41 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:13:04 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
Fri Nov 3 14:16:46 2017 daemon.info odhcpd[702]: Using a RA lifetime of 0 seconds on br-lan
also, i was wondering what dropbear was, so i read a bit on wikipedia, but wasn't sure i could remove it. so you're saying if i use Luci i can remove it?
thanks for all the help guy, i really appreciate it!
That's a long standing issue with rt2x00 drivers, which has nothing to do with memory exhaustion, but rather is a bug somewhere between the RaLink wireless hardware, its firmware and the rt2x00 driver - chances for this to be fixed aren't that great (the rt2x00 developer team has mostly dissolved, the affected devices are out of production for a while and Mediatek's current designs use a different, unaffected, driver). Testing snapshots rather than 17.01.x has a tiny chance of improvements, but I wouldn't expect too much.
1 Like
Yeah dropbear is LEDE's tiny SSH server. So without it you cannot use SSH anymore. But since you can basically do everything from within LuCI SSH can be turned off. Please note that you don't have to remove Dropbear, it's even better to let it be because removing something on a squashfs filesystem takes even more storage. Better just disable the server LuCI --> System --> Startup --> Press "enabled" for dropbear so it changes to "disabled". Then you can press "stop" or reboot your devices.
Also I found this bugtracker a while back: https://dev.openwrt.org/ticket/12313
I also have this same issue with my Arcadian VGV7519 and Sitecom WL-351 targets specifically with Apple devices. So that's why I asked. This is a known problem just like @slh mentions.
You could use this workaround (https://dev.openwrt.org/ticket/12313#comment:29):
root@OpenWrt:~# cat /mnt/usb/scripts/monitor.sh
logger "Starting the monitor script"
logread -f | while read LOGLINE
do
if [ "$LOGLINE" != "${LOGLINE/Dropping frame due to full tx queue/}" ]; then logger "Found \"$LOGLINE\". Rebooting..."; reboot; else echo "No errors found in \"$LOGLINE\"" >>/mnt/usb/monitor.log; fi
done
root@OpenWrt:~# cat /etc/rc.local
/bin/sh /mnt/usb/scripts/monitor.sh &
root@OpenWrt:~#
This will force a reboot every time this message pops up. It's not proven that when either this message appears that WiFI breaks, but at least I did not have any issue ever since. Ignoring the fact that my AP reboots so now and then ofc.
@Timeless you can't do everything in luci, for example updating modules, i've only managed to do via SSH.
as for the solution, i've search that line online, and other linux forums state that there's a way to flush the queue via command. maybe there's a way to do it here like in the script you posted.
also chrome does not let me go to the links you posted, it says cert removed.
Yeah thats also why I mentioned to not remove dropbear entirely but instead just enable it when needed.
Have not seen any method on how to empty the queue. Would be a nice workaround though. Because it will most likely create a shorter interrupt than a soft-reboot.
Don't know why Chrome complains about OpenWRT's certificate. I use Firefox myself and had no issue. The OpenWRT website is less maintained so maybe the certificate does not support the newer standards Chrome expects. You could try another browser instead.
https://ubuntuforums.org/showthread.php?t=2210322
that's the post i found. it's on Ubuntu, but i guess it's the same drivers? or very similar.
as for the SSH, would be nice to have a way to update packages from luci.
It doesn't make sense to disable dropbear, you don't win any security, you lose access to the shell - even less on a system with >= 64 MB RAM.
yeah i was not planning to, just it would be nice to not fire up putty just to update stuff with the opkg
Not that it was not about security. But ofcourse you win security. One less program to access a router. Adding a extra window to a house also creates a additional entrypoint even while it is closed.
But thats a little bit offtopic here. I just wanted to mention this if ram is really a tight fit.
Also being able to update packages is still pretty new so thats why it is not possible to update them through LuCI as for now.
That linked article is just about unloading/loading a kernel module. I'm not sure if this will help. And stuff about how to identify a wireless card. Ubuntu and LEDE are both linux yes, but the drivers can be patched different from upstream.
so if there's no solution in sight, i guess there's no other choice for me but to return to the stock firmware.
bummer, it was a really nice way to control my router, a shame the wifi doesn't work properly.
Also if this is a known problem, shouldn't the wiki page for this router warn that the wireless is unstable so who ever tries to install lede would know?
and does anyone know if this same issue with the chips happens on openwrt as well?
OpenWRT DIR-645...
https://wiki.openwrt.org/start?do=search&id=dir645
I would lean more towards a configuration issue.
What wireless security settings are you using? (WPA2-PSK, Force CCMP-AES)
If you are using auto for WiFi channel selection, I would hard select a channel (1, 6, or 11) for 2.4 GHZ and see if that makes a difference.
Also, if you are using 802.11n, WMM must be checked.
I would expect to see a warning on a LEDE device page if more than one person reported an issue, and it was confirmed by the LEDE team.
i currently use no security, but i hide ssid broadcasting.
Tried hard setting it, don't think it made a difference, and WMM is checked.
how would one contact the lede team in order to confirm the issue?
seems like openwrt faces the same issue with the wifi under high loads.
Hiding your SSID does nothing but prevent your neighbor from accidentally connecting to your WiFi network.
You are taking a risk running with no security.
Do a site search to find out how to report issues.
2 Likes
Again, i'm a ccna and network security expert and certified, i know what hiding my ssid means.
i'll check, but as i said, openwrt also faces this issue.
EDIT: i've checked, but there's no way to report a bug for a whole release, only for luci or packages, it's not luci, and i have no idea what package may cause the problem.
also there's no email to contact in such a case.