You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Bad value
│
│ with module.ovpn_server.routeros_ovpn_server.server,
│ on ../modules/terraform-ros-ovpn-server/main.tf line 4, in resource "routeros_ovpn_server" "server":
│ 4: cipher = var.cipher
│
│ Unexpected value: aes256
But if I define value like "aes256-cbc
Terraform will perform the following actions:
# module.ovpn_server.routeros_ovpn_server.server will be updated in-place
~ resource "routeros_ovpn_server" "server" {
~ cipher = "aes256" -> "aes256-cbc"
id = "interface.ovpn-server.server"
+ reneg_sec = 3600
# (17 unchanged attributes hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
module.ovpn_server.routeros_ovpn_server.server: Modifying... [id=interface.ovpn-server.server]
╷
│ Error: from RouterOS device: invalid value for argument cipher
│
│ with module.ovpn_server.routeros_ovpn_server.server,
│ on ../modules/terraform-ros-ovpn-server/main.tf line 1, in resource "routeros_ovpn_server" "server":
│ 1: resource "routeros_ovpn_server" "server" {
│
Additional context
RouterOS expect value like "aes256"
/interface ovpn-server server
set auth=sha256,sha512 cipher=aes256 <....> tls-version=only-1.2
RouterOS v7.7
The text was updated successfully, but these errors were encountered:
Describe the bug
The routeros_ovpn_server resource expects the cipher parameter "aes256-cbc", however in routeros the valid value for is "aes256"
To Reproduce
Define value cipher = "aes256" for routeros_ovpn_server
Expected behavior
Valid values:
Stack Trace
But if I define value like "aes256-cbc
Additional context
RouterOS expect value like "aes256"
RouterOS v7.7
The text was updated successfully, but these errors were encountered: