NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
name99
Oct 23, 2019Guide
length of name of attached devices
Can Netgear PLEASE allow us to use names for attached devices that are long than 15 characters? 15 characters is, frankly, amateur hour. As is forced capitalizing all the names that you were able to ...
schumaku
Oct 23, 2019Guru - Experienced User
Nighthawk App and e.g. the R9000 device names are limied to 32 chars, and no change in the first characger from lower to uppercase (as on the gaming routers.
schumaku
Oct 23, 2019Guru - Experienced User
Nighthawk App and e.g. the R9000 device names are limited to 32 chars, and no change in the first character of the string from lower to uppercase (as on the RAXnnn).
ChristineT we still can't edit posts in this community section ...
- name99Oct 23, 2019Guide
I didn't try the iOS app, but using the web interface it's 15 characters. Beyond that it just won't accept characters.
32 is closer to acceptable, but still ridiculously low (especially if people want to use unicode characters).
And the selection of devices you can classify against is utterly bizarre. Multiple particular iPhone models, but not a single IoT device? Bridge, Switch, Router, and Repeater?
And don't get me started on the bizarre editing UI.
The whole things feels like a project put together by a not especially talented 14year-old programmer 20 years ago. No concern for UI. No concern for real-world issues (like name lengths or unicode). No concern for what devices people actually see on their networks and want to name/classify.
BTW the point of the comment is not to solicit details on what namelengths are allowed where. It is to get Netgear to fix the damn apps and the web interface. I have to post here since Netgear don't seem interested in providing a bug/suggestion web page.
- michaelkenwardOct 23, 2019Guru - Experienced User
name99 wrote:
BTW the point of the comment is not to solicit details on what namelengths are allowed where. It is to get Netgear to fix the damn apps and the web interface. I have to post here since Netgear don't seem interested in providing a bug/suggestion web page.
In that case you are in the wrong place.
You should know that this community is essentially a user-to-user venue with some input from a small band of Netgear techies.
Most of the answers come from fellow users who have no connection with Netgear. They just have a lot of collective experience and are familiar with the sort of problems that turn up.They certainly have no control over what Netgear gets up to, although some seem to like to feel that they are important enough to try to pull strings from on high.
What you want is best posted in the appropriate section.
Try:
Idea Exchange For Home - NETGEAR Communities
I think that qualifies as the mysterious missing "suggestion web page".
Hope that helps.
- name99Oct 23, 2019Guide
Awesome! Netgear do a pretty awful job of NOT making that clear.
So far not especially impressed withe the user-facing parts of the company.
- schumakuOct 23, 2019Guru - Experienced User
name99 wrote:I didn't try the iOS app, but using the web interface it's 15 characters. Beyond that it just won't accept characters.
32 is closer to acceptable, but still ridiculously low (especially if people want to use unicode characters).
Played this before, and re-tested today on the Android App version - test string with some random 32 Chinese chars borrowed from the Shanghai Wikipedia entry.
The App does deny any "non-English" characters:
The R9000 (v1.0.5.2) with a slightly older Web UI than the OP's RAX does go belly up with a 400 Bad Request. The Web input field is 32 chars long - so this is not a limit to 32 Bytes.
name99 wrote:
And don't get me started on the bizarre editing UI.
1990ties Web design 8-)
name99 wrote:
And the selection of devices you can classify against is utterly bizarre. Multiple particular iPhone models, but not a single IoT device? Bridge, Switch, Router, and Repeater?
It's even worse - the number and type of devices differs between the Web UI and the App (at least for the pair mentioned above).
name99 wrote:
The whole things feels like a project put together by a not especially talented 14year-old programmer 20 years ago. No concern for UI. No concern for real-world issues (like name lengths or unicode). No concern for what devices people actually see on their networks and want to name/classify.
Reads almost like my complaint sent to Netgear some time ago - thumbs up!
Look, we're waving the flag for a looong time, trying to document such issues. Haven't got even a "thank you" or a "we are working on it." - appreciate your push of course!
- michaelkenwardOct 23, 2019Guru - Experienced User
schumaku wrote:
ChristineT we still can't edit posts in this community section ...
Some of us can. You just have to get in before anyone replies.
More worrying is the recent loss of the HTML editor. More dumbing down of the interface.
- schumakuOct 23, 2019Guru - Experienced User
michaelkenward wrote:
schumaku wrote:ChristineT we still can't edit posts in this community section ...
Some of us can. You just have to get in before anyone replies.
Some newer community sections have been set-up without the editing option - so probably a different cause here, OK.
michaelkenward wrote:More worrying is the recent loss of the HTML editor. More dumbing down of the interface.
+1000000 Complained about the minute it was gone already. It's required - because the Rich Text editor is a pitb and buggy.