virtual Switching between Hosts

[sysadminfromhell]

Hey there,

maybe I am stupid or I missing something. Idk
So i wanted to create a virtual Firewall for testing and sandboxing with some VMs.
I created a Linux Bridge without a port but I have the problem that i cannot reach the vm from a different host even its the same vswitch config.
Is there something I miss? I guess theoretically and only from the logic I need a physical nic to route the traffic between the hosts right?
Can I do that with one nic which is utilized alredy by a different bridge?

Kind regards,

 

[bobmc]

if you have a switch that supports VLANs you could span vlan traffic between the hosts

 

[sysadminfromhell]

So the way to go would be:
Create VLANs, Make the Brides VLAN Aware then?
Can u give me a quick overview?

 

[bobmc]

Create a VLAN interface on either host, allow tagged traffic on each port on the switch

e.g

iface eno1 inet manual

iface eno1.5 inet manual

auto vmbr0v5
iface vmbr0v5 inet manual
        bridge-ports eno1.5
        bridge-stp off
        bridge-fd 0

auto vmbr0
iface vmbr0 inet static
        address  10.10.10.10/24
        gateway  10.10.10.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

 

[sysadminfromhell]

Does the VLAn Traffic needs to be tagged or untagged to the hosts then?

 

[sysadminfromhell]

nevermind I could figure it out myself. but for now I face a different problem. I may need a different switch because I use a Netgear one which support VLAN 802.1Q Tagging but If I tag it correctly I can access the Proxmox Host but not the switch anymore and another way around.
So its kind of a mess and I need to figure it out later then.

 

[bobmc]

the switch ports assigned to the two proxmox hosts should be left as untagged on vlan1 but should be tagged for vlan5, this shouldn't affect your existing setup.

Once this is done, a vm on one host with a nic assigned to vmbr0v5 should be able to communicate with a vm on the other host, setup in the same way and also in vlan5, on the same subnet.

 

[sysadminfromhell]

So just to confirm that:




and thats it?

 

[bobmc]

vmbr0v30 is not linked to eno1.30 but otherwise, that looks OK

 

[sysadminfromhell]

vmbr0v30 is not linked to eno1.30 but otherwise, that looks OK

Yea its because of the v inside the name. i renamed it to just vmbr030 and now its connected. I will test it out