Problem communication VM

Disink

New Member
Jan 12, 2024
1
0
1
HI,
I used proxmox for 1 year on a dell server with 1 VM first and until now everything's working fine. Yesterday I've added a second VM on vmbr2 but with this one I can't download updates on Ubuntu VM, the port 80 and 443 doesn't reply whereas it works successfully with vmbr1.

nc -vz 128.38.28.141 443
nc: connect to 158.64.35.141 port 443 (tcp) failed: Connection refused
same for port 80

Here is my config on hypervisor :

Code:
auto lo
iface lo inet loopback
iface eno8303 inet manual
iface ens1f0 inet manual
iface ens1f1 inet manual
iface ens1f2 inet manual
iface idrac inet manual
iface ens1f3 inet manual
iface eno8403 inet manual

auto bond0
iface bond0 inet manual
       bond-slaves eno8403 ens1f1
       bond-miimon 100
       bond-mode balance-tlb

auto vmbr0
iface vmbr0 inet static
        address 128.38.28.142/25
        gateway 128.38.28.129
        bridge-ports eno8303
        bridge-stp off
        bridge-fd 0
#host

auto vmbr1
iface vmbr1 inet static
        address 128.38.28.140/25
        bridge-ports ens1f0
        bridge-stp off
        bridge-fd 0
#ticketing service

auto vmbr2
iface vmbr2 inet static
        address 128.38.28.141/25
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
#www

Two Ubuntu VM with the following config :

Code:
network:
  ethernets:
    ens18:
      addresses:
      - 128.38.28.141/25
      nameservers:
        addresses:
        - 128.xxx.xxx.xxx
        - 128.xxx.xxx.xxx
        search: []
      routes:
      - to: default
        via: 128.38.28.129
  version: 2


I've disabled the Firewall on Proxmox, the ufw is not active on both VM. I even tried to use the interface ens1f1 instead of bond0 because I thought it could be the problem without success.

It's probably a routing problem, my approach is probably wrong somewhere, but after spending 2 days on it, dunno, I'm losing patience.
 
It's probably a routing problem
It is partially a routing problem. Just considering the bare metal setup, you have configured two network interfaces to be active on the same subnet.
This is a configuration one should use when there is a really good reason for it. Setup and troubleshooting of this is beyond the scope of the forum:
https://access.redhat.com/solutions/30564

my approach is probably wrong somewhere,

I'd recommend rethinking your network strategy and experimenting in a Virtualized environment.
- 128.38.28.141/25
there appears to be a duplicate IP setup between hypervisor and VM


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!