Full fresh install of Core Update 165 (testing) Development Build: master/38f5bc99 (Mar22) .iso, and restoring from a production backup of Core Update 164 Development Build: master/b69659af (profile id 238cd43f341383bfb813e9f8caa9e11d08638315) 1-) System->SSH Access: 'Set SSH port to default 22' is ENABLED, whereby the wiki indicates ... "SSH in IPFire The Internet Assigned Numbers Authority IANA has allocated port 22 to the SSH protocol, but IPFire runs SSH on port 222 by default because of security reasons." Note that a restore from the prior core backup, that had this previously disabled, does change it. 2-) Network->DHCP Server: DHCP values for BLUE, such as BLUE dhcp enabled, are not set from a restore of previous core backup. 3-) Network->DHCP Server: List of fixed leases not imported via restore from previous core backup. 4-) IP System - Snort/VRT GPLv2 Community Rules were ok on previous core 164. On 165 test they show up as one of the providers, and a forced update sets the date, but the ruleset does not appear when clicking 'Customize Ruleset' Deleting the provider, and adding it again, and doing a 'Force Ruleset Update' for it did not help. Emergingthreats.net Community Rules: ruleset were present, but none were checked. Enabled each rule and everything ok for that provider. Same for Abuse.ch SSLBL Blacklist Rules 5-) Firewall->Blue Access: Wireless configuration "Devices on Blue" is blank even after a restore from previous core backup.
Could you please provide log files so that we can investigate? This potentially might want to be five individual bug tickets.
No problem Michael. Just let me know which files (logs) I should be pulling up. I'm not an expert yet on location of various log files and thir contents. Meanwhile I be further testing to try and determine if the problem is on the side of the 164 (test) backup, (which was restored from a 163 backup), or if the issue is actually on the restore side of the core 165 (test).
Please see bug https://bugzilla.ipfire.org/show_bug.cgi?id=12817 which I just raised. Manfred Knick and I have been working on this during today on the forum.
I only saw this bug after I had raised the other one.
(In reply to Adolf Belka from comment #4) > I only saw this bug after I had raised the other one. Yes I just saw that. I will try later today to restore my 165 (test) from an even earlier backup like 163 and 161, thus skipping the 164 altogether.
*** This bug has been marked as a duplicate of bug 12817 ***