Core 139 testing

Hi,

A first short test has been positive so far.

Bug 12198 also seems OK here and the WUI shows the DNS servers after reboot.

To the topic in the old forum: https://forum.ipfire.org/viewtopic.php?f=5&p=128558#p128558

Thanks for a great job.

EDIT: Also the beeper of my mini “beeps” here for first time. Firmware for the apu 10.0.3 works also.

Markus

1 Like

Thank you very much for your feedback!

i’m experiencing some troubles testing core 139. iso backup was working on core 138. Getting zero mb iso image.

iso backup will not work with testing versions because it cannot download the base iso.

1 Like

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]”

1 Like

Hi,

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

Edit I’ve reported a Bug: https://bugzilla.ipfire.org/show_bug.cgi?id=12260 thanks wildgunman.

IDS does not start on Banana Pi either. I was also using 81.3.27.54 as primary DNS.

Although there have been some comments that Banana Pi does not have resources for IDS, it was running, with RAM & CPU to spare, at core 130, on my fairly slow 13 mb/s link. I have not deployed it since then.

when the new (fixed) Core 139 testing version will be available?

Thanks for all the work.

1 Like

After the Core Update, IPS is working again. Thx

1 Like

work’s here too after updating again. Thanks very much.

Working for me too, on x86_64 & Banana Pi.

Although it is the service having largest consumption of memory, at 34 MB, on Banana Pi, there is still 59% free memory.

In reply to [flavio verrando] “i’m experiencing some troubles testing core 139. iso backup was working on core 138. Getting zero mb iso image.”

Backup of ISO fails on my core 138 system (not testing), too. 0 size or just a “backup.cgi” file containing the website of backup. Tested with IE, FF and Chrome. If this is due to a missing “base ISO” it would be great, if the backup interface could be enhanced to give a corresponding error message.