[SOLVED] HOST / VM & Container config only works partially

c24

New Member
Dec 6, 2020
4
0
1
46
Hello everyone,

Hetzner Dedicated Server
168.xxx.yyy.aaa / Main Server IP
168.xxx.yyy.zzz / Main Server Gateway

168.xxx.yyy.111-333 / additional IPs (3 single)

On Proxmox i have a VM install in which Proxmox Back Server runs - using vmbr0 / 168.xxx.yyy.111
And that works perfectly (IN/OUT)

Now when I create a VM or Container which uses vmbr2 / 168.xxx.yyy.333
it does not work at all, no IN/OUT traffic works.
I tried every possible distribution Debian 11, Ubuntu 20.04 etc.
Also different config, like /etc/network/interfaces and netplan, in nearly endless combinations with
pointopoint and not and different variations. Nothing works. While the same set-up works on vmbr0 / 168.xxx.yyy.111

Fun-fact, in the VM (PBS) the /etc/network/interfaces only contains

Code:
address 168.xxx.yyy.111
gateway 168.xxx.yyy.aaa

Here is my HOST-config:

Code:
auto lo
iface lo inet loopback

iface eno2 inet manual

auto eno1
iface eno1 inet static
        address 168.xxx.yyy.aaa/25
        gateway 168.xxx.yyy.zzz
        pointopoint 168.xxx.yyy.zzz

auto vmbr0
iface vmbr0 inet static
        address 168.xxx.yyy.aaa/32
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        up ip route add 168.xxx.yyy.111/32 dev vmbr0

auto vmbr1
iface vmbr1 inet static
        address 168.xxx.yyy.aaa/32
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        up ip route add 168.xxx.yyy.222/32 dev vmbr1

auto vmbr2
iface vmbr2 inet static
        address 168.xxx.yyy.aaa/32
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        up ip route add 168.xxx.yyy.333/32 dev vmbr2

Does anyone has an idea why vmbr0 is working and witht he same settings vmbr2 is not?
Also firewall-settings are fine, same as for 168.xxx.yyy.111 just different IP (obviously)

Thank you for your time, and hopefully someone has an idea.
Best regards!
 
SOLVED myself,..

Obviously, my config is complete BS.

Here is how it should look like in a routed-configuration:

Code:
auto lo
iface lo inet loopback

iface eno2 inet manual

auto eno1
iface eno1 inet static
        address 168.xxx.yyy.aaa/25
        gateway 168.xxx.yyy.zzz
        pointopoint 168.xxx.yyy.zzz

auto vmbr0
iface vmbr0 inet static
        address 168.xxx.yyy.aaa/32
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        up ip route add 168.xxx.yyy.111/32 dev vmbr0
        up ip route add 168.xxx.yyy.222/32 dev vmbr0
        up ip route add 168.xxx.yyy.333/32 dev vmbr0

I also had some NIC on a container not coming up,
so all this combinations of "bugs" drove me crazy
that i changed my configuration so often that i ended up with the BS in my previous posting.

Cheers.
 

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!