She/They
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.
I started 30 minute backups earlier. It updates from the yuzu repo and downloads all of the releases from yuzu-mainline if there are new ones. Anything else I should also backup?
I wouldn’t have a clue where to put this stuff on the interwebs, but if shit happens, I will be 1 of many backups I guess.
I wonder if the $300 is sort of like extra startup money to get better hardware, infrastructure, software improvements in the short term. I honestly have no idea. I pop on there sometimes to watch the full length videos from YouTube and there is some really great content, but not necessarily enough. Their UI/apps could definitely use some work, though I have not checked recently.
I really hope they continue to run and it looks like I need to catch up on some content. I took a break from most YouTube/TV/etc. I cancelled all of my other subscriptions, but I have no reason to not support a company like Nebula, especially at their price points.
I am not going to debate the ethics of piracy or people’s justifications for or against it. It isn’t productive. I do think this is an instance where you are better off paying for a month than spending a lot of time trying to get it another way. Sometimes, I like to put things in the perspective of I make X dollars an hour, how many man hours did I spend to do X task? Cost benefit analysis. This isn’t always practical, thus the “sometimes”.
For the love of all that is unholy, learn and get comfortable with the command line. Go install WSL if you are on Windows. Not saying you have to be a master, but learn how to compile your code manually, get around the OS, tab complete, grep, ps, and other simple commands. Learn the basics of a text editor. vim/emacs/nano. Just pick one or two. Learn how to redirect output to standard and error out. Simple shell scripts.
Debugger. If you do not know how to set breakpoints, with or without conditions, and inspect variables, go learn today. I have junior developers that can’t do this.
Critical thinking and investigation. This is a rather loaded term, but your problem solving skills will go a lot farther than how your code looks. Bad but working code can be improved. Alternative solutions can be found. You at least understand the problem and an approach to take. If you don’t understand how something works, figure it out. Ask your senior team members. Spend time in the debugger and the source code, if available. Good documentation doesn’t always exist. You will not always find the perfect answer or tutorial on the Internet. If you are going to use code off the internet, you damn well better understand how it works and how to expand on it.
Keep up with the standards and updates to the languages you use. A lot of tutorials can be out of date fairly quickly. Newer language features can be a huge boon and you get a sense of where that language is going. Older ways of using libraries and languages can be hard to avoid, but make an effort to check. Speak up to your seniors if you find something that may be useful or if something is now considered bad practice.
Look at source code on GitHub/GitLab/Whatever and then the all mighty practice.
In my opinion, once you can get a handle on the above, then you can go back and learn more advanced principles, algorithms, read textbooks, and things like that. They will make a lot more sense. This may seem a little opposite than what most people would say, but for me a lot of the things I learned in school or read previously started to click.
C# is my happy place. Started doing python more over bash scripts for complicated stuff and I like it. I mostly use Java for work and my opinion of it depends on the how much extra effort I had to spend doing something I could have done in C# in a few minutes. Otherwise it has some nice features and project Panama has been a game changer.
Everything runs 24/7, but now I am thinking about theoretical power saving modes. Besides any built in power saving whatever (a little clueless), you could always throttle the CPU more. Not sure if it would be worth it without testing with a power meter.