Regarding pihole setup (assuming you are using it on the WAN settings page): https://www.snbforums.com/threads/new-ac86u-firmware-3-0-0-4-386_42643.72178/page-4#post-687428So my first post so hello everyone.
After updating to this version, as someone mentioned, I also couldn't set up my DNS server (Pi-hole). I think the problem is that the server is inside the network because the external DNS servers were working. I did not check Pi-hole off-grid.
Due to problems, I downloaded the FW_RT_AC68U_300438641634 versions from the Asus website and now everything works as it should. Additionally, this old version reminded me that I had RT-AC68U was fast and responsive. The new versions are way too heavy for this router.
The place to put the Pi-Hole IP address is on LAN/DHCP Server/DNS Server. Not in WAN/DNS Server 1 or 2. The router needs to be able to connect with a DNS server on boot to set the time so it will work correctly.So my first post so hello everyone.
After updating to this version, as someone mentioned, I also couldn't set up my DNS server (Pi-hole). I think the problem is that the server is inside the network because the external DNS servers were working. I did not check Pi-hole off-grid.
Due to problems, I downloaded the FW_RT_AC68U_300438641634 versions from the Asus website and now everything works as it should. Additionally, this old version reminded me that I had RT-AC68U was fast and responsive. The new versions are way too heavy for this router.
I have always set up Pi-hole in Lan / DHCP. However, as for "too heavy", I meant the Router GUI loading speed and the router's response time when I clicked something in the menu. As for the operation of the network itself, nothing caught my attention (apart from the previously mentioned DNS problem).Regarding pihole setup (assuming you are using it on the WAN settings page): https://www.snbforums.com/threads/new-ac86u-firmware-3-0-0-4-386_42643.72178/page-4#post-687428
What do you mean by "The new versions are way too heavy for this router."? Thx.
Was never broken.Anyone know if they fixed the custom DNS yet? (LAN > DHCP Server > Manually Assigned IP around the DHCP list)
No, it is 192.168.1.x hereAnyone else notice DHCP IP addresses are assigned in the 192.168.101.x range now, despite what you set in DHCP server?
No, it is 192.168.1.x here
Anyone else notice DHCP IP addresses are assigned in the 192.168.101.x range now, despite what you set in DHCP server?
You're right, only guest DHCP clients. Must be a recent change, because I use a different class of IP addresses (Class B, not Class C) and the other DHCP clients are correctly assigned that range, and previously, guest DHCP clients would get an IP from the range I specified in DHCP server. Guess there's no way to manually configure the guest DHCP IP range?On my router it seems normal for the Guest accounts be assigned 192.168.101.x.
Custom DNS server entries via the DHCP server appears to be working for me. I upgraded from an older build so I guess I didn't notice any issue before or after. I point specific clients to a Pihole (separate host) and that is still receiving traffic.Anyone know if they fixed the custom DNS yet? (LAN > DHCP Server > Manually Assigned IP around the DHCP list)
Not really recent. Has been that way since the 386 code was released.You're right, only guest DHCP clients. Must be a recent change, because I use a different class of IP addresses (Class B, not Class C) and the other DHCP clients are correctly assigned that range, and previously, guest DHCP clients would get an IP from the range I specified in DHCP server. Guess there's no way to manually configure the guest DHCP IP range?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!