Search results

  1. S

    wrong network interface / wol

    Enhancement/feature request opened: #5255 Directed broadcast support for "pvenode wakeonlan" -- Stefan
  2. S

    wrong network interface / wol

    I have the same issue (in 8.1.3) and looked for that feature/enhancement request in bugzilla but found nothing so I'll probably open it myself. Looking at the code it should be easy to replace the hardcoded local broadcast (255.255.255.255) with a new configuration option (e.g. "Broadcast...
  3. S

    Hostname (FQDN).......huh?

    I'd recommend to use home.arpa https://datatracker.ietf.org/doc/html/rfc8375 Stefan
  4. S

    Shutdown/reboot error nodes.

    In my case the (standalone) host waited for 3 minutes even though all guests had shut down long before. I actually used a drop-in snippet instead of editing the original service template. root@pve:~# systemctl edit pve-guests ... root@pve:~# cat...
  5. S

    4.15 based test kernel for PVE 5.x available

    Hi Thomas, With PVE5.2 and kernel 4.15.17-3-pve I was not able to run jumbo frames (MTU 9000) on an Intel I350 card (igb). Same configuration worked on two other nodes in the cluster with Broadcom NIC (tg3). Installation of pve kernel 4.15.17-13 solved the headache for me :) Thanks a lot Stefan

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!