Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 22879 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM Build HDMI Issue

TomRimmer

Hello

I have had Sophos UTM running on a small test box for a while and have just purchased this bit of hardware;

http://www.mini-itx.com/store/?c=112


In the hope to run Sophos UTM again but with more NICs etc. It wasn't until installing I stumbled across the threads regarding installing UTM and the HDMI issue (stalling at 66% on hardware detection) that I realised I may have an issue using this hardware :|

The mainboard has no other display options but HDMI, is there any work around at all that will get it up and running?

Is there an option of using Mini PCI-E to VGA and if so would Sophos UTM detect this and would it work?

My other thought was to run up Windows Server on it and run UTM in a VM. To be honest I was trying to avoid this as I wanted it to be a purely Firewall device but if this was the only option I would look at it. Will a virtualised UTM be ok with the fact the Hypervisor only has native HDMI and no VGA/DVI ?



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to TheMeridian

    Thanks heaps for this response TheMeridian, sounds like you tried the exact same process of elimination as myself, right down to trying the USB Graphics adapter!

    Unfortunately my device is in production now so I can't blow it away and retry now. I did email the hardware provider though as they are likely following this thread as it was a reasonably new specialised bit of hardware which the main use for it would be firewall instances. Hopefully they will have a new build or two on a test bench that they can try this method on and confirm for readers of the thread if it is working or not.


    I will update the thread once they respond to my email :)

  • 0 in reply to TomRimmer

    Finally got around to testing this and had no luck, the install would kick off again but then came up with "Bus error (core dumped) then back to the Bash-3.2 prompt. Tried a few more BIOS settings but to no avail.

     

    While it was working in a virtual machine on Windows 10 (Windows Server 2012 etc doesn't support the I211 network cards on this board which was mega frustrating also). The issue I had was that the Virtual machine didn't seem to be able to use the modem in bridged mode and create PPPOE connections. It is like it wasn't seeing some of the traffic. Anyhow trawling the interwebs I found a few with similar problems. Some resolved it by essentially enabling a pass through mode in Windows that allows the VM direct access to the network card, unfortunately this mode is only available in the Windows Server operating system and so it was back to the drawing board for me or continue to deal with the double NAT connection :| Not to mention the inability stop Windows 10 Updates rebooting the machine occasionally.

     

    In the end I bit the bullet and installed VMWare Sphere 6.5 and setup a new VM and all issues were solved, could connect to router in bridged mode and make a direct internet connection placing the ISP statis IP on the WAN connection like I wanted, no more double NAT!! Also VMWare VSphere detects and can use all of the network cards on this board. Also it managed to solve the connecting to the bridged modem issue without having to enable device passthrough, which I figured would be the next step should the hypervisor cause issues similar to the ones experienced when the VM was on Windows 10.

     

    Anyhow thought I would throw this up here should anyone else come up against this terrible snowball of a problem.

     

    thanks

Unfiltered HTML