NGFW v16.0.0 RC available!

[jcoffin]

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.

Check the session viewer. What is the policy assigned to this traffic? Sounds like the race condition Policy manager bug from 15.1. It will be fixed shortly. Rebooting should fix the policy matching.

[jcoffin]

Does this release now support UEFI? If so, are there special instructions for going to UEFI (e.g., must be upgraded from USB, BIOS must be set to UEFI instead of Legacy, etc.)?

Read the release notes. Yes, 16.0 allows fully UEFI on most BIOS. There will be some BIOS not supported YMMV.

You can't upgrade to UEFI. If you want to change to UEFI, you need to reinstall using 16.0.

[Marty_B]

Check the session viewer. What is the policy assigned to this traffic? Sounds like the race condition Policy manager bug from 15.1. It will be fixed shortly. Rebooting should fix the policy matching.

All of the traffic is assigned to the default policy. Also from the dash board, in the policy overview widget, 0 sessions are assigned to the Kids policy.
I will reboot the system and check it out.
Thanks.

[Marty_B]

I rebooted and the problem appears to be resolved.

Thanks for your help.

[djrees]

FYI, When I click the link to download the filename shows as: UNTANGLE-NGFW-BETA-16.0.0.iso

[donhwyo]

That is the right file. Agree the name is embarrassing. It is not in the "Latest Forum News" either?

[djrees]

That is the right file. Agree the name is embarrassing. It is not in the "Latest Forum News" either?

Looks like this on my Z4, just installed as UEFI.
Build: 16.0.0.20200921T174233.a0954a20ea-1buster
Kernel: 4.19.0-8-untangle-amd64

Had to do the regular install (Graphical install failed) and try the repartition a few times to get the UEFI install to complete. Partitioned using the whole disk choice and then it continued and completed normally.

[djrees]

Read the release notes. Yes, 16.0 allows fully UEFI on most BIOS. There will be some BIOS not supported YMMV.

You can't upgrade to UEFI. If you want to change to UEFI, you need to reinstall using 16.0.

What advantage is UEFI going to give on an Untangle Firewall?

[jcoehoorn]

What advantage is UEFI going to give on an Untangle Firewall?

1. Protection from certain kinds of malware
2. Build systems that pxe boot from enterprise storage
3. Install on certain newer systems that no longer do BIOS emulation
4. Install to a boot partition larger than 2TB (you could work around this with a separate /boot partition, but with UEFI that's no longer needed on a large drive)
5. Better support for live migrations with some hypervisors (you could take an untangle guest VM instance running on one physical host and move it to another host without shutting it down)... assuming you can also move the network interfaces you need at the same time (which is also possible with some SDN-capable switches)
6. Better integration with some types of hardware monitors and tiny server LCD screens.
7. Better support for onboard management/KVM solutions like IMM/ILO/IDRAC.

[djrees]

1. Protection from certain kinds of malware
2. Build systems that pxe boot from enterprise storage
3. Install on certain newer systems that no longer do BIOS emulation
4. Install to a boot partition larger than 2TB (you could work around this with a separate /boot partition, but with UEFI that's no longer needed on a large drive)
5. Better support for live migrations with some hypervisors (you could take an untangle guest VM instance running on one physical host and move it to another host without shutting it down)... assuming you can also move the network interfaces you need at the same time (which is also possible with some SDN-capable switches)
6. Better integration with some types of hardware monitors and tiny server LCD screens.
7. Better support for onboard management/KVM solutions like IMM/ILO/IDRAC.

Wow, That is quite a difference. Thanks for the info.