kthomas

Hi, thanks for the quick reply. The first one I bought was for my house specifically for gaming. That's when I noticed the problem with Device Manager. Even as a gamer, it's terrible and should be a high priority. For one, my daughter got in trouble and I wanted to see if she was connected. I also wanted to see if there were any devices logged in that I didn't recognize. I also had an issue setting up a roku TV and couldn't find it in the circle. I also added a device to use as backup storage for games and couldn't find the mac address. These are all very common scenarios that even cheap routers can handle for home use. So it's not exclusively a business thing. However, because the performance was good, back at work we deployed a few mostly as Access Points, or routers for small simple networks that didn't need anything fancy, but were using VoIP. We thought the QoS, bufferbloat, etc. may be useful here, so we tried it and it works great. But I assumed, like the OP, that this was some kind of 'slick' default setting, which could be switched back to "normal view". I spent loads of time trying to find that setting, until I realized it didn't exist. Regardless if gaming or in a small office, you have a basic feature that is fundamental to every router on the market that simply doesn't work. Why would you develop new features before fixing what you know is broken? In fact, one of the techs here, who is a huge gamer, specifically isn't buying this for gaming (your target market) because of this one feature. I think you guys are underestimating how bad this is. One simple tweak, that could be completed in a day, would not only make your current customers happy, but it would open up a whole new market for these otherwise amazing routers. Don't sell yourselves short "there are many other things they will likely want to focus on first" I mean come on, how hard is it to just display the info in a table instead of that circle nonsense? Or at least give us an optional table view. I've never understood how some dev teams can get real feedback from real users, and then confirmation of the exact same thing from other real users, and conclude that no one cares much about it. This would be a super easy fix that would go a long way in making your customers happy, so I think it's worth revisiting the priority. Especially since there isn't anything to "develop" because you already have the information we want to see. It's just a matter of displaying it in a view that's more useful and more readable. That can't be too terribly hard for you guys.

Hi Everyone, I created this account just to express how much I agree with the OP. I'm referring to XR500 in case it matters. I really like the OS and many of the things you've done, but this is completely useless. It's also the only reason we decided not to deploy these in several locations for clients. I read above that this is on a list but not a big priority. I also read that you guys think this is a "power user" feature. We manage business networks and I'm telling you, this is not a power user feature; it's most definitely a basic fundamental feature that should be required since version 0.0. Likewise, I'm not sure what all is on your to do list, but it's a huge mistake to think this is a low priority. It's literally the only thing that our technicians hate about these routers. There is not a single new feature they care about that would be more important than fixing this. Check out this image to see what were dealing with. As you can see, it is in fact completely useless and has caused us many headaches that no other router causes. This is a huge step back...we need a table with useful information. Plus, I don't know why these routers can't figure out device names. Other routers have no trouble. Please, reconsider making this a higher priority. I don't believe it would take much development time. Thanks!