Hello,
First of all, pretty cool and I am looking forward to 22.1!
Tdy. I was able to clean install the rc1 on my apu2 and noticed a few issues and want to report them.
1. Zfs
I received the following error '─Error: sysctl'
'sysctl: unknown oid 'vfs.zfs.min_auto_ashift'
1.1 tried a few things including guided and manual zfs install options but I always received the same error but UFS worked.
2. Console
2.1 The following msg. appears:
'HTTPS: ld-elf.so.1: /lib/libcrypto.so.111: Unsupported relocation type 572213003 in non-PLT relocations'
2.2 Point 10 - Firewall log does not work
3. Services
I do not receive an ip via dhcp on Lan - Configured the lan manually (client side) which worked to get acces to the sense, so I ran the wizard and tried again to get an ip via dhcp but nope.
3.1 I just changed 2 settings (enable forwarding and hide version) and after save and apply unbound crashed and stopped unbound without any logs (gui) + I was not possible to start unbound again via gui + still no logs.
I didn't investigated it deeper just to let u know my few things which might help.
Best & Greets!
Hi!
QuoteFirewall log does not work
plain or live?
in plain view it is necessary to set the value of the severity filter to informational or higher, because entries are written with "informational" severity (my bad. will make a pr)
QuoteI was not possible to start unbound again via gui + still no logs.
can you try to edit /usr/local/opnsense/scripts/unbound/start.sh as in https://github.com/opnsense/core/pull/5243/files ? this shoud redirect unbound start errors (before it switch logging to syslog after reading .conf) to syslog. so it may help to debug "silent" start failures
Good morning,
Regarding 1.
It sounds like ZFS kernel module did not load correctly. How much RAM does this APU2 box have?
I've done a lot of UFS and ZFS installs and haven't seen these issues.
Regarding 2.
Also an odd issue. Also because of RAM?
Regarding 3.
Strange issue, no problems here with DHCP obviously.
Unbound also needs a lot of RAM.
Conclusion:
3+ unrelated issues at once points to something wrong with the hardware, maybe in conjunction with FreeBSD 13? Just speculation at this point.
Cheers,
Franco
Quote from: mfpck on January 12, 2022, 05:34:33 PM
3. Services
I do not receive an ip via dhcp on Lan - Configured the lan manually (client side) which worked to get acces to the sense,
Same here.
No DHCP on LAN while configuring over console, havent tried to get an DHCP IP configured in GUI.
On WAN Interface DHCP works fine for v4 and v6.
No problems regarding the other issues, but I dont use unbound.
AAEON board (Securepoint RC100 G3) w/ 4GB RAM
Found another small issue, not worth a new thread...
WOL config import failed:
The following input errors were detected:
You have selected to restore an area but we could not locate the correct xml tag.
Are you sure <wol> tag is in the config.xml? Haven't heard of this oddity before.
Cheers,
Franco
Nope, this tag doesnt exist, WOL part begins with
<wol version="1.0.0">
Config was exported from 21.7.6 but after setting up WOL manually, the tag is also missing in 22.1r1 exported config.
Thanks, I'm seeing the way it tries to scan the xml and you need to excuse me I need to facepalm for a bit...
!stristr($data, "<" . $_POST['restorearea'] . ">")
Will fix this today.
Cheers,
Franco
On second thought this might already work? https://github.com/opnsense/core/commit/61e0b950cc
# opnsense-patch 61e0b950cc
FWIW, looks like this has been hiding in there for a number of years.
Cheers,
Franco
Ok. I ran memtest to double check the memory - all good.
Also I redownloaded Opnsense and reimaged it to a different stick and reinstalled Opnsense and all issues as I reported yesterday where gone, super strange... I guess the image or the stick was somehow faulty.
No issues so far !
In such cases running a health audit would be beneficial. :)
Cheers,
Franco
Quote from: franco on January 13, 2022, 11:46:45 AM
On second thought this might already work? https://github.com/opnsense/core/commit/61e0b950cc
# opnsense-patch 61e0b950cc
Yap, it works, WOL config can be restored now, thanks!