Yeah, I forgot to mention that i have a switch between my router and the server. The switch im using is an HP PrpCurve 1810g-8. the port 1 of it is a Tagged port with the following vlans [1, 2, 3, 4], vlan 2 is a 10.0.2.0 network ... and vlan 4 is a 10.0.3.0 network. Port 6 of the switch is a Tagged port and not an Untagged one wich should allow all vlans out of there right?
Port 1 is where the router (pfsense? judging from the screenshot) and port 6 is where vmbr1 is connected to? It has the same VLANs configured as tagged?
Then I would try to configure an IP on the guest manually and see if you can ping the router. If that does not work you will have to debug the VLAN settings on all involved parts further and can ignore anything DHCP related. It can help to configure an IP for that VLAN on the switch to check how far you get as you then can ping the switch directly.
Then I would try to configure an IP on the guest manually and see if you can ping the router. If that does not work you will have to debug the VLAN settings on all involved parts further and can ignore anything DHCP related. It can help to configure an IP for that VLAN on the switch to check how far you get as you then can ping the switch directly.
vlan is still quite confusing for me, on vlan 3 has its port 1 tagged and port 5 is the pve host(management) and port 6 is the vmbr1, not sure if still carys vlan 4 in vlan 3 from the switch? nor could it be my trunk?
Is the mgmt interface in VLAN3? Otherwise I don't know why you would configure it untagged on the switch port where the mgmt interface of the PVE node is connected to. Otherwise if the cables are attached correctly it does look okay.
What do you mean by that? That a machine in VLAN 3 can reach a machine in VLAN 4? You need routing for that which is either done in the router/firewall or maybe the switch can do that as well. You most likely won't have any firewall capability then.