Created attachment 725 [details] wui of ips Hi, Intrusion Prevention Service not start in 139 Dec 12 20:15:58 cyberdyne suricata: This is Suricata version 4.1.5 RELEASE Dec 12 20:15:58 cyberdyne suricata: [ERRCODE: SC_ERR_ADDRESS_ENGINE_GENERIC(89)] - failed to parse address " 84.200.69.80 194.150.168.168" Dec 12 20:15:58 cyberdyne suricata: [ERRCODE: SC_ERR_INVALID_YAML_CONF_ENTRY(139)] - failed to parse address var “DNS_SERVERS” with value “[ 84.200.69.80 194.150.168.168]”. Please check it’s syntax Dec 12 20:15:58 cyberdyne suricata: [ERRCODE: SC_ERR_INVALID_YAML_CONF_ENTRY(139)] - basic address vars test failed. Please check /etc/suricata/suricata.yaml for errors I think the error is in the file suricata-dns-servers.yaml. Here is a space between the bracket and the first ip-address “[ 84.200.69.80 194.150.168.168]” same here. IPS is stopped in the log: [ERRCODE: SC_ERR_ADDRESS_ENGINE_GENERIC(89)] - failed to parse address " 81.3.27 .54 46.182.19.48" 13:49:19 suricata: [ERRCODE: SC_ERR_INVALID_YAML_CONF_ENTRY(139)] - failed to parse address var “DN S_SERVERS” with value “[ 81.3.27.54 46.182.19.48]”. Please check it’s syntax 13:49:19 suricata: [ERRCODE: SC_ERR_INVALID_YAML_CONF_ENTRY(139)] - basic address vars test failed. Please check /etc/suricata/suricata.yaml for errors also with space "[ 81.3.27.54 46.182.19.48] I don’t know if that’s the problem
I think it's related to 12166.
Stefan, could you please urgently fix this? We will have to rebuild the Core Update after this.
*** Bug 12256 has been marked as a duplicate of this bug. ***
https://patchwork.ipfire.org/patch/2644/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=fd2dccaabb2e28cf875d7d81c7faf90f7941f56b
https://blog.ipfire.org/post/ipfire-2-23-core-update-139-released