Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)
Posts
1
Comments
326
Joined
2 yr. ago

  • 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.

  • I at least got one of those little cheap half size ironing boards that I can hide by the dryer. I iron special occasion clothes and that one silk shirt I love to straighten the button strip whatever if it is egregious... Otherwise it sits unused 99.5% of the year.

  • I know right? I have seen seen vision systems do some impressive things, but they are carefully calibrated to work in a specific way under certain conditions. Some of the ones my company works with get fed CAD in real time so the robot knows what to look for.

  • 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.

    Step 1 - Create 99-default.link file

    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
    
    
      

    Step 2 - Reboot and find new name of NIC that will be based on MAC

    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.

    1. 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
    
      

    Step 3 - Fix your network config and restart network manager

    You will need to edit your /etc/network/interfaces file so the correct card is used.

    1. Make a copy of /etc/network/interfaces, just in case you mess something up.
    2. 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
    
    
      
    1. Restart your networking service. You shouldn't need to reboot. sudo systemctl restart networking.service

    Step 4 - Profit?

    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.

    1. sudo systemctl status networking.service will show you if anything went wrong and hopefully show that everything is working correctly
    2. ip -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.

  • Fuckwit is my go to. Or "Too stupid to breathe." Or bring out some Linus Torvalds, but honestly Trump doesn't deserve to be graced by that mans insults, as awesome as they are from a "JFC dude, that is going way too far", except Trump would actually deserve them unlike the poor kernel maintainers.

  • 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.

  • I wish I understood how to use them. I have half written scraps of paper and random text in random text files. Notebooks are about the best I can do. I can't write very well on a vertical board. It is really really uncomfortable and I end up obsessing on how bad it looks over solving the problem. Sometimes drawing on my iPad instead works, but that is another place to look for things.

    I do like using Markdown + Mermaid. Obsidian is a nice little note taking app once I got it configured. It just takes me forever.

  • I know right? It sucks having a curved screen with a case as it pushes my thumb in the exact worst spot on the side of the screen. I accidentally do things all the time. I rest my thumb on the case edge to try and avoid it, but if I barely tilt, it touches the oversensitive touchscreen. First world problems.

  • Thank you. I admit I don't use Firefox right now due to issues I ran in to during my trial run earlier this year. Once the battery drain issues are fixed on the Android client I can at least switch back to it on my phone.

    My company surprised me last week as we did an install and things didn't work right in Firefox for the customer. My boss and the team are committed to fixing it and doing better on browser testing. There was not a moment of hesitation on this decision. We of course told them to use Edge, Safari, or Chrome in the meantime, but by no means are we throwing it on the bottom of the "fix" pile. Team is almost done and ready to send to QA. Super proud.