[SOLVED] Two physical Network Cards -> two separate Networks / Two separate Bridges... How?

[smartysmart34]

Hello all,

Entirely new to Proxmox and I haven't found anything similar yet in the Forum. What I have:
I do have a Server with two physical network Ports. Currently they are both connected to the same switch within the same network.
In the future, they will be on a managed switch, which will assign them to separate VLANs providing IPs from different networks (One will be my main internal network, the other will be my IOT playground).
But for now, they will be in the same Network, same Address range.

So what I want to do:
I want to have them both active, receiving individual fixed IP addresses. Like 192.168.3.10 and 192.168.3.11
I then want to create two bridges in Proxmox. vmbr0 and vmbr1.

vmbr0 would be the one for my main internal network and would also be the Proxmox-Admin interface and I will run 2 VMs on that one (Fileserver and Windows VM)
vmbr1 would be for my IOT Network and I will run two more VMs on that one (iobroker, Homeassist).

Currently I struggle to set them up.
In Proxmox, eno1 and eno2 are listed as "active" and I issued a "ifup eno1" as well as "ifup eno2" without system complaints.
But "ip a" does not report any IP addresses assigne dto these interfaces.

@proxmoxbox:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether a0:36:bc:ce:1a:44 brd ff:ff:ff:ff:ff:ff
    altname enp5s0
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
    link/ether a0:36:bc:ce:1a:45 brd ff:ff:ff:ff:ff:ff
    altname enp6s0
4: enx92c1961d5f9c: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 92:c1:96:1d:5f:9c brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a0:36:bc:ce:1a:44 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.10/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::a236:bcff:fece:1a44/64 scope link
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a0:36:bc:ce:1a:45 brd ff:ff:ff:ff:ff:ff
    inet6 2a02:8106:221:9f03:a236:bcff:fece:1a45/64 scope global dynamic mngtmpaddr
       valid_lft 5866sec preferred_lft 2265sec
    inet6 fe80::1c84:8ff:fea9:a698/64 scope link
       valid_lft forever preferred_lft forever
11: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr102i0 state UNKNOWN group default qlen 1000
    link/ether 4a:d3:e6:d9:3c:dd brd ff:ff:ff:ff:ff:ff
12: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:fb:4d:da:18:f4 brd ff:ff:ff:ff:ff:ff
13: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 5e:f1:c4:a4:e7:e5 brd ff:ff:ff:ff:ff:ff
14: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
    link/ether 46:fb:4d:da:18:f4 brd ff:ff:ff:ff:ff:ff

Yet, the Proxmox Web-Frontend works via 192.168.3.10:8006...

I also set up the two vmbr0/1 and set them to eno1 and eno2 respectively.

A VM which uses vmbr0 seems to be offline as it can't connect to any server...
Any guideance as to where to start here? Which information would you need?
It's my first time running two physical inetrfaces and my first time with Proxmox so I am somewhat confused, honestly...

Thank you and kind regards,
Martin

 

[smartysmart34]

Sorry to have bothered you.

So I checked in teh Guest itself and for some reason, there was a second network card. eth1. eth0 was the one initially configured and eth1 was not configured. A had to configure that as well. now the vm is online...