Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
bug in naming convention
« previous
next »
Print
Pages: [
1
]
Author
Topic: bug in naming convention (Read 1771 times)
jaco.vandenberg
Newbie
Posts: 8
Karma: 0
bug in naming convention
«
on:
May 28, 2020, 11:30:33 am »
Hi,
while setting up an IPsec VPN, I checked the option "This Interface does not require an intermediate system to act as a gateway". The option is under Interfaces --> <interface created by ipsec phase 2 rule>
When checked, a Gateway is automatically created under System --> Gateways --> Single
in my case, it's AZURE-IPSEC_GW. it uses the
interface name
to construct a
gateway name
.
However, this name does not meet the restrictions for gateway names, it can not contain a dash!
So now I cannot edit the gateway, it will report
"The following input errors were detected:
The name must be less than 32 characters long and may only consist of the following characters: a-z, A-Z, 0-9, _"
Workaround for now is using a very strict naming convention that never contains any other character anytime anyplace anywhere, however I think I should report this for further finetuning the interface. If this is not the place to do so, guide me
Logged
hbc
Hero Member
Posts: 501
Karma: 47
Re: bug in naming convention
«
Reply #1 on:
May 29, 2020, 10:22:51 am »
Try
https://github.com/opnsense/core/issues
Logged
Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz (24 cores)
256 GB RAM, 300GB RAID1, 3x4 10G Chelsio T540-CO-SR
franco
Administrator
Hero Member
Posts: 17661
Karma: 1611
Re: bug in naming convention
«
Reply #2 on:
May 29, 2020, 01:57:33 pm »
via
https://github.com/opnsense/core/issues/4143
-- thanks!
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
bug in naming convention