Proxmox VM cannot ping other proxmox VM on same node. Host PC cannot ping proxmox vm.

[helloworld123]

there is only 1 node. proxmox vm can access internet and also ping host and proxmox management ip but cannot ping anything else.

There is no subnetting or vlans or routing or anything fancy. I keep everything on 192.168.1.0/24

firewall on windows vm has been disabled.
firewall on proxmox has no rules.

________________________

root@b:~# iptables -L -v
Chain INPUT (policy ACCEPT 315K packets, 256M bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 303K packets, 452M bytes)
pkts bytes target prot opt in out source destination
___________________

root@b:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp4s0f0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.206/24
gateway 192.168.1.1
bridge-ports enp4s0f0
bridge-stp off
bridge-fd 0

iface enp4s0f1 inet manual

 

[cheiss]

Hi,

can you also provide the output of both pveversion -v and qm config <vmid>, replacing <vmid> with the numeric ID of the VM you mentioned? (Best to put them in code tags for better readability.)

And what is the network configuration of the VM itself (e.g. IP address, gateway, ..)?

That should give us some more information.

 

[supermicro_server]

Also, do not disable the firewall on windows, but create a rule to permit all. Then try again

 

[helloworld123]

Last login: Mon Jul 10 21:17:48 EDT 2023 on pts/1
root@b:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.3-3
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-3
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.3
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.11-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

 

[helloworld123]

vm 105: 192.168.203 /24 DG 192.168.1.1

vm 102: 192.168.1.194 /24 DG 192.168.1.1

 

[helloworld123]

nvm figured it out.
windows firewall had to be disabled on both VM's.