To be fair, Linux systems also require superuser rights for a process which wants to bind to a port below 1024. 67 and 68 today are DHCP/BOOTP, and HyperV binds that port to provision IP addresses to VMs, just like it gets bound by the virtual machine manager on my pc when i open it. Only difference is that Hyper-V is always active and i have to open the VM-Manager.
It’s the always active part that is the problem. I wouldn’t care if I needed elevated rights to do it when I needed to. Instead I literally have to use a virtual machine to set addresses on some devices, or else have to go through the update and restart process required to turn it off. And then turn it back on again to use the VM I need.
I truly hate that crappy industrial software has me chained to windows at work.
To be fair, Linux systems also require superuser rights for a process which wants to bind to a port below 1024. 67 and 68 today are DHCP/BOOTP, and HyperV binds that port to provision IP addresses to VMs, just like it gets bound by the virtual machine manager on my pc when i open it. Only difference is that Hyper-V is always active and i have to open the VM-Manager.
It’s the always active part that is the problem. I wouldn’t care if I needed elevated rights to do it when I needed to. Instead I literally have to use a virtual machine to set addresses on some devices, or else have to go through the update and restart process required to turn it off. And then turn it back on again to use the VM I need.
I truly hate that crappy industrial software has me chained to windows at work.