Wireless AP - slow LuCI GUI

Hi,

I'm new to OpenWRT and have recently flashed my D-Link DAP-2695 Wireless AP to the current release on the https://openwrt.org/toh/d-link/dap-2695 page....
openwrt-18.06.2-ar71xx-generic-dap-2695-a1-squashfs-factory.img

but have a few issues with it, if someone could help me with.

The biggest issue is the LUCI web GUI is very sluggish, sometimes waiting up to a minute to respond moving through settings pages, tried 3 different browsers and all the same.

The wireless 5ghz 'LED' no longer works and looking in the GUI LED control settings page, no reference in the 5ghz, only power and 2.4ghz led's .

Can someone also explain if I can update from the default branch factory FW above and what is the snapshot version for this AP?

Any help appreciated, thanks.

background XHR child processes have been known to grind luci down.... be sure the processes are totally ended on your client.

try installing luci-app-uhttpd and checking the concurrent connection limit ( option max_requests '1' ) > 3-5 ( on the Advanced Tab - far right )

Thanks Guy's, I look into those!

I haven't tried anything at the moment, still on factory image.

Just found this regarding updating LuCI packages but doesn't work, need some guidance...

This feed is enabled by default. Your feeds.conf.default (or feeds.conf) should contain a line like:
src-git luci https://github.com/openwrt/luci.git

To install all its package definitions, run:
./scripts/feeds update luci
./scripts/feeds install -a -p luci

Thanks.

Can you get to LUCI > System > Software?

If it hangs, hit ( no click :wink: ) stop and change the URL to just the IP the ENTER ( a couple of times )

Yes I can and I've pulled the latest packages but there are 100's of them, which ones do I need to install?

Thanks.

luci-app-uhttpd

This is likely just the way it is.... ( not a router fault )... It's not a common device? so there is a small<<<-medium chance a newer build has it fixed. ( nb: ath71 )

As with the above question if the ToH says supported and you read the installation notes...... ( checked: its not listed there ... notes are scarce too.... reversion to stock looks simple if it ever comes to that )... you need to use a sysupgrade .bin for updation.... ( not factory like on first install )

http://downloads.openwrt.org/snapshots/targets/ar71xx/generic/openwrt-ar71xx-generic-dap-2695-a1-squashfs-sysupgrade.bin

Bear in mind that these images are generally not tested and have no GUI by default, use them at your own risk.

Given your starting out.... there is limited documentation and benefit? i don't think its worthwhile.... just yet.... LUCI is fixable.... and we'll wait to see if someone else who has the device can report back on the LEDs....

Shall I also try the snapshot image for my model AP?

snapshot lacks the luci web ui, you would need to install it from ssh remote terminal.

I can save you the hassle by checking the source code in OpenWrt project repository.

By looking at the source files for OpenWrt snapshot https://github.com/openwrt/openwrt/blob/master/target/linux/ar71xx/files/arch/mips/ath79/mach-dap-2695-a1.c
it seems the 5Ghz led was not defined.

Also by looking at the commit (the code contribution that added support for your device) https://github.com/openwrt/openwrt/commit/e3875350f3e4185020b64e0588bba521cd1d6e64
there is no description at all on why they didn't add the 5GHz led.
Thankfully they added rules later to make sure people won't just merge commits with no description like that anymore, but older ones remain.

Also, still by looking at the source, I don't see any mention of your device being ported to the newer ath79 target either.

From what I know for other devices, 5Ghz leds may have been controlled directly by the wifi chip and only the stock firmware's driver can make them work.
OpenWrt uses the opensource driver which isn't the same.

You can try sending an email to the person that contributed the code for this device, he is a known and active contributor, he should be able to answer.

he should also exist in this forum, let's see if I can summon him here. @stintel

Thank you @bobafetthotmail and @anon50098793 (for your added info/edit)

Whilst I researched the 5ghz led issue I did come across old references which coincide exactly what you have described...
'From what I know for other devices, 5Ghz leds may have been controlled directly by the wifi chip and only the stock firmware's driver can make them work.
OpenWrt uses the opensource driver which isn't the same.'

I have updated to the snapshot trying to get the latest build/packages for my AP, however I am now stuck trying to install luCI, putty output response is failed signatures for luCi package and some others, so they are instantly removed.

Need guidance on best approach to get the most update files on my AP or if the snapshot is the latest - help with getting around the failed signatures issue for most of the update packages inc luCI.

Had a look to try manual download/install but so many files in the repository it's near impossible to locate the correct packages, don't want to end up with a mess or brick :confused:

Thanks.

Putty output - opkg update

root@OpenWrt:~# opkg update Downloading http://downloads.openwrt.org/snapshots/targets/ar71xx/generic/packag es/Packages.gz Updated list of available packages in /var/opkg-lists/openwrt_core Downloading http://downloads.openwrt.org/snapshots/targets/ar71xx/generic/packag es/Packages.sig Signature check passed. Downloading http://downloads.openwrt.org/snapshots/targets/ar71xx/generic/kmods/ 4.14.125-1-4798db7ce04dcb4337e44dbaa2a958a0/Packages.gz Updated list of available packages in /var/opkg-lists/openwrt_kmods Downloading http://downloads.openwrt.org/snapshots/targets/ar71xx/generic/kmods/ 4.14.125-1-4798db7ce04dcb4337e44dbaa2a958a0/Packages.sig Signature check passed. Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/base/Packa ges.gz Updated list of available packages in /var/opkg-lists/openwrt_base Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/base/Packa ges.sig Signature check failed. Remove wrong Signature file. Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/luci/Packa ges.gz Updated list of available packages in /var/opkg-lists/openwrt_luci Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/luci/Packa ges.sig Signature check failed. Remove wrong Signature file. Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/P ackages.gz Updated list of available packages in /var/opkg-lists/openwrt_packages Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/P ackages.sig Signature check failed. Remove wrong Signature file. Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/routing/Pa ckages.gz Updated list of available packages in /var/opkg-lists/openwrt_routing Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/routing/Pa ckages.sig Signature check failed. Remove wrong Signature file. Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/telephony/ Packages.gz Updated list of available packages in /var/opkg-lists/openwrt_telephony Downloading http://downloads.openwrt.org/snapshots/packages/mips_24kc/telephony/ Packages.sig Signature check failed. Remove wrong Signature file. root@OpenWrt:~#

That's kind of weird that it fails when checking only some package list signatures.

Try to reset the OpenWrt firmware to defaults, when you upgrade to snapshot you should NOT preserve configuration. The instructions here to reset OpenWrt configuration. https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset#factory_reset

Anyway, snapshot builds (and all their packages) are recompiled daily, if anything fails during updates it usually means that the image you installed is too old and is unable to find its packages anymore.

Try to download the snapshot image, and install again.

If it still fails please post here the packages you want to install over a default OpenWrt image (which is basically what you have in the snapshot image + Luci) and I'll build an image with the Image Builder with those packages integrated already. https://openwrt.org/docs/guide-user/additional-software/imagebuilder
Or if you have a Linux system handy, you can do it yourself too.

1 Like

I'm sure I unchecked the 'keep configuration' box when I flashed the snapshot, i'll try again as soon as I can.

I have currently reverted back to the release image.bin via putty commands (1st uploaded image.bin to /tmp/) in the interim to have a working system at the moment.

Can you confirm that I need to flash the .bin sysupgrade snapshot image or the factory snapshot .img and if the .bin is sufficient - ok to flash via release LuCI gui upgrade?

Thanks for your help with this, appreciated.

Be back soon!

once you have a working OpenWrt system you only need to use the sysupgrade images.

The "factory" images are used only when you are installing Openwrt from stock device firmware.

Doing the upgrade from Luci or from putty is the same as long as you do not save configuration if you are updating from release to snapshot or back.

@bobafetthotmail

Ok, success this time, all signatures ok/updated and I then installed LuCI but now when I access the IP/login of the AP via internet explorer - I get the LuCI login page but then logging in, IE just says waiting for (AP IP address) trying to login and then I get 'Bad Gateway' The process did not produce any response :confused:

Tried rebooting, defaulting settings, reinstall and installed the recommended 'SQM-QoS package' as directed on the install snapshot guide web page but still the same, IE tries to login but then bad gateway every time.

Any idea's?

Thanks.

Chances are you have "redirect https" set to on and no https running.

opkg list-installed | grep https
uci show uhttpd | grep https

Thanks...

opkg list-installed | grep https - ok

uci show uhttpd | grep https - uci: entry not found

whoops;

uci show | grep http

will do...

1 Like

No Probs, Will retry again tomorrow evening and report back, Thanks!

@anon50098793

'uci show | grep http' went ok (Putty output below) but still cannot login, ages waiting to login then bad gateway again :confused:

Putty Output

root@OpenWrt:~# uci show | grep http
ucitrack.@httpd[0]=httpd
ucitrack.@httpd[0].init='httpd'
uhttpd.main=uhttpd
uhttpd.main.listen_http='0.0.0.0:80' '[::]:80'
uhttpd.main.listen_https='0.0.0.0:443' '[::]:443'
uhttpd.main.redirect_https='1'
uhttpd.main.home='/www'
uhttpd.main.rfc1918_filter='1'
uhttpd.main.max_requests='3'
uhttpd.main.max_connections='100'
uhttpd.main.cert='/etc/uhttpd.crt'
uhttpd.main.key='/etc/uhttpd.key'
uhttpd.main.cgi_prefix='/cgi-bin'
uhttpd.main.lua_prefix='/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'
uhttpd.main.script_timeout='60'
uhttpd.main.network_timeout='30'
uhttpd.main.http_keepalive='20'
uhttpd.main.tcp_keepalive='1'
uhttpd.defaults=cert
uhttpd.defaults.days='730'
uhttpd.defaults.bits='2048'
uhttpd.defaults.country='ZZ'
uhttpd.defaults.state='Somewhere'
uhttpd.defaults.location='Unknown'
uhttpd.defaults.commonname='OpenWrt'
root@OpenWrt:~#

You did not show us the result of;

opkg list-installed | grep https
or
opkg list-installed | grep ssl

Also do a;

netstat -lnp

See here:

Output below, thanks.

login as: root


BusyBox v1.31.0 () built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt SNAPSHOT, r10250-016d1eb
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt:~# opkg list-installed | grep https
root@OpenWrt:~# opkg list-installed | grep ssl
root@OpenWrt:~# netstat -lnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 192.168.137.242:53      0.0.0.0:*               LISTEN      1025/dnsmasq
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1025/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1058/dropbear
tcp        0      0 fe80::9ed6:43ff:fe28:d7e1:53 :::*                    LISTEN      1025/dnsmasq
tcp        0      0 fe80::9ed6:43ff:fe28:d7e1:53 :::*                    LISTEN      1025/dnsmasq
tcp        0      0 fe80::9ed6:43ff:fe28:d7e2:53 :::*                    LISTEN      1025/dnsmasq
tcp        0      0 fe80::9ed6:43ff:fe28:d7e2:53 :::*                    LISTEN      1025/dnsmasq
tcp        0      0 ::1:53                  :::*                    LISTEN      1025/dnsmasq
tcp        0      0 :::22                   :::*                    LISTEN      1058/dropbear
udp        0      0 192.168.137.242:53      0.0.0.0:*                           1025/dnsmasq
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1025/dnsmasq
udp        0      0 :::546                  :::*                                1343/odhcp6c
udp        0      0 :::547                  :::*                                1154/odhcpd
udp        0      0 fe80::9ed6:43ff:fe28:d7e1:53 :::*                                1025/dnsmasq
udp        0      0 fe80::9ed6:43ff:fe28:d7e1:53 :::*                                1025/dnsmasq
udp        0      0 fe80::9ed6:43ff:fe28:d7e2:53 :::*                                1025/dnsmasq
udp        0      0 fe80::9ed6:43ff:fe28:d7e2:53 :::*                                1025/dnsmasq
udp        0      0 ::1:53                  :::*                                1025/dnsmasq
raw        0      0 ::%2139380676:58        ::%4380989:*            58          1154/odhcpd
raw        0      0 ::%2139380676:58        ::%4380989:*            58          1343/odhcp6c
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node PID/Program name    Path
unix  2      [ ACC ]     STREAM     LISTENING        343 532/ubusd           /var/run/ubus.sock
root@OpenWrt:~#