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.
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.
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.....).
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.
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
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...
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.
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.