Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
VPN IPSEC UX Enhancement Request
« previous
next »
Print
Pages: [
1
]
Author
Topic: VPN IPSEC UX Enhancement Request (Read 462 times)
joelmnz
Newbie
Posts: 4
Karma: 0
VPN IPSEC UX Enhancement Request
«
on:
November 02, 2023, 10:55:25 pm »
The current layout of editing an IPSEC connection is awesome. I have come across an area where it gets messy and could be cleaner though: When a child tunnel requires NAT/BINAT.
When editing the child connection, we have the Local and Remote fields, but must go into the Firewall:NAT:One-to-One to configure the translation.
How this is handled in pfsense is much cleaner and easier to configure as per the attached image there is a section between Local and Remote where the NAT/BINAT can be configured and is always visible when editing the child in future.
Is it possible to consider adding this into the OPNsense UX?
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
VPN IPSEC UX Enhancement Request