Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
23.1 Legacy Series
»
Bug/Feature Request: Autotrim pasted data
« previous
next »
Print
Pages: [
1
]
Author
Topic: Bug/Feature Request: Autotrim pasted data (Read 684 times)
ChirpyTurnip
Newbie
Posts: 13
Karma: 0
Bug/Feature Request: Autotrim pasted data
«
on:
April 08, 2023, 04:18:45 am »
So I've just migrated from pfSense and one of the hardest parts of it was manually re-doing the configuration. The biggest pain was that after copying and pasting data OPNsense would straight away 'lock' the data into those little 'data blocks' so you cannot edit what you've just pasted, you can only click 'Save' or press 'x' on the little data blocks to delete them.
The problem I had is that my source data had spaces and commas:
192.68.1.234, 192.168.1.235, 192.168.1.236
OPNsense slaps that straight into these data blocks:
"192.168.1.234" " 192.168.1.235" " 192.168.1.236"
When you save the data is rejected as spaces have been put into the second and third IP addresses. It annoyingly does this everywhere where the data blocks are used and it meant I had to first paste my data in a text editor, strip the spaces, re-copy, then paste to OPNsense. An extra miserable step in an otherwise unnecessarily painful process.
If the UI is going to 'smart' then it should also be clever enough to TRIM the input before it converts to the block format.
As an aside I cannot believe that there is no pfSense config importer given many new users will be pfSense refugees. The data format is similar *AND* it is the OPNsense end that has all the extra lines of metadata in the XML. At a minimum something to import the FW aliases and DHCP reservations would have helped because loading them was pretty tedious (even though I did it by munging my pfSense config to look like an OPNsense export).
:-(
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
23.1 Legacy Series
»
Bug/Feature Request: Autotrim pasted data