You did this complication yourself. Remote router running beta firmware with potentially disruptive blocking script relying on community block lists and perhaps running on USB stick not designed for this type of use and known to fail over time... why? So many failure points for no reason. Your parents perhaps have a few active devices at a time and need something maintenance free. And what is there to QoS so much, hardcore gamers?
They live 15 mins away not hard for me to fix if something fails, but remote management over vpn is more convenient for me in some cases. QoS to stabilize their cable internet connection, and prioritize their voip over everything else when the voip over lan port 1. Currently QoS isn’t enabled since the setups works like this atm.
Currently:
Cable modem (dhcp) -> wan of isp voip box (dhcp, but can’t access this device) -> wan of router (dhcp). So it’s like nat central.
Future:
Cable modem (dhcp) -> wan of router (dhcp) -> wan of isp voip modem. But this causes issues without good QoS for the phone.
They only have 17 down 2 up.
I don’t want to use the dhcp server of anything supplied by my isp (except wan) so double nat is inevitable unless I want to start screwing around with my fathers isp’s devices.
Adblocking and community blocklist are just a nice to have, I use it at home even with a USB stick which yes they are known to fail, but never have I had a usb actually die before the router. Most cases any corrupted usb stick happens from not unmounting the stick before doing a firmware update. USB sticks are cheap, since they don’t use the NAS functionality it will limit the writes to the stick. Obviously not as ideal as an external usb ssd in terms of speed. But I’m not convinced it’s something that is necessary they use a ssd or harddrive.
I’m not really a maintenance free kinda guy for my devices, and it’s not a random client I’m servicing otherwise yeah maintenance free is best as most people plug it in and forget about their router.
Well it’s fine for now honestly I can wait for updates from gnuton, nothing serious is wrong with the router just addons clearly are not happy in beta 1 of 388.7_1.
Will likely downgrade on Friday, and verify if the issue exists in 388.6_1.