Nostr Web Client

Sys admin shit is hell.

Proxmox and its first VM working great... until it isn't. Spontaneously. Looks like everything is still running but the networking is getting knocked out.

Googling... specific ethernet controller + specific driver release = these failures. Sure, yeah, that classic "r8168 vs r8169" gotcha.

How do I install/revert to r8168? Enable `non-free-firmware` apt sources. But, what... can't resolve the domains? Total DNS failure... Oh, DNS server is set to localhost? Update to 8.8.8.8 (this is shit I'm surprised I know and am not happy it's taking space in my brain). Ah, now able to resolve DNS.

Cool, back to apt. Can't update from an unsecure repository? Okay, googling... edit `/etc/apt/sources.list` (again).

Nope, not there. Ah, remove the proxmox enterprise repos...

(endless spiraling sys admin hell continues)

Marcelinho 2y ago

keith you are bothered with the same issues as me with proxmox and the realtek network driver😅

Reply to this note

Please Login to reply.

Discussion

Marcelinho 2y ago

i will try the kernel downgrade to 5.x.x lts

Keith Mukai 2y ago

I "fixed" it by finally managing to install the r8168 driver. But after a reboot, networking was totally dead. I haven't had time to do any further debugging.

Marcelinho 2y ago

Q1: Have you installed "pve-headers" before the "r8169-dkms" package?

Q2: In the folder "/etc/modprobe.d" is a "r8168-dkms.conf"

Uncomment the last line and reboot this fix worked for me. but network is still unstable, so I will try the 5.15 kernel.

Marcelinho 2y ago

Network looks more stable with kernel 6.2.16-3 (I think you Proxmox 8 runs with >=6.2.16-6)

Keith Mukai 2y ago

So far so good for me with Proxmox v7.4-3! Zero network dropouts.