Will this release candidate update to final?
Can it be installed on production machines or better to wait for final?
Printable View
Will this release candidate update to final?
Can it be installed on production machines or better to wait for final?
Riven,
If your production is important i would hold a few weeks.
I updated my NFS unit first and then run test before i suggest to any of my clients that they should update.
I requested early access and it updated last night. No issues at all.
You need to transfer the license to the new UID. https://support.untangle.com/hc/en-u...a-subscription
I am not sure that this is the correct space to post this but I am experiencing the following issue with all of the 16.X builds. This issue does not exist in version 15.1.
My untangle box has 4 NICs. I used one of these ports to connect to a seperate Wireless access point that is used by guests. This port is configured to use the "Kids" policy. All traffic through this AP/NIC should be sent this policy. This works perfectly in version 15.1, but does not work in any of the 16.0 betas.
In version 16.0 all traffic goes through the default policy and the Kids policy is ignored.
Attachment 10636
Attachment 10637
Attachment 10638
Attachment 10639
Am I doing something wrong? As I said, this works perfectly in version 15.1
Thanks.
Yes, Untangle v16.0 RC supports EFI boot, this is an updated kernel and bootloader as well as installation script to do this.
If you do not set your BIOS to boot UEFI, how do you expect it to boot UEFI?
And no, there are no instructions otherwise because that's something you do on a hardware level. Untangle is software, not hardware. Honestly, I'd suggest leaving whatever hardware you have alone. There's no benefit of booting EFI vs BIOS in Untangle's case unless EFI doesn't work, or can't work, as is the case of attempting to boot to PCIe NVME storage.