The label entered on the Networking page are showing up on the sysinfo page. I like this.
The minor issue I noticed, is that on the Networking page, there's no place to put a label for br0. I do have an eth0 interface with a label that is associated with br0.
Can you please screenshot where you see the ability to provide a label for br0? I have checked three different types of routers (Atheros, Broadcam, Marvell) and I do not have anywhere to provide a label for br0 on any of them. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
A bit of a risky move with some of the other configuration relying on the name br0. But I found a back door way of setting br0_label via command line. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
Since I was involved in the implementation of this feature, Im interested in what this workaround is, likely will be breaking something, but who knows if there is a bug on this.
The key is that there isn't a place in the GUI to enter the label for br0, so in order to have it operate consistently, br0_label needs to be set via the command-line interface. _________________ Linksys: Several WRTxx00AC variations | Netgear: 4x WNDR4500v2, 7x WNDR4300, R6400v1 | Asus: 2x RT-AC66U | Gl.inet: 3x GL-AR150
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Apr 04, 2022 10:00 Post subject:
plawer wrote:
The key is that there isn't a place in the GUI to enter the label for br0, so in order to have it operate consistently, br0_label needs to be set via the command-line interface.
Is not a big issue to add a new column to the tables in specific pages to account new features, problem becomes when you are in certain pages the tables dont have sufficient width to accommodate yet another column and then it breaks especially when labels are too big (account for translations of table headers etc where width of label can often go from OK to insane in some languages).
Then if I hide the overflow to avoid breaking the UI everyone has something to say about either about the breakage or the fix.
In this instance the above is true, there is no more width to add a label table header and column below without causing issues in the UI, as is with current design, its not possible.
Now, I repeat this across many many threads, since how the UI is rendered from umpteen source pages ranging from webconfig files, to C source and asp files a veritable soup of hardcoded HTML and a large amount is not even translated to CSS classes, which existing CSS, a large majority are workarounds and hacks, redesigning the lot is a full time job for months at least, after finding a proof of concept that works, that alone is another set of unknown time...
All good if you are employed to do this full time, not so great when its done on spare time and for free (I do it, for the love of dd-wrt and giving something back to the project that costs $0 to me to use) and ontop you have real life to deal with also which sometimes turns shit upside down and inside out and then side projects especially opensource suffer.
