Honestly, that's what makes it even more aggravating to me...here we are with real bugs that need fixed and very limited developer resources, and what does it get spent on? Removing existing and fully functional functionality that was working just fine as it was. Or splurging on things like MultiWAN that has a very limited userbase while introducing a ton of new bugs that remain unfixed years later. If it ain't broke... I am 100% positive that the WiFi power level setting works. I've used it for as long as I've used Tomato and it has worked on every model router I've used it on. How do I know? Because I do signal strength field testing with my phone and can see exactly how a router's signal strength measures up. Maybe it doesn't work on every supported model, but I have yet to see it not work. There have been locations where I've tweaked power levels to make devices between two meshed routers choose the better one more reliably by dropping the strength of the lower quality signal so the device will choose the other one consistently. Honestly, if we were going to change anything, I would've been pushing to move the Transmit Power setting to the Basic Network page, right beside the Enable Wireless checkbox--more like the Ubiquiti products, where Transmit Power is featured as one of the most important settings. As far as the antenna setting, I have no opinion. It's kinda awkward when there's only options for antenna A or B and I'm looking at a router with three antennas. I haven't noticed any changes when tinkering with those settings. But that's just me; maybe someone else gets use out of those settings on their router.