Search results

  1. S

    Network connected but can't ping gateway / external ips or domains

    Please share your output of : # pveversion -v # cat /etc/network/interfaces
  2. S

    Network connected but can't ping gateway / external ips or domains

    100% packet loss when pinging google.com and proxmox.com is not what I would define as "DNS resolution works fine"....... From the PVE host what is the result of: # dig google.com # dig proxmox.com
  3. S

    All VMs don't boot anymore after upgrade to Proxmox 8

    Do you really need jumbo frames (mtu 9216) ? What is the result when you use standard MTU size, or delete the mtu lines in your config?
  4. S

    Proxmox 8 clients can't get ip from dhcp server

    What does this command do on your PVE host: # ip link set enp10s0f0 up
  5. S

    Proxmox 8 clients can't get ip from dhcp server

    You can try and use one of the two Intel nics. Maybe the Aquantia nic is not compatible with PVE8 and kernel 6.2.
  6. S

    PVE server not able to connect to network.

    From PVE host shell do: # pveam update # pveam available What template are you searching for?
  7. S

    PVE server not able to connect to network.

    You can ping indeed an ip address like 8.8.8.8, but you cannot ping 'google.com'. That's where DNS comes in, so please check that file like I mentioned here before.
  8. S

    PVE server not able to connect to network.

    https://en.wikipedia.org/wiki/Resolv.conf
  9. S

    PVE server not able to connect to network.

    please check this file: # /etc/resolv.conf It should contain at least one valid DNS server (like 8.8.8.8 etc) Or else add 192.168.68.1 as DNS server You can have max 3 DNS servers in this file.
  10. S

    PVE server not able to connect to network.

    From the PVE host what is the output of: # dig debian.org Also check on PVe host: # cat /etc/resolv.conf But like UdoB said, your Gateway is incorrect (or you have a very exotic network/Gateway config.....).
  11. S

    renaming vmbr_x to vmbr_y (/etc/network/interfaces)

    Thanks for your reply. I want to rename the Bridges into logical names that correspond with the nic naming. But I think I just leave it as it is...too much work and reconfiguration.
  12. S

    Successful Upgrade from 7 to 8 EXCEPT for kernel

    After you UNpin the 5.15 kernel and do a proxmox-boot-tool refresh, what is the output of # proxmox-boot-tool kernel list Maybe do a # apt reinstall pve-kernel-6.2
  13. S

    [NUC13+PVE8] Switching from grub to proxmox-boot-tool

    Sorry for asking, but what model/type NUC is this that has two onboard nics ? Google shows just this model with one nic...
  14. S

    Successful Upgrade from 7 to 8 EXCEPT for kernel

    Have you tried: # proxmox-boot-tool kernel unpin 5.15.30-2-pve # proxmox-boot-tool refresh
  15. S

    renaming vmbr_x to vmbr_y (/etc/network/interfaces)

    Hi, just a quick question: when I rename an existing vmbr0 to something like vmbr1 on the PVE host, all my vm's and lxc's loose their original vmbr0 connection. In other words, I have to re-assign in every virtual machine the new Bridge, because the old one is gone. Is there a fast way to...
  16. S

    i cant acesss web gui

    Did you do a restart of the network service after changing the ip address? systemctl restart networking Or reboot the Proxmox server if you can.
  17. S

    Strange Ping-Behaviour

    Check your firewall/switch/VLAN config, because in theory you should not get a succesfull ping reply from other devices in (isolated) VLANs....
  18. S

    5 minute delay

    In the properties of the LXC, set IPv6 to static (with empty ip address) and not dhcp.
  19. S

    Strange Ping-Behaviour

    A quick Google search shows that more people with a Shelly dimmer cannot ping this device. Also, when I do a ping command from my PVE host (192.168.1.0/24) to any other vm in a VLAN, I get a time out. (I use OpenvSwitch - OVS). But again, isolating different subnets is the purpose of VLANs.
  20. S

    [SOLVED] Additional VLAN Aware Bridge Working but VLANs not going through uplink

    So now you have "bundled" all interfaces toegether (that's what a bond is)..... I believe a bond is a kind of failover, when one cable or port fails the other one takes over. Okay, if this works for you than that's fine. Not sure though if it is THE solution. Always nice when every...