Also worth noting is that the set-name: eth0 option causes a race condition with persistient network interface naming in some images that prevents matching on anything other than mac address.
eg. this works:
version: 2
ethernets:
ens18:
dhcp4: true
match:
driver: virtio_net...
Hi @mira, Link [1] above is now at : https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html#network-config-v2
@Vengance:
You can reference the relevant section...
I see this in 8.1! Great!
Is there any way more decompression options could be added? I see a few were suggested in https://bugzilla.proxmox.com/show_bug.cgi?id=4849.
I'd specifically like to add bzip2.
Also, could the compression type be autodetected from the mime type: application/x-bzip2?
OK. So with your help and a couple of relevant posts I found elsewhere I figured it out!
It isn't a duplicate MAC.
I realised that the bridge is correctly seeing the MAC on the external interface and learning it, because the ARP is being reflected back to it by the external switch.
I got a...
Hi,
Thanks again for following up!
Here are the version numbers I could see in my install - in case they are relevant:
Linux 5.13.19-6-pve #1 SMP PVE 5.13.19-14
pve-manager/7.1-10/6ddebafe
I note you are be using the optional 5.15 kernel.
I have just now tried the following without luck...
Thanks for taking a look!
Yes, the gateway (172.20.1.1) is off host.
The host is on the bridge (172.20.1.191) vmbr0
The container is (172.20.1.181) veth100i0
The packet capture shows the ARP reply arrive on vmbr0, but not get forwarded to veth100i0 for a variable amount of time.
The firewall...
I notice this issue only occurs after the container or vm is restarted.
I have had a container running, but idle for several days now and if I start a ping to and address that eventually worked earlier, it works immediately now.
However if I restart a container, the delay is back, and recovers...
OK, So I have the same issue from the debian 11 net install iso in a VM.
I switched to virtual console 2 during the install and could ping the host, but not anything beyond vmbr0 until a few minutes worth of ARP requests go unanswered and then once the first reply arrives it comes right:
Hi Moayad,
Thanks for taking a look.
I chose 'use host settings' for DNS when creating the container, so the resolver matches the host.
I checked the containers settings below:
root@deb-11-container:~# cat /etc/resolv.conf
# --- BEGIN PVE ---
search dr.<***obfuscated***>
nameserver...
Hi,
After starting a container, a PING from inside the container to any address beyond the host it can take up to a few minutes before the replies start flowing.
root@deb-11-container:~# ping 172.20.1.1
PING 172.20.1.1 (172.20.1.1) 56(84) bytes of data.
From 172.20.1.181 icmp_seq=1 Destination...
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.