servers/roles/proxmox/templates/interfaces.j2

{# bridges must be named vmbrN for proxmox to care #}
{% for vlan in cluster.custom_fields.vlans | default([], true) | sort(attribute='vid') %}
# bridge and VNI for {{ vlan.name }}
auto vmbr{{ vlan.vid }}
iface vmbr{{ vlan.vid }}
    # {{ vlan.name }}
    bridge-vlan-aware no
    bridge-ports vni{{ vlan.vid }}
    bridge-stp off
    bridge-fd 0

auto vni{{ vlan.vid }}
iface vni{{ vlan.vid }}
    vxlan-id {{ vlan.vid }}
    mstpctl-bpduguard yes
    mstpctl-portbpdufilter yes

{% endfor %}

source /etc/network/interfaces.d/*
Factor frr role from debian, ceph and proxmox Consolidate base system and networking setup into debian role and BGP configuration into frr role. Add facts role to collect data from NetBox once to avoid many slow lookups. Also many other tweaks and cleanups. 2024-05-18 16:35:41 +00:00			`{# bridges must be named vmbrN for proxmox to care #}`
			`{% for vlan in cluster.custom_fields.vlans \| default([], true) \| sort(attribute='vid') %}`
			`# bridge and VNI for {{ vlan.name }}`
proxmox: use multiple non-VLAN-aware bridges The Proxmox SDN feature does not play nice with our FRR and VXLAN setup. With a single bridge we can’t have interface aliases. So use a bridge for each VLAN. Actually don’t even have VLANs, just bridges mainlined into VXLAN tunnels. Read the list of VLANs carried by Proxmox nodes from a custom field on the cluster in NetBox. Remove the vmbr0 device from individual nodes. 2024-02-20 15:40:13 +00:00			`auto vmbr{{ vlan.vid }}`
proxmox: don’t route host traffic over VNIs Very bad, much slow. 2024-05-05 10:56:58 +00:00			`iface vmbr{{ vlan.vid }}`
proxmox: use multiple non-VLAN-aware bridges The Proxmox SDN feature does not play nice with our FRR and VXLAN setup. With a single bridge we can’t have interface aliases. So use a bridge for each VLAN. Actually don’t even have VLANs, just bridges mainlined into VXLAN tunnels. Read the list of VLANs carried by Proxmox nodes from a custom field on the cluster in NetBox. Remove the vmbr0 device from individual nodes. 2024-02-20 15:40:13 +00:00			`# {{ vlan.name }}`
			`bridge-vlan-aware no`
			`bridge-ports vni{{ vlan.vid }}`
proxmox: add initial support for L2 VXLAN I heard we like L2 so I put some L2 in our L3 so we can L2 as we L3 on L2. 2023-10-18 13:01:02 +00:00			`bridge-stp off`
			`bridge-fd 0`

proxmox: use multiple non-VLAN-aware bridges The Proxmox SDN feature does not play nice with our FRR and VXLAN setup. With a single bridge we can’t have interface aliases. So use a bridge for each VLAN. Actually don’t even have VLANs, just bridges mainlined into VXLAN tunnels. Read the list of VLANs carried by Proxmox nodes from a custom field on the cluster in NetBox. Remove the vmbr0 device from individual nodes. 2024-02-20 15:40:13 +00:00			`auto vni{{ vlan.vid }}`
proxmox: don’t route host traffic over VNIs Very bad, much slow. 2024-05-05 10:56:58 +00:00			`iface vni{{ vlan.vid }}`
proxmox: use multiple non-VLAN-aware bridges The Proxmox SDN feature does not play nice with our FRR and VXLAN setup. With a single bridge we can’t have interface aliases. So use a bridge for each VLAN. Actually don’t even have VLANs, just bridges mainlined into VXLAN tunnels. Read the list of VLANs carried by Proxmox nodes from a custom field on the cluster in NetBox. Remove the vmbr0 device from individual nodes. 2024-02-20 15:40:13 +00:00			`vxlan-id {{ vlan.vid }}`
proxmox: add initial support for L2 VXLAN I heard we like L2 so I put some L2 in our L3 so we can L2 as we L3 on L2. 2023-10-18 13:01:02 +00:00			`mstpctl-bpduguard yes`
			`mstpctl-portbpdufilter yes`

			`{% endfor %}`

			`source /etc/network/interfaces.d/*`