Been using Pi-hole for several years now and Pi-hole is absolutely a lifesaver. If you are not already using a DNS sinkhole, have a look at the project. But recently I updated my pfSense hardware and started wondering if things could be done a bit more simple - by adding my DNS sinkhole directly to the same hardware. Turns out you can; pfSense has a package called pfBlockerNG, that aims to basically do something like Pi-hole. It's not strictly for ad-blocking, but rather for general-purpose DNS filtering. This makes pgBlockerNG potentially a lot more powerful than Pi-hole, but it also means the learning curve is a bit steeper. So if all you're looking for is a DNS adblock, you are fine with Pi-hole.
TODO: Convert the Metasploitable2 VMDK (VMWare image) to a VHD/VHDX (Hyper-v) image.
What you need: Except an running Hyper-v setup, all you need to download and install is Microsoft Virtual Machine Converter 3.0 (it really is 3.1) Luckily you don’t really need to use this - it is somewhat half baked and not what you expect, but the convert module is excellent, and that is the only thing we care about here. If you have a running VMware/Citrix setup running, the MS converter application could work.
Some note about my take on a Raspberry/Volumio box. This is not a expert how-to or anything like that, but just stuff that would be nice to avoid; things I would have liked to know before i started. I.e. if you are not super electricity minded, you might find something useful.
Bookshelf size Volumio box.
Export and import VM from Hyper-V Manager. Host running Hyper-V server 2012R2. Hyper-V Manager running on 2012R2.
Does not work :( Source and copy have identical SID. The ‘GenerateNewId’ parameter does not change this. You avoid running all these updates again, but no way of getting round not sysprepping the imported vm. Damn.
Running a Server 2012R2 Hyper-V Server. Exported a VM and absolutely 100% failed to import the exported VM again. Looks like running a Hyper-V manager from Windows 10 is a bad place to be. So install a fresh 2012R2 - only for running the manager. Exported from a Hyper-V manager installed on a 2012R2, from a host running 2012R2 Hyper-V Server. What could go wrong with this? Export is running fine (again), and export format is version 8 again. So Hyper-V Manager is exporting a format it cannot import. That is ... beyond strange. So MS is thinking something like: Export, update host OS and then import. As the Eurovision judges from Belarus say, “nil point” (stole that quote).2016 should be able to import version 8 VMs, but have to try.
In short: Export from Hyper-V Manager and import with Powershell Import-VM cmdlet.
Trying to install Hyper-v feature on 2012R2 Core Standard, running on ESXi 6.5 (not the Microsoft Hyper-V server 2012 R2 barebone version).
Adding the feature, result in the error message below: A hypervisor is already running.
Project: Clone an existing VM and register the clone as a new VM. Using both WinSCP and Putty. You need to enable and start SSH on the host to be able to do this.
Source: Existing VM called ‘197-2012r2’. Source directory is: ‘/vmfs/volumes/datasstore0/197-2012r2/’ and source file is ‘197-2012r2.vmdk’
Clone is ‘196-2012r2’ and use a directory called: ‘/vmfs/volumes/datasstore0/196-2012r2/’