But, once the NICs were reversed in the Interface Management post OS install, the correct Internal static IP was set in place and DNS was set to the SPRINGERS' SBS VM everything fell into place nicely.įor the book we were working with version 5.x of the Untangle product. How the setup routine decides which NIC is Internal and which NIC is external is not known.
#Untangle firewall object groups mac#
We set up static MAC addresses for both NICs with the intent of setting the External NIC MAC address up with a static IP reservation in our own SBS server's DHCP.ĭuring the Untangle setup routine and subsequently the Untangle Setup Wizard the NICs were reversed. The other caveat when setting up the Untangle product in a Hyper-V based VM is the NIC setup. This management will need to be accomplished via a workstation as the security settings in IE on the SBS box will not allow the Untangle management features to initialize. The Untangle product does allow HTTPS connectivity to the machine for management purposes once everything has been set up though.
Thus, we needed to be at a physical workstation whenever we needed to manage the VM directly. In the case of the Untangle VM we were not able to do so. As a result, there is no mouse capture in the VM when opened via the Hyper-V Manager ( gives console access) if connected to the Hyper-V management system via a RDP session.įor some systems, keyboard shortcuts may suffice to get about the OS and its management features.
#Untangle firewall object groups install#
In the case of the Untangle VM, there is no way to install the Hyper-V Integration Services into the VM. There are some caveats when working with non-Windows OSs as Hyper-V guests.
0 kommentar(er)
