OPNsense Forum

English Forums => General Discussion => Topic started by: Jyling on August 21, 2025, 09:26:29 PM

Title: If not for this, open sense would have been the best budget router out there
Post by: Jyling on August 21, 2025, 09:26:29 PM
If not for this field, open sense would have been the best budget router out there, bar none:

alias_net.png

This is the result of copying/pasting a list of subnets (ex: from the rules screen or other sources)
On top of this, the current component does not truncate leading/trailing spaces and includes them in the generated sub-component, which results in further errors even when copy/pasting the subnets one by one. This is a gigantic productivity killer. A clear-cut case in favor of KISS principle.

Could the developers consider converting this field into a plain multiline text box and doing basic deduplication upon save instead of the component that it's currently is?
Title: Re: If not for this, open sense would have been the best budget router out there
Post by: Patrick M. Hausen on August 21, 2025, 09:35:46 PM
You can paste a comma separated list of networks/hosts/whatever in these multi value fields. Prepare with a shell one-liner or your favourite text editor.
Title: Re: If not for this, open sense would have been the best budget router out there
Post by: Jyling on August 22, 2025, 10:09:13 PM
Quote from: Patrick M. Hausen on August 21, 2025, 09:35:46 PMYou can paste a comma separated list of networks/hosts/whatever in these multi value fields. Prepare with a shell one-liner or your favourite text editor.

Thanks a lot for this tip, but speaking of the component itself it's one hell of a counter-intuitive solution, especially that there is no help for the field. An added step of adding commas to the lists is not such a big deal but still extra work. Were this a simple text field, it would have been much more user-friendly.