Hi all,
I'm trying to learn the basics of router and firmware configs, I've been watching this forum intently and you are all great mentors
I've come across my first issues that I cannot figure out and thought it was time to join and ask for help. I have successfully put Merlin's 386.1_2 on my RT-AC86U and it runs fine until I start adding devices, it then crashes and goes in to an endless boot loop cycle. Through the process of elimination I have discovered that it is a HP Envy 4520 WIFI printer that is causing it to crash. When all other devices are connected there is no issues, however as soon as I connect the HP Printer the router crashes and the boot loop cycle starts. If I reset the printer/turn if off the router boots up fine. This has blown my mind a some as I am out of my depth with this one.
To add some detail, I followed the excellent guides on performing a Nuclear reset on the router and then doing the M&M config as part of going from stock to Merlin. I also have two DSL-AC68U routers running the latest GNuton firmware in AiMesh set up and it all works perfectly until I add this printer. This issue still happens with no AiMesh setup, so I think I have ruled that out. I never had this happen before with stock firmware.
I've attached one of the crash logs from when it happens, none of it really makes sense to me, but I would love to understand if there is something really sinister going on.
Thanks![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
I'm trying to learn the basics of router and firmware configs, I've been watching this forum intently and you are all great mentors
To add some detail, I followed the excellent guides on performing a Nuclear reset on the router and then doing the M&M config as part of going from stock to Merlin. I also have two DSL-AC68U routers running the latest GNuton firmware in AiMesh set up and it all works perfectly until I add this printer. This issue still happens with no AiMesh setup, so I think I have ruled that out. I never had this happen before with stock firmware.
I've attached one of the crash logs from when it happens, none of it really makes sense to me, but I would love to understand if there is something really sinister going on.
Thanks