This time, we’d love to hear if you have you ever been confused by any of the terms or labels while setting up your device(s).
Here’s what we’d like to know:
Were there any terms or options that weren’t clear to you?
Did you have to look something up to understand what it meant?
Are there any settings you think could be renamed or explained more clearly?
Do you have suggestions for simpler or more intuitive alternatives?
Your feedback will help us make the configuration process easier and more user-friendly—especially for those who might not have a technical background.
On a couple of facebook groups I have helped with, people
did not appreciate on this screen that one entry per remote network
is needed (even though the “+” symbol is there)
if the explanation bubble said a little more, like perhaps:
*IP subnet Address (e.g. 192.168.0.0/24) of the remote networks * (one per line) that you want to connect to
I was checking something on a friends RUT device yesterday and it reminded me of a pet dislike of the GUI which goes further than just terminology, but as it “sort of“ fits into a bigger picture – I thought I should share….
I have often thought the firewall rules sections of the GUI is not the best implementation.
The overview section (STATUS > NETWORK >FIREWALL) does a “deep dive” into Iptables !
its basically an “iptables -L” sanitised into HTML
Anyone with minimal Linux networking experience will not understand the difference between the RAW/NAT/MANGLE/ETC tables and when you “mouse over” each section there is no apparent help as to what table does what.
Conversely, When I go to the firewall rules section (NETWORK > FIREWALL):
A) There is little to no correlation with what I see on the STATUS screen; is it working ? is it not? If I didn’t understand iptables its impenetrable.
B) The order of the menu might be better starting at the least complicated aspect (Zones) ending up at the most complicated (Custom Rules)? - making the pages more navigable
C) The traffic rules forwarding and port forwarding could benefit from some greater clarity Its very easy to get the two mixed up (this is what I was fixing on my friends device)
D) There are rules that I may want to apply to a fixed WAN that I do not want to apply to cellular WAN, yet it seems that in the drop down menus these get lumped together.
I hope this is useful feedback and I fully appreciate that a lot of this was inherited from the “Open Source” origins of platform.
regards
BB
[edited as the things I mainly use for bullets (asterisk and hashtag) cause unintended formatting]
I very much appreciate the continued improvement within the docs and UI of devices.
One thing I have noticed is sometime there is inconstant naming/labeling happening between the two.
for example within the docs, something is referred to as “sending data“ but within the UI of devices it is referred to as “data export“ - Please not these names purely examples -.
One thing I would also recommend is try to avoid language (read jargon)/configuration examples that require the end user to understand the language used.
apologies for the generalities and not having any cocreate examples at present.
