Hi so i have one old CT container, that can access the network just fine
But when i create a new one it manages to get an IP but that is about it..
The network configuration on proxmox
cat /etc/network/interfaces
pveversion --verbose
Why can't the broken CT container access my network?
(Sorry if i dumped to much information, i have no idea what would be of use)
But when i create a new one it manages to get an IP but that is about it..
| Working CT | Broken CT |
| pct config 210
Code:
| config (pct config 100)
Code:
|
| ip link
Code:
| ip link
Code:
|
| cat /etc/network/interfaces
Code:
| cat /etc/network/interfaces
Code:
|
| cat /etc/resolv.conf
Code:
| cat /etc/resolv.conf
Code:
|
| ip neighbor show
Code:
| ip neighbor show
Code:
|
| ip r
Code:
| ip r
Code:
|
| ip a
Code:
| ip a
Code:
|
| ping 192.168.20.1
Code:
| ping 192.168.20.1
Code:
|
| Ping from proxmox ping 192.168.20.157
Code:
| Ping from proxmox ping 192.168.20.158
Code:
|
| ip route list
Code:
| ip route list
Code:
|
The network configuration on proxmox
cat /etc/network/interfaces
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface enp6s0 inet manual
iface enp0s31f6 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.98.160/24
gateway 192.168.98.1
bridge-ports enp6s0
bridge-stp off
bridge-fd 0pveversion --verbose
Code:
proxmox-ve: 8.2.0 (running kernel: 6.8.8-2-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-14
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
pve-kernel-5.15.158-1-pve: 5.15.158-1
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.12-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1Why can't the broken CT container access my network?
(Sorry if i dumped to much information, i have no idea what would be of use)
