Search results

Resolved the issue. Short answer, another device got configured with the IP of this container. Hence the intermittent connectivity. I found this after creating a new container, still getting the problem. Then tried a CentOS container, which complained about an IP conflict on starting. That gave...

root@unifi01:~# ping -c2 10.0.0.1 PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. --- 10.0.0.1 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1020ms root@unifi01:~# arp -vn Address HWtype HWaddress Flags Mask Iface 10.0.0.132...

I'm able to force to work for a few seconds at a time by flushing the arp table. So here it is not working, a flush, then it works for a short bit (10-15 seconds later it stops working again. root@unifi01:/etc/resolvconf# ping -c1 10.0.0.1 PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. ---...

Nope. It's a static and nothing else responds when trying to reach it.

Nope. It's disabled.

Hunh. Actually, it loses all connectivity. When it was able to ping the host, it must've been in the middle of cutting over. Still trying to catch it when it does work. root@unifi01:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000...

It's pretty basic. The proxmox host (prox01) is 10.0.0.40/24. root@prox01:/etc/pve/lxc# cat 103.conf arch: amd64 cpulimit: 2 cpuunits: 1024 hostname: unifi01 memory: 2048 net0: name=eth0,bridge=vmbr0,gw=10.0.0.1,hwaddr=DA:F6:61:E0:28:65,ip=10.0.0.110/24,type=veth ostype: ubuntu rootfs...

I'm experiencing an odd issue with one of my LXC containers. It has intermittent network connectivity to anything beyond the proxmox host. I recently re-installed my entire system going to 5.1 from an old 4.2 installation where everything worked. I backed up ~15 LXC containers and 3 QEMU VMs to...