I've had a quick look into the DNS. It could possibly be the DNSCrypt and/or Dynamic DNS packages I have installed. I'll try disabling them, re-test and report back.
As a side note in relation to RAM, is there a way to monitor or log RAM usage?
Hey Guys I'm back and unfortunately with bad news...
I ended up re-installing LEDE Reboot 17.01.4, updated all my packages via SSH using PuTTY and installed the following packages:
luci-ssl
luci-app-upnp
luci-app-sqm
luci-app-ddns
ca-bundle
ddns-scripts
hostapd-common
hostapd-utils
wpad
qm-scripts
I then disabled the DDNS scripts package thinking this was the cause of the DNS request via the menu 'System > Startup' and clicked on the 'Enabled' button which turned into to 'Disabled'. Finally I rebooted my router and left if for a few minutes before then unplugging the WAN cable, sitting and waiting patiently for LuCI to start behaving slow and locking up after about 15 minutes or so. On the overview page I took some screenshots of the RAM usage available when it slowly drifted down to 9% compared to the 78% I have when everything is all up and working. As well slow loading webpages within LuCI I would also get an out of memory message in plain text. What's weird is when I could get to the 'Status > Processes' page and look under the RAM usage column there wasn't anything over 1%. I was expecting something to be hogging the RAM resources...
How are you updating the packages? It is not recommended to update core packages because it can introduce issues related to kernel versions and other dependencies.
My recommendation would be to re-flash with 17.01.4 and only setup the basics (do not update any existing packages, do not install any new ones). Test at this point.
Then, one at a time, install packages (again, do not update core packages; installing new packages is fine, though)... do it one at a time (aside from direct dependencies, of course) and test between each package installation. At some point, the problem will show up again and you should have a better idea of what might be causing the issue (base install, or a specific package, etc.). The best way to troubleshoot is to keep it simple and isolate variables.
When I updated the packages I did it through SSH using OPKG Packet Manager commands. If you recommend not updating the packages and only flashing the firmware and installing the fresh packages I do want, I'll give that a go and let you know.
Yes, please try what I recommended. Start simple. Does the problem manifest when you have a fresh install (with no extra packages installed, no upgrades). If so, you are either dealing with a bug or a configuration issue with the base firmware. Installing packages one-by-one after verifying that the base install is okay (assuming that is the case) will help narrow down the packages responsible for the issue.
Read this thread (and feel free to search for other threads related) for information about why it is not recommended to update the core packages. If you are really intent on updating those core packages, it would probably be best to build your own firmware from the source or to use a snapshot.
I've finally got round to troubleshooting my router.
I've factory reset the router so there is a fresh instance of LEDE 17.01.4.' So far all I've changed is gone to 'Network > Interfaces' and deleted WAN6 (as I don't really need this) and then under WAN changed the protocol to PPPoE, filled the username and password accordingly to my ISP and then set the MTU to 1492.
Unfortunately in the space of five and a half minutes the router is out of memory. What do I do now? I haven't installed any packages and it's already playing up with no Ethernet cable plugged into the WAN port.
This device has 512 MB RAM...I agree with @psherman. Can you provide the log entry (or picture of the top command) that shows that you're out of memory.
This is the stock LEDE firmware. I have not added any additional packages or made any other tweaks except change the protocol on the 'Network > Interfaces' page. I'm not using any swap space. The only program I had open was PuTTY. The issue is that all the LAN devices stop seeing each other, the Wi-Fi drops out so the router becomes useless with a WAN drop out. I'm definitely not using Swap space as I wouldn't know how to especially as I have not configured the router for USB.
LEDE/OpenWRT can be run in as little as 32MB of RAM (not recommended, see 4/32 warning), so 256MB should be totally sufficient.
I would start fresh with a fresh, official stable download of LEDE 17.01.4 for your device (here). Grab the sysupgrade.bin file (and ensure it is for your version of hardware -- acv1, acv2, or acs). Do not preserve system settings as you flash.
Then make the WAN6 and WAN/PPPoE changes that are necessary and see what happens.
I think I remember this device might have issues with a memory leak with the WiFi drivers. Could you please disable all WiFi interfaces completely (just click op stop on the WiFi interfaces overview page of Luci) and see whether the bug still occurs? We can continue from there
After setting up the password (as you do on clean installs) I went over 'Network > Wireless' and clicked remove on both radios despite being disabled by default. I then did my usual basic tweaks; delete WAN 6 on interfaces page, set PPPoE as protocol, put in username and password and set MTU to 1492. Same result. LuCI locked out with 'Internal Server Error
Failed to create CGI process: Out of memory' message and SSH refusing commands.
As far as I'm aware the development builds of OpenWRT don't have LuCI installed. With this in mind how do I allow internet access to the OpenWRT router so that I can download packages but keep it connected to my spare ISP provided that's providing a WAN and LAN connection so that I can connect to it via my PC on the LAN?
The WAN port (eth1) is defaulted to the DHCP client protocol. However, when I try to access the IP that my ISP router has given out I have no GUI. At the moment I have my ISP router connected from its LAN port to the LAN port on the OpenWRT router and I have a connection. However, going to 'System > Software' and clicking update lists can't establish a connection. It's though it's set to read from eth1 not eth0 (OpenWRT's LAN interface).