Enable direct P2P ethernet connection between 2 computers (Windows)

I recently had to add a secondary ethernet connection between two PCs, in order to quickly transfer lots of data between them. I ended up using two USB 2.5Gbps network adapters; those computers were already on a Gigabit LAN.

 In order to prioritize the transfer over the 2.5Gbps connection, I had to make a manual entry in each computer's routing table. Let's assume the static IP address of each machine are 192.168.200.1 and 192.168.200.2.

Step 1: You need to run ROUTE PRINT and find the network interface (IF) number of the device. e.g. 49 for our example below

Step 2: Then in an elevated Command prompt, execute the following:

route -p add <destination network> MASK <net mask> <gateway> METRIC <interface metric> IF <interface number>

e.g. On 192.168.200.1 computer: route -p add 192.168.200.0 MASK 255.255.255.0 192.168.200.2 METRIC 1 IF 49

e.g. On 192.168.200.2 computer: route -p add 192.168.200.0 MASK 255.255.255.0 192.168.200.1 METRIC 1 IF 49

Now whenever you initiate network traffic between the two, it will use the direct connection (192.168.200.0 network) you setup, instead of their usual LAN (say 192.168.x.0).

Chia 2.0 GPU plotting performance compilation

Compiled summary of different Nvidia GPU plotting performance from folks on the web, using Chia 2.0.0+ bladebit.

These are across various CPU models and configurations, so use it as a rough guideline to spec your plotter hardware.

In general, 

I will update as I discover more.

GPU	System RAM (GB)	Time (s)
Tesla P4	256	485
GTX 1070	128	286
Tesla P40	256	242
RTX 3050	256	230
RTX 3060 Ti	128	187
RTX 3070	128	167
RTX 4060 Ti	128	162
RTX A4000	256	122
RTX 3070	256	97
RTX A5000	128	90
RTX 3090	256	77
RTX 4090	256	75

How to fix “Authentication is required to create a color profile/managed device” when using xrdp

For those folks getting that annoying message when RDP into a Linux host running xrdp.

Create a new config file here:

$sudo nano /etc/polkit-1/localauthority/50-local.d/45-allow-colord.pkla

and put:

[Allow Colord all Users]
Identity=unix-user:*
Action=org.freedesktop.color-manager.create-device;org.freedesktop.color-manager.create-profile;org.freedesktop.color-manager.delete-device;org.freedesktop.color-manager.delete-profile;org.freedesktop.color-manager.modify-device;org.freedesktop.color-manager.modify-profile
ResultAny=no
ResultInactive=no
ResultActive=yes

Credit: https://devanswe.rs/how-to-fix-authentication-is-required-to-create-a-color-profile-managed-device-on-ubuntu-20-04-20-10/

How to import a virtual machine (in OVA format) into Proxmox server

1.  Download the .ova file in the Proxmox server shell
2. Then do the following:

$ mkdir ova_import

$ cd ova_import

$ tar -xvf ../<filename>.ova

$ sudo qm importovf 101 ./<filename>.ovf <disk> --format qcow2

$ sudo qm importdisk 101 ./<filename>.vmdk <disk> --format qcow2

Then use the Proxmox GUI to attach the disk to the VM, configure Network and you're done!

Merge dashcam video file segments into a large MP4 file

As most dashcams save videos in 2-5 minute segments, sometimes you need to stich them together to create a full-length video - e.g. road trip footage. 

To do this, the best solution is to use FFmpeg's concat function.

Step 1: Create a file containing the list of segment file names (in Windows Command Prompt)

(for %i in (*.mp4) do @echo file '%i') > mylist.txt

Step 2: Run ffmpeg to create the output file

ffmpeg -f concat -i mylist.txt -c copy output.mp4

Force remove old drivers in Windows 11 for enabling Memory Integrity

 In Command Prompt with Administrator privilege, do the following:

pnputil /delete-driver oemXX.inf /uninstall /force

A solution for Intel ProSet Adapter Configuration Utility no longer supported in Windows 11 for managing VLANs

So I finally bit the bullet yesterday and upgraded one of my Windows 10 machine to Windows 11. I figured a lot of Win11 bugs have been ironed out by now, so I decided to get on with it before Win10 support expires in 2025.

I am pretty impressed with the overall upgrade process; all my software and documents were left intact... except for one very big issue. My Hyper-V VMs were no longer working due to the VLAN configuration being hosed.

As it turns out, Intel pulled support for the ProSet utility for Windows 11, which is what I used to configure multiple VLANs on my NIC. So, the solution is to now use Windows PowerShell commands to manually establish VLAN interfaces you need, via the Hyper-V stack. Go ahead and install the Hyper-V host components.

What you are essentially doing is to create a Hyper-V VLAN switch and attach multiple VLAN adapters to it. In the example below, we'll name your VLAN switch "VLAN-vSwitch" and I will assume your NIC is named "Ethernet" (usually by default, or find it out with "Get-NetAdapter" command). And we'll create three VLANs with ID 101, 102, and 103.

In a Windows PowerShell running as Administrator, do the following:

New-VMSwitch -name VLAN-vSwitch -NetAdapterName Ethernet -AllowManagementOS $true

Remove-VMNetworkAdapter -ManagementOS -Name VLAN-vSwitch

Add-VMNetworkAdapter -ManagementOS -Name "VLAN101" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 101

Add-VMNetworkAdapter -ManagementOS -Name "VLAN102" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 102

Add-VMNetworkAdapter -ManagementOS -Name "VLAN103" -SwitchName "VLAN-vSwitch" -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 103

Running the Get-NetAdapter command again will now show you the VLAN adapters you created. Let me know if you have any questions!