Gregory P. Smith (he/him) :python: 🚲🦝 :donor:<p>Last night in <a href="https://infosec.exchange/tags/HomeLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HomeLab</span></a> :<br> * Dang it, this proxmox server isn't booting after I removed the GPU.<br> * & I don't have inputs on left on my monitor or display cables on other machines in convenient to move places.<br> * ... Oh right! My crowdfunded <a href="https://infosec.exchange/tags/JetKVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JetKVM</span></a> arrived last month, I should open one and try it out.</p><p>Success! That new little Ethernet connected h264 streaming <a href="https://jetkvm.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">jetkvm.com/</span><span class="invisible"></span></a> is literal magic. A joy to use. Also a potential Security Nightmare, so I'm treating it as a crash-cart and won't leave it attached, at least with USB connected.</p><p>Original problem: Motherboard BIOS device numbering combined with Linux stupidity. enp3s0 turned itself into enp2s0 upon removal of the PCIe GPU (why?!?) which didn't match the setup in /etc/network/interfaces.</p><p>This is partially systemd's fault. But also Linux's in general. A friend ironically pointed out that the <a href="https://systemd.io/PREDICTABLE_INTERFACE_NAMES/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">systemd.io/PREDICTABLE_INTERFA</span><span class="invisible">CE_NAMES/</span></a> is properly in YELLING CASE even though it is the wrong solution to this decades old problem in the face of non-server hardware UEFI BIOS that renumbers IO bus ports based on device presence. The rotten cheese was merely moved, not thrown out.</p><p>I'd call my (likely hand edits) to /etc/network/interfaces and the concept of that file listing actual interfaces the problem. None of the above configuration methods really do what we _want_ to express.</p><p>"The only network interface with the active Ethernet connection? yeah use that one."</p><p>"The interface that gets an address showing X as its default gateway"</p><p>"The faster interface"</p><p>"Don't believe this interface's lies - it's an untrusted network."</p><p>There are ways to express some configuration desires in a more robust to changes manner, but they tend to be hacks instead of the first thing you reach for. Thus problems.</p>