Wait, is that actually Garbage? That was the first thing that popped into my head when I saw the picture. That Bond music video she did was awesome. World is Not Enough.
She/They
Wait, is that actually Garbage? That was the first thing that popped into my head when I saw the picture. That Bond music video she did was awesome. World is Not Enough.
Sorry, didn’t make it home until today and not sure if you get notifications on edits. You will need a monitor and keyboard hooked up to your server as you will not have ssh access until the network config is “fixed”. I would do the below with the GPU removed, so you know 100% that your networking config is correct before mucking about further.
Add a /etc/systemd/network/99-default.link
with the below contents.
# SPDX-License-Identifier: MIT-0
#
# This config file is installed as part of systemd.
# It may be freely copied and edited (following the MIT No Attribution license).
#
# To make local modifications, one of the following methods may be used:
# 1. add a drop-in file that extends this file by creating the
# /etc/systemd/network/99-default.link.d/ directory and creating a
# new .conf file there.
# 2. copy this file into /etc/systemd/network or one of the other paths checked
# by systemd-udevd and edit it there.
# This file should not be edited in place, because it'll be overwritten on upgrades.
[Match]
OriginalName=*
[Link]
NamePolicy=mac
MACAddressPolicy=persistent
I forget if you have to reboot, but I am going to assume so. At this point, you can get the new name of your nic card and fix your network config.
ip link
should list all of your nic devices, both real and virtual. Here is how mine looks like for reference, with the MAC obfuscated:1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxAABBCCDDEEFF: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
You will need to edit your /etc/network/interfaces
file so the correct card is used.
/etc/network/interfaces
, just in case you mess something up.sudo vim /etc/network/interfaces
(or whatever text editor makes you happy)
It will need to look something like below. I have to have DHCP turned on for mine, so your config likely uses static. Really all you need to do is change wherever it says enp yada yada to the enxAABBCCDDEEFF
you identified above. source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
iface enxAABBCCDDEEFF inet manual
auto vmbr0
iface vmbr0 inet dhcp
#iface vmbr0 inet static
#address 192.168.5.100/20
#gateway 192.168.0.1
bridge-ports enxAABBCCDDEEFF
bridge-stp off
bridge-fd 0
sudo systemctl restart networking.service
Hopefully at this point you have nework access again. Check the below, do some ping tests, and if it doesn’t work, double check that you edited the interfaces file correctly.
sudo systemctl status networking.service
will show you if anything went wrong and hopefully show that everything is working correctlyip -br addr show
should show that the interface is up now.lo UNKNOWN 127.0.0.1/8 ::1/128
enxAABBCCDDEEFF UP
vmbr0 UP 192.168.5.100/20
At this point, if all is well, I would reboot anyways, just to make sure. If you add any GPUs, sata drives, other PCI device, disable/enable wifi/bt in the BIOS, or anything else that changes the PCI numbering, you don’t have to worry about your NIC changing.
I am not at home, but what I did was change the 99-default.link file. I found this from the two pages below. https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES https://wiki.debian.org/NetworkInterfaceNames
Basically, by doing this, your nic cards will be forcibly named using the mac address:
#/etc/systemd/network/99-default.link
[Match]
OriginalName=*
[Link]
NamePolicy=mac
MACAddressPolicy=persistent
Afterwards, you will need to reboot and then update your network config file to use the correct names. I don’t ever change the network config with the GUI in proxmox as it has wrecked it too many times. I will update this reply again later with some more information on what to do.
🤣 no need. I certainly am not Linus levels of stickler on it and don’t sit there and worry about it. I just found the concepts he is trying to teach very helpful. Fail fast and breaking things up into smaller methods that do “a thing”.
See, when I was in school, they didn’t teach fail fast and if anything they told you not to. Nowadays, we have moved past that nonsense. I gave it a shot about a year ago, and it has made me a better programmer. I am not going to sit there and count braces, but things are a lot easier when you get the error cases over with and out of the way.
There are always going to be exceptions, but I have personally found a lot of value in using ‘fail fast’, and making more smaller methods that say what they do. I am not always great at that second part, but it is a process. As someone with severe ADHD, it has made it a lot easier to work through problems. Sure, you can end up with more lines of code, but who cares. Compiler should be optimizing most of that shit out anyway.
https://m.youtube.com/watch?v=CFRhGnuXG-4
Watch this. I have found that this makes it way easier to debug shit, is more readable, and cuts down on mistakes.
Hey, you ok? I am not ok today, but I definitely don’t want to fill my skull with bullets. Go wash your sheets/bedding. For whatever reason, clean sheets are the best.
I changed my settings to name nic cards by mac address instead of the enumeration as I got sick of the name changing when I would add/remove pci devices.
In all of chihuahuas I have met, only one was a psychotic rage monster. The rest totally tracks. Now Pomeranians…those things drive me insane. I absolutely love dogs, but I cannot stand Pomeranians. WHERE IS THE OFF SWITCH.
It looks like with multiple power cubes you can break it up. My favorite thing about the switch is the separate joy cons. This is far far far less painful for me to hold than traditional controllers. If this worked on Linux, Mac, PlayStation, and my Steamdeck, I might try it, as long as I could return it if it doesn’t work out.
I struggle with buttons in general. My palms are too small so I can’t wrap my hand around them very well. I have to death grip with my palm or I drop it, but I am constantly shifting around as my fingers can’t reach certain things easily either. The off-axis joysticks on an Xbox controller is a no go as I have to hold the controller rotated a bit which means that up isn’t up. I do much better with PS5 controllers, but still get a lot of pain in my hands if I play too much.
I lucked out. Success at last! Now I can continue to code furiously doing things I know how to do.
Been there. Done that. FML on searching for programming help some days. Versioning is a nightmare as the way you “used” to do things is no longer relevant and the rest of the results are some asshole saying it is a duplicate question that was answered 10 years ago…that is no longer fucking relevant!
Sorry. Yesterday sucked. I hope today is less frustration and more things working like they are supposed to.
I use this on all on my Pis. It just works. I like the text config file for headless installation and how you can even add scripts to run on install too.
I never considered old DOS games until now. Thank you!
I think I vaguely remember something about that, but I would be pretty upset if the keyboard navigation was unusable. It is almost as bad as the stupid mouse enabled BIOSs that never work. It doesn’t even work on the Dell laptop I have for work. The keyboard navigation is always extra special in those cases and involves a lot of button mashing to get to the correct thing, if I can figure it out at all.
I don’t use wired mice either and had to dig the old gaming mouse out recently so I could get to some menus on a new machine to pair the mouse. I have done the mouse pairing thing through console and it isn’t the best experience, especially if you are trying to figure out if things are working in the first place. For me, I could figure it out. For a new user, you are asking a lot.
Just give me an old school OS installer with simple menus, easy keyboard navigation, and the bare minimum guidance needed to not entirely fuck it up.
I love purple, but I constantly click on Discord instead of Teams throughout the day. Too many icons with the same or similar color scheme.
I am so glad my new job had sense to say no. Their cost benefit analysis pretty much said the amount of pain, man hours, and bullshit it would cost to run far outweighed the higher price of the alternative product they went with.
The best was on arch because I had no idea how to use pacman, which I needed to install man, when I needed how to use pacman. I will have to take a look at tldr. I mostly use Debian without a desktop environment, but have an Arch VM for gaming here and there. Works out.
I get confused every time I install a distro and man isn’t installed by default. I guess I get the bare minimum philosophy, but it throws me off every time. First thing I install is vim, man, git, and probably a couple other things I can’t remember right now.
I do like a decent man page that has examples for us dummies and I have found that they have improved a lot over the years.
I had to change mine to mac address naming on my proxmox server after the second time the name changed due to a GPU or SSD being added. It was kind of like, so what, if an SSD dies suddenly or I have some issue with a device you are going to rename my fucking nic card again while I am trying to troubleshoot? Absolutely deranged.