Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
Intrusion Detection and Prevention
»
Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139)
« previous
next »
Print
Pages: [
1
]
Author
Topic: Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139) (Read 2088 times)
Bytechanger
Full Member
Posts: 239
Karma: 0
Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139)
«
on:
February 01, 2022, 07:34:21 am »
Hi,
after moving OPNSense from PC to VM all works fine, but only one thing:
Intrusion Detection doesn´t start, suricata shows following error:
2022-02-01T07:32:17 Error suricata [100526] <Error> -- [ERRCODE: SC_ERR_INVALID_YAML_CONF_ENTRY(139)] - Invalid mpm algo supplied in the yaml conf file: "hs"
What´s the matter?
Greets
Byte
Logged
Lost_Ones
Newbie
Posts: 11
Karma: 1
Re: Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139)
«
Reply #1 on:
February 14, 2022, 02:28:31 pm »
Hello,
Did you end up getting this working? I moved from qume/kvm to proxmox and I too was having an issue. My settings for the Pattern Checker was Hyperscan, and when I moved it to the default Aho-Corasick I was back in business.
Regards,
Logged
Bytechanger
Full Member
Posts: 239
Karma: 0
Re: Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139)
«
Reply #2 on:
February 14, 2022, 10:07:30 pm »
Hyperscan worked after I set CPU-model from KVM64 to 'Host' and set AES on.
I think it will read out by suricata.
So all worked fine now.
Greets
Byte
«
Last Edit: February 15, 2022, 07:06:42 am by Bytechanger
»
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
Intrusion Detection and Prevention
»
Error suricata after moving to VM - SC_ERR_INVALID_YAML_CONF_ENTRY(139)