

I am still having a gaming rig here with rx6900xt as well but way too big to get it wife approved into the living room and have no man cave to run it 24/7.
It’s pretty trivial to make use of an LLM compute box remotely; in fact, most of the software out there is designed around doing this, since lots of people use cloud-based LLM compute machines. I use the Framework Desktop in this fashion — I leave it headless, just as an LLM compute node for whatever machine is running software that needs number-crunching done. So if your gaming machine is fine for you in terms of compute capability, you might want to just use it remotely from the living room with another machine being in the living room.
Another benefit of sticking the compute box elsewhere is that while my Framework Desktop is very quiet (single large fan, about 120W TDP, and is notable for being rather quieter than other AI Max-based systems), keeping my 7900 XTX loaded will spin up the fans. You may not want to have a heavy-duty number-crunching machine in the living room from a noise standpoint.



Okay, gotcha. In that case, my guess is that the most-likely issue is with the DNS daemon that OpenWRT is using, which is most-likely dnsmasq.
You could confirm that your DNS configuration on the LAN hosts is actually using OpenWRT as the DNS server if you wanted — I could walk through that, if you’re not sure. But from a test-when-it’s-happening situation, I’d probably:
Install
digon the Mint box, if it’s not already installed. That’s a DNS diagnostic program that doesn’t use your system resolving mechanism, talks directly to DNS, so it cuts out any other factors. It’ll be in the bind9-dnsutils package.Install
digon the OpenWRT box.Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems (your router’s LAN address probably being something like 192.168.1.1):
Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems using whatever outside DNS server you have the OpenWrt box set to use (assuming 1.1.1.1 here):
Next time you have problems, repeat the above. If both the
digon your OpenWrt box and on your laptop using the OpenWrt DNS server now fail, then it’s probably pretty safe to say that it’s the DNS server on the OpenWrt box at fault. If just the one on your laptop fails, then it’s going to be a communication issue between your LAN box and the OpenWrt DNS server.Assuming that the problem is the OpenWrt DNS server, and assuming that it’s dnsmasq, to troubleshoot further, I might try looking at its logs, or installing
tcpdumpon the OpenWrt box and running that, something like$ tcpdump -nvvv -i any udp port domain. That should let you see both the incoming DNS queries going to the OpenWrt DNS server as well as the queries that it is sending upstream (the-nwill preventtcpdumpfrom itself sending DNS queries to look up IP addresses, which would generate more noise, the-vvvto show all possible information about the packets, and the-i anyto show all packets on all interfaces). That’ll let you see whether it’s getting flooded with DNS queries and to see what queries it’s sending to the upstream DNS server out on the Internet.That won’t alone solve your problem, but it’d be the next step I’d try to narrow down what’s going on.