[SOLVED] Changing Video Card Broke Networking

[Luke Monahan]

My first Proxmox install has been working pretty well. I'm trying to get my video card to passthrough. I read about the trick of moving it to the second pci-e slot.

I stuck some old card in the first slot and my main in the second slot. Everything seems to boot right, but I could not connect to any networking services.

I would have sworn that changing video cards would not effect networking so after an hour of messing with my onboard card and secondary pci card and getting NOTHING. I decided to move the video cards back. Everything works normal again.

Someone tell me I'm crazy.

 

[vmanz]

hehehe - you're traped by predictable interface names ...

... sorry I'm laughing because of my own despair in that thing - but I 'm also near to crying.

Since Debian 9 your NIC has a name with reference to the architekture (here: PCI-slot). Now you changed the slot and the system changed the name of the NIC.

Short solution:
Go to shell and execute the command : ip addr show

Now look for the name of your NIC and notice it.

Edit "/etc/network/interfaces" and adjust the bridge_ports entry to the actual name of the NIC.


I'm only the guy who helps you to get over the weekend. I hope anyone else will give a meaningful hint to get this [think of what Linus T. vocabulary would give] feature solved and shot back to the consumer-department at Dell software-development. Also be aware of People growing their "bil" of contributions to this forum with their "L"i"N"u"X" Competences.

Btw: you`re not crazy - but you`re on the same way right into - like me,

Greets.

 

[dietmar]

Yes, that is the predictable interface names feature. All major linux distribution use that now. The explanation can be found here:

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

 

[vmanz]

hi Dietmar,

It is amazing, that proxmox support-staff has an eye to this forum even at weekend-days. I`m soon be able to enter community subscription level.

Can you tell me about your best practice to handle this "feature". I can`t imagine you at proxmox change network cards at your test center and everytimes afterwards fiddling around the /etc/network/interfaces. Or doing mutlitiple reboots until the names changed right back after some kernel-updates.

Dietmar, please tell my your secrets.

Double-best regards back,

vmanz

 

[dietmar]

Can you tell me about your best practice to handle this "feature". I can`t imagine you at proxmox change network cards at your test center and everytimes afterwards fiddling around the /etc/network/interfaces.

I imaging that is the way everyone handles it. Changing slots of network cards is nothing we do every day.

 

[dietmar]

Or doing mutlitiple reboots until the names changed right back after some kernel-updates.

Seems you miss-understood the feature. A reboot will NOT change the name (that is the feature).

 

[vmanz]

Err, I read spent much time about in the meantime.

Because IT DID CHANGE at reboot FORMERLY. If I can reproduce that in a scienceful manner I would open a thread or bug report (and mention that it is merely a debian problem).

But for now: YOU`RE RIGHT! IT DID NOT CHANGE!

I prepared a test-system here at my side some weeks ago to do some test and now I thought is the right time (my wife accepted until now).

I actually installed a fresh 5.1-iso3 and got eno1, eno2 for the onboard devices and they remained for all the tests. In the pci-slots I did a shuffleing-raid with some extension-nics. And everything was quite predictable. Sure the dual NICs have peculiarities at their numberings

As far as I remember, with the debian-versions of formerly proxmox(5)-releases the onboard-NICs where named eth0 and eno1. Maybe there once at a reboot happened a change to eno1 and eno2 which shuffled up my configs AND my trusts in predictable network interface names.


But if it happens again I swear to you to necro this thread. Even if it is in 12 years.

Have a nice weekend, greets and thanks to the rest of the proxmox-staff,

vmanz

 

[Luke Monahan]

SO to recap...

When I change a PCI card all the bus locations will change. So I just update my /etc/network/interfaces to refer to the correct
`bus info: pci@0000:05:00.0` or `logical name: enp5s0`

Essentially create a new interface link normal, correct?
Does my on motherboard NIC fall into "Predictable Naming" My static ip/ main lan ip is vmbr0.


Here's my current conf wirth 1 video card and functioning properly.


<code>
GNU nano 2.7.4 File: /etc/network/interfaces Modified


auto lo

iface lo inet loopback


auto vmbr0

iface vmbr0 inet static

address 10.10.11.196

netmask 255.255.255.0

gateway 10.10.11.254

bridge_ports enp4s0

bridge_stp off

bridge_fd 0

##messed up from testing...

auto enp4s0

iface enp8s0 inet dhcp

</code>



<code>
root@prox:~# ifconfig

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

ether bc:5f:f4:97:62:51 txqueuelen 1000 (Ethernet)

RX packets 742509 bytes 173404280 (165.3 MiB)

RX errors 0 dropped 1782 overruns 0 frame 0

TX packets 1253606 bytes 1617139710 (1.5 GiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

device interrupt 16


lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0

inet6 ::1 prefixlen 128 scopeid 0x10<host>

loop txqueuelen 1000 (Local Loopback)

RX packets 93144 bytes 18782112 (17.9 MiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 93144 bytes 18782112 (17.9 MiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


tap201i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500

ether 3e:fe:7f:a5:b6:65 txqueuelen 1000 (Ethernet)

RX packets 319806 bytes 1521796447 (1.4 GiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 663444 bytes 133415135 (127.2 MiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 10.10.11.196 netmask 255.255.255.0 broadcast 10.10.11.255

inet6 fe80::be5f:f4ff:fe97:6251 prefixlen 64 scopeid 0x20<link>

ether bc:5f:f4:97:62:51 txqueuelen 1000 (Ethernet)

RX packets 298867 bytes 45835015 (43.7 MiB)

RX errors 0 dropped 9 overruns 0 frame 0

TX packets 42526 bytes 31071938 (29.6 MiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

</code>

 

[Dark26]

my solution :

create the file you need for the aliases in /etc/systemd/network

example :

vi /etc/systemd/network/10-intel.link

content this text :

[Match]
MACAddress=00:15:17:bc:d3:00

[Link]
Name=intel0

il you have a second card


vi /etc/systemd/network/10-realtek.link

content :

[Match]
MACAddress=d0:50:99:9c:f6:33

[Link]
Name=realtek0


the cards will always have the same name after reboot : intel0 and realtek0

in the config for the network something like that ( example ):

vi /etc/network/interfaces


iface realtek0 inet manual

iface intel0 inet manual

auto bond0
iface bond0 inet manual
slaves intel0 realtek0
bond_miimon 100
bond_mode 802.3ad


auto vmbr0
iface vmbr0 inet static
address 192.168.1.170
netmask 255.255.255.0
gateway 192.168.1.254
bridge_ports bond0
bridge_stp off
bridge_fd 0

 

[Luke Monahan]

thanks all. I didn't get the .link file working, but i was easily able to manually change the file.

 

[adjrobinson]

@Dark26 thanks so much for this, got the link files working and everything stayed the same when I put a new gpu in.