Would be good to have the possibility to optionally change additional information in node name.
Therefore the GUI could have checkboxes, text fields etc.
Additional information could be
- option (checkbox) to add mac right after node name, instead of hardcoding this,
e.g. " (66:72:03:3d:7e:32)"
- option (text field) to add a definable prefix, e.g. short community name "[FFWP]"
- option (text field) to add a definable suffix for 5GHz
- option (checkbox) to add a increasing number (loop counter) to name - in case there are nodes with duplicate names
- option (checkbox) to add hardware right after node name, e.g. " / TP-Link TL-WDR3600 v1"
If neither mac (Point 1) nor "5GHz"-suffix (Point 3) is checked then default to appending "(5GHz)" for uniqueness in 5GHz band.
so results might look like this:
2.4GHz:
66:72:03:3d:7e:32|KUS-Ulmet-1
66:72:03:3d:7e:32|[FFWP]0123_KUS-Ulmet-1
66:72:03:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1
66:72:03:3d:7e:32|KUS-Ulmet-1(66:72:03:3d:7e:32)
66:72:03:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1(66:72:03:3d:7e:32)
0123 is number from point 4 (with left padded zeros, 4 digits).
5GHz:
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1(5GHz)
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1(66:72:04:3d:7e:32)
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1(5GHz)
and similar combinations...
Maybe hardware name could be shortend due to available space.
A model abbreviation could therefore be defined in ./data/hardware.json, e.g. "TL-WDR3500v1".
Then shown string could be shortend to e.g.:
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1/TL-WDR3500v1(5GHz)
Would be good to have the possibility to optionally change additional information in node name.
Therefore the GUI could have checkboxes, text fields etc.
Additional information could be
e.g. " (66:72:03:3d:7e:32)"
If neither mac (Point 1) nor "5GHz"-suffix (Point 3) is checked then default to appending "(5GHz)" for uniqueness in 5GHz band.
so results might look like this:
2.4GHz:
66:72:03:3d:7e:32|KUS-Ulmet-1
66:72:03:3d:7e:32|[FFWP]0123_KUS-Ulmet-1
66:72:03:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1
66:72:03:3d:7e:32|KUS-Ulmet-1(66:72:03:3d:7e:32)
66:72:03:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1(66:72:03:3d:7e:32)
0123 is number from point 4 (with left padded zeros, 4 digits).
5GHz:
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1(5GHz)
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1(66:72:04:3d:7e:32)
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1 / TP-Link TL-WDR3500 v1(5GHz)
and similar combinations...
Maybe hardware name could be shortend due to available space.
A model abbreviation could therefore be defined in ./data/hardware.json, e.g. "TL-WDR3500v1".
Then shown string could be shortend to e.g.:
66:72:04:3d:7e:32|[FFWP]KUS-Ulmet-1/TL-WDR3500v1(5GHz)