Hello all - I'm by far not a networking guru,
I over the past week have purchased an ASUS RT-AC3100, installed asuswrt-merlin (so awesome!), and then pihole alongside my Emby server ( using these instructions: - https://www.reddit.com/r/pihole/comments/dfm5j4/guide_for_asuswrtmerlin_users_with_screenshots/ ). Latest versions of all btw.
Everything has been rocking along swimmingly, until I tried doing the no-script access to my bridged ISP Modem ( https://github.com/RMerl/asuswrt-merlin/wiki/Access-modem-Web-UI-on-WAN-port-(no-script) ). The script worked for about 2 minutes and then my network came down to a craaaaaaaawl and no-dns resolution for anyone / any device. Even getting to the router web gui took a good 1 minute or more using the IP address. Once I changed "Get the WAN IP automatically" back to YES, everything went back to normal! I'm thankful for not having to do a hard factory reset...
Router IP = 192.168.1.1
PiHole is on = 192.168.1.40
Modem is on = 192.168.100.1
Any insights on what may be happening, or even what I can turn on debug/log wise if I decide to try and enable the no-script UI access again to work the issue out?
I over the past week have purchased an ASUS RT-AC3100, installed asuswrt-merlin (so awesome!), and then pihole alongside my Emby server ( using these instructions: - https://www.reddit.com/r/pihole/comments/dfm5j4/guide_for_asuswrtmerlin_users_with_screenshots/ ). Latest versions of all btw.
Everything has been rocking along swimmingly, until I tried doing the no-script access to my bridged ISP Modem ( https://github.com/RMerl/asuswrt-merlin/wiki/Access-modem-Web-UI-on-WAN-port-(no-script) ). The script worked for about 2 minutes and then my network came down to a craaaaaaaawl and no-dns resolution for anyone / any device. Even getting to the router web gui took a good 1 minute or more using the IP address. Once I changed "Get the WAN IP automatically" back to YES, everything went back to normal! I'm thankful for not having to do a hard factory reset...
Router IP = 192.168.1.1
PiHole is on = 192.168.1.40
Modem is on = 192.168.100.1
Any insights on what may be happening, or even what I can turn on debug/log wise if I decide to try and enable the no-script UI access again to work the issue out?