Good to see my MR7350 isn't the only device giving entries into its oops partition.
Over the last months I reseted this thing so often went to stock, tried new settings but strange wifi problems persisted.
Really thought about giving up on this.
Now I know I'm not the only one, TY also for private messages here.
I'm sorry for butchering the cat command in my post!
Joined: 18 Mar 2014 Posts: 13883 Location: Netherlands
Posted: Wed Oct 08, 2025 10:30 Post subject:
Zyxx wrote:
Good to see my MR7350 isn't the only device giving entries into its oops partition.
Over the last months I reseted this thing so often went to stock, tried new settings but strange wifi problems persisted.
Really thought about giving up on this.
Now I know I'm not the only one, TY also for private messages here.
I'm sorry for butchering the cat command in my post!
I do not want to discourage you but the MR7350 with IPQ6028 especially if you want to add NSS is difficult to support also because 512Mb RAM is on the low side for ATH11K.
@vatovey, on my x86 dd-wrt system WAN pppoe wont start wince 4 or 5 releases until I hit the connect button on Status --> Wan (despite it being configured to autoconnect).
Every like 20th reboot it works automatic though.
Maybe this is also the case for your problem?
@egc oh man. I was under the impression MR7350 and 7500 would be the future.
I retired the 7800 for faster wifi speeds with ax mode and in case of 7500 the fast WAN port.
*sad*
I really have high hopes for those two devices.
At least the RAM on 7350 isnt full, still somewhat like 150 MB free.
Joined: 16 Nov 2015 Posts: 7063 Location: UK, London, just across the river..
Posted: Thu Oct 09, 2025 7:08 Post subject:
Zyxx, my R7000 didn't have any problems with PPPoE, but yes in the past there was that trick working as you mention it...sadly Im away of it to test the last build and then again it doesn't see many updates and still on the old kernel 4.4xx _________________ Atheros
TP-Link WR1043NDv2 -DD-WRT 62606 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 -DD-WRT 63257 GTW/SmDNS/DoT,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT 62606 Gateway/DNSCryptv2,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla,VPN cli
Netgear R9000 --DD-WRT 62606 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Dynalink DL-WRX36-DDWRT 62606
Broadcom
Netgear R7000 --DD-WRT 63257 GTW/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN cli
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) client
I feel like we are closer at least for the 4300 series. VAPs on secondary node seem to have worked fine for the few days I have had this installed. Most everything else has been good, a couple of hiccups with the DDNS/wireguard serving but I am currently guessing that might be the provider for that and not the firmware itself.
VAPs on secondary router have been working fine, mesh seems to be a bit snappier, but that may just be its loading the gui faster, no analytical support for it except cloudflare speed reports having a reduced latency and jitter on the mesh points, but not enough to call it anything yet.
Only problem i have run into is NOW the main router seems to lose WAN connection ability after about a day..It still shows connected but devices have no internet connection until hard reboot. Soft reboot via gui will not fix it, but turning switch off and on does rectify.
Note that there was still some issues with the 9/20 and 9/26 versions with VAPs on secondary that have not appeared on this...yet anyway.
The WAN connection/loss of internet on primary and thus losing internet on all routers I dont think has been an issue on the 4300 recently though it was known a few months ago, but overall this seems to have the good stuff from 9/11 and back to 8/20 as far as the secondary routers are concerned and the one hiccup so far on the wan/internet blocking. Nothing exciting in the logs. We are approaching the timeframe today where if its gonna go out, should be in the next 12 hours so we shall see if it happens again, but great job overall and THanks so much for the hard work!
I might just again mention, routers reboot daily at around 6 am via the keep alive schedule reboot, which I currently have main router rebooting and then secondary/mesh in series...Is that the best way to do it? But the failure seems to happen at about a day and a half....so far at least...again thanks so much!
Seems like its around 2 days (approx 48 hours) that the wan ip connection goes out even though it still shows connected on the primary router. everything else seems to be working including the VAP on secondary routers and I even tried on mesh...but around 2 days with this version, as had happened a few months ago, the internet connection drops until a hard (via switch) reset. Soft gui reset does not bring the connection back up. But most of the other things seem to be fixed on the mx4300. Nothing in logs when it happens, at least regular logs. intranet streaming still works to mesh and such for locally served content, its just the interent connection on the main router goes out.
I have tried to make sure its not anything else, ie cable modem dropping or whatever and will verify more the next few days as it happens again. Is there a debug setting that might offer more insight? besides serial output, since I dont have the stuff to do that yet....
Router/Version: Linksys MX4300
File/Kernel: DD-WRT v3.0-r62240 std (10/04/25) / Linux 6.6.108-rt29 #4155 SMP Sat Oct 4 04:40:07 +07 2025 aarch64
Previous/Reset: DD-WRT v3.0-r61557 std (05/31/25)
Mode/Status: Gateway
Issues/Errors: I've noticed that the PPPoE connection for my DSL Internet has taken longer than previous versions to get an IP address during the connection process, upwards of 3-4 minutes. It also appears to cause loading the Router Status page to hang during the connection process. This area in general has had strange inconsistencies with DD-WRT releases over the years.
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) client
I feel like we are closer at least for the 4300 series. VAPs on secondary node seem to have worked fine for the few days I have had this installed. Most everything else has been good, a couple of hiccups with the DDNS/wireguard serving but I am currently guessing that might be the provider for that and not the firmware itself.
VAPs on secondary router have been working fine, mesh seems to be a bit snappier, but that may just be its loading the gui faster, no analytical support for it except cloudflare speed reports having a reduced latency and jitter on the mesh points, but not enough to call it anything yet.
Only problem i have run into is NOW the main router seems to lose WAN connection ability after about a day..It still shows connected but devices have no internet connection until hard reboot. Soft reboot via gui will not fix it, but turning switch off and on does rectify.
Note that there was still some issues with the 9/20 and 9/26 versions with VAPs on secondary that have not appeared on this...yet anyway.
The WAN connection/loss of internet on primary and thus losing internet on all routers I dont think has been an issue on the 4300 recently though it was known a few months ago, but overall this seems to have the good stuff from 9/11 and back to 8/20 as far as the secondary routers are concerned and the one hiccup so far on the wan/internet blocking. Nothing exciting in the logs. We are approaching the timeframe today where if its gonna go out, should be in the next 12 hours so we shall see if it happens again, but great job overall and THanks so much for the hard work!
I might just again mention, routers reboot daily at around 6 am via the keep alive schedule reboot, which I currently have main router rebooting and then secondary/mesh in series...Is that the best way to do it? But the failure seems to happen at about a day and a half....so far at least...again thanks so much!
Seems like its around 2 days (approx 48 hours) that the wan ip connection goes out even though it still shows connected on the primary router. everything else seems to be working including the VAP on secondary routers and I even tried on mesh...but around 2 days with this version, as had happened a few months ago, the internet connection drops until a hard (via switch) reset. Soft gui reset does not bring the connection back up. But most of the other things seem to be fixed on the mx4300. Nothing in logs when it happens, at least regular logs. intranet streaming still works to mesh and such for locally served content, its just the interent connection on the main router goes out.
I have tried to make sure its not anything else, ie cable modem dropping or whatever and will verify more the next few days as it happens again. Is there a debug setting that might offer more insight? besides serial output, since I dont have the stuff to do that yet....
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) clientt....
Sounds like the same problem I encountered!
A few more days down the road and this is consistently happening..about 2 days something will lock up, mostly on the primary router, but i switched around and it seems to be locking up on the secondary router about the same time period...
So my guess is something goes out after about 48 hours regardless of gui/daily reboot. I think because the primary has seen it more often it has happened before the secondary/others have the issue. My secondary/vap has lost the connection once or twice I think because it had longer running than the primary which I rebooted to clear the 48 hour whatever.
So it seems that if it happens on the primary and i power cycle the primary, the secondary router still works fine until around the 48ish hour mark. So rebooting/fixing the primary resets whatever the issue is on the secondary. AT least I think so...in theory then the secondary should not have a problem since the primary was power cycled more recently..but it was off for awhile so im still monitoring to try and figure out whats going on.
From moving routers around and such, i have twice gotten into the situation where the secondary was nearing the 48 hours and the primary only had been up say 24 hours...then the secondary lost the connection for devices connected to it, but primary still worked...maybe that will help the troubleshooting a bit....something is ticking down and losing the internet connection around 2days (on whichever device reaches it first).
On the secondary, it just still had devices connected but no internet. I have not had this problem with those routers just operating as mesh. I have not tried the 10/13 firmware version because waiting for the other error to be fixed on that and this has allowed me to track a bit better this weird issue with the internet loss after X time.
I have confirmed its not the modem or a switch losing connection, its something the routers seem to be doing around 2 days. I hope I am describing it clearly...and nothing showing in standard logs so far.
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) clientt....
Sounds like the same problem I encountered!
A few more days down the road and this is consistently happening..about 2 days something will lock up, mostly on the primary router, but i switched around and it seems to be locking up on the secondary router about the same time period...
So my guess is something goes out after about 48 hours regardless of gui/daily reboot. I think because the primary has seen it more often it has happened before the secondary/others have the issue. My secondary/vap has lost the connection once or twice I think because it had longer running than the primary which I rebooted to clear the 48 hour whatever.
So it seems that if it happens on the primary and i power cycle the primary, the secondary router still works fine until around the 48ish hour mark. So rebooting/fixing the primary resets whatever the issue is on the secondary. AT least I think so...in theory then the secondary should not have a problem since the primary was power cycled more recently..but it was off for awhile so im still monitoring to try and figure out whats going on.
From moving routers around and such, i have twice gotten into the situation where the secondary was nearing the 48 hours and the primary only had been up say 24 hours...then the secondary lost the connection for devices connected to it, but primary still worked...maybe that will help the troubleshooting a bit....something is ticking down and losing the internet connection around 2days (on whichever device reaches it first).
On the secondary, it just still had devices connected but no internet. I have not had this problem with those routers just operating as mesh. I have not tried the 10/13 firmware version because waiting for the other error to be fixed on that and this has allowed me to track a bit better this weird issue with the internet loss after X time.
I have confirmed its not the modem or a switch losing connection, its something the routers seem to be doing around 2 days. I hope I am describing it clearly...and nothing showing in standard logs so far.
Time will tell if it's 2 days for me too; independent of reboots seems unlikely, but something is certainly amiss.
I'd upgraded on 10/14 at ~9pm and had my disconnect and locking up of the Status page happen 10/16 at ~10am.
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) clientt....
Sounds like the same problem I encountered!
A few more days down the road and this is consistently happening..about 2 days something will lock up, mostly on the primary router, but i switched around and it seems to be locking up on the secondary router about the same time period...
So my guess is something goes out after about 48 hours regardless of gui/daily reboot. I think because the primary has seen it more often it has happened before the secondary/others have the issue. My secondary/vap has lost the connection once or twice I think because it had longer running than the primary which I rebooted to clear the 48 hour whatever.
So it seems that if it happens on the primary and i power cycle the primary, the secondary router still works fine until around the 48ish hour mark. So rebooting/fixing the primary resets whatever the issue is on the secondary. AT least I think so...in theory then the secondary should not have a problem since the primary was power cycled more recently..but it was off for awhile so im still monitoring to try and figure out whats going on.
From moving routers around and such, i have twice gotten into the situation where the secondary was nearing the 48 hours and the primary only had been up say 24 hours...then the secondary lost the connection for devices connected to it, but primary still worked...maybe that will help the troubleshooting a bit....something is ticking down and losing the internet connection around 2days (on whichever device reaches it first).
On the secondary, it just still had devices connected but no internet. I have not had this problem with those routers just operating as mesh. I have not tried the 10/13 firmware version because waiting for the other error to be fixed on that and this has allowed me to track a bit better this weird issue with the internet loss after X time.
I have confirmed its not the modem or a switch losing connection, its something the routers seem to be doing around 2 days. I hope I am describing it clearly...and nothing showing in standard logs so far.
Time will tell if it's 2 days for me too; independent of reboots seems unlikely, but something is certainly amiss.
I'd upgraded on 10/14 at ~9pm and had my disconnect and locking up of the Status page happen 10/16 at ~10am.
After several random reboots, I've rolled back to DD-WRT v3.0-r61557 std (05/31/25).
PPPoE worked immediately and time will tell how long of uptime I hit.
