jow-:

Please open http://192.168.1.1/cgi-bin/luci/admin/network/wireless_assoclist in your browser and see if there's any error reported.

jow-:

Also hit F12 while on the overview page to open the debug console and look for errors.

brianjmurrell:

Yes, /cgi-bin/luci/admin/network/wireless_assoclist has 3 entries, just like /cgi-bin/luci/admin/network/wireless does.

There are no errors showing in the Console when I open the Developer Tools window.

jow-:

So does it show "Collecting data..." or "No information avaialble" or does it not render the table at all? Can you provide a screenshot?

Also which device exactly (to get an indication for CPU speed) and which browser?

brianjmurrell:

It shows "No information available". I can provide a screenshot if still desired.

Device is a "D-Link DIR-825 rev. B1".

jow-:

Please see if the error persists after clearing your browser cache - in some cases the xhr.js file is not getting refreshed, causing such issues.

Also take a look at the network tab in the debug console and see if requests to wireless_assoclist get cancelled without result after exactly 5s.

brianjmurrell:

I'm not really interested in the penalty of clearing my entire browser cache, but I can confirm the problem on a different machine that never views these pages, so effectively an empty cache.

The Network tab in the Devtools only shows fetches for '?status=1&_0.[numbers]' and the occasional 'signal-*.png'. There are no requests to 'wireless_assoclist'.

If I view the Network tab in the Devtools on the '/cgi-bin/luci/admin/network/wireless' page, I do see fetches for 'wireless_assoclist' just as confirmation that I understand what I am looking for.

So it seems the main overview page is simply not making the calls to 'wireless_assoclist'.

jow-:

Please attach the complete source code (ctrl-u) of the rendered page here.

brianjmurrell:

Attached

jow-:

That LuCI version is quite old, contains various known issues and is not the version shipped along with 18.06.0 final. Is this a custom build with stale feeds by any chance?

brianjmurrell:

It is a custom build, using the imagebuilder, yes. So I guess it's entirely possible that the feeds are stale, I suppose. What should one do to ensure one's feeds are always up-to-date when using the imagebuilder process?

brianjmurrell:

https://openwrt.org/docs/guide-user/additional-software/imagebuilder says nothing at all about feeds.

Can you just provide a pointer to some doc somewhere about how feeds and the ImageBuilder work together because indeed, the only references I can find about feeds is with the SDK, not the ImageBuilder.

jow-:

The Imagebuilder does not use feeds but fetches the packages from online repos or uses a local copy, depending on how it was built.

Anyhow, can you reproduce the problem with a recent snapshot or vanilla release image?

brianjmurrell:

I built a new image with my imagebuilder driver and it seems to be working now.

You can close this.