Proxmox VE SDN VXLAN Setup

[@exteraNL]

Very usefull, thank you! I hope we will see support for anycast gateways in the future (one and the same on each node) to really make life simpler 😊 with dhcp or dhcp relay. I hope you will also cover EVPN and I hope you will cover the IPAM and DNS integrations. I couldn't get them to work in my lab... Some extra feedback: maybe you can show a diagram of what you are demonstrating. For example, the firewall VM you have running wasn't very clear to me at first

[@TechTutorialsDavidMcKone]

Thanks for the feedback, much appreciated I like diagrams myself and was using them in my earlier videos, so I'm not sure why I've stopped adding them in It will be interesting to see where this SDN solution goes mind For now I'm not touching DHCP or EVPN as they're still in tech preview I did try the DHCP server for instance but I was getting error messages after uninstalling Dnsmasq Even in a lab that's not a good situation to be in Fortunately I use nested hypervisors so I just rolled them back to a snapshot

[@Zambiziify]

Absolute gold dust! "_udp_4789 !" So much to wrap my head around.. Well explained demo, very helpful to debug VNet using tcpdump the and factoring in MTU sizes incl the extra additional overhead needs factoring in for real MTU. Very powerful technology!

[@TechTutorialsDavidMcKone]

I see this as a real game changer, and there's more to come when EVPN comes out of tech preview But VXLAN alone really simplifies Datacenter design as you just need to build the underlying physical network once and then after that you just make changes in the PVE cluster So much time and money to be saved and it will make life so much simpler

[@barma1309]

Thanks, very helpfull!!!!

[@TechTutorialsDavidMcKone]

Thanks for the feedback I'm glad this SDN module is now supported as it's very useful Looking forward to other parts being added

[@MadalinIgnisca]

Seems that communication between 2 vnets in same vxlan zone can’t talk out of the box. Would you have a hint?

[@TechTutorialsDavidMcKone]

Use a firewall or router if you need to connect them VNets are similar to VLANs, i.e. they provide logical separation of traffic From a private user/company perspective, each VNet will represent a different subnet e.g. 192.168.1.0/24 and 192.168.2.0/24 These days, computers in two different subnets shouldn't be able to communicate directly So in this case we've been given VNet instead of VLAN separation to achieve that You could setup a virtual router to route between the two But a firewall would be better from a security perspective

[@ZifeRRoT]

Great video, thx a lot! By the way, is there any solution to allow vms to connect to the internet from vxlan without adding additional interface?

[@TechTutorialsDavidMcKone]

Normally you'd want computers behind a firewall So I have a virtual firewall that has an interface in the vxlan network of the vms and its wan interface connects to the default linux bridge I still have a physical firewall in between the internet and my hypervisors though for extra security

[@ZifeRRoT]

@@TechTutorialsDavidMcKone normally i would do the same😁 Interesting just for some kind of weird practice

[@simo47768]

Hi Is a kubernetes sdn network a good use case for this?

[@TechTutorialsDavidMcKone]

As long as there's no need for direct contact with a physical device, then anything virtual should benefit Proxmox VE just needs to be able to put the traffic into a tunnel and then it can send it to any other node

[@barma1309]

i'll do exactly but i got problem with dhcp (( vm inside zone didn't custom ip address. VM got only 192.168.1.10x addresses((

[@TechTutorialsDavidMcKone]

Not sure on your setup In mine, although I configured a VNet and 192.168.50.x subnet, it's only for reference Even if the extra software is installed, at the moment, Proxmox VE will only supply an address for that subnet via DHCP if a Simple Zone is configured So for now, to supply an IP address via DHCP to VNets in a VXLAN Zone, you have to use a separate DHCP server And I had one connected to the subnet handing out IP addresses in the 192.168.1.x range Later on, hopefully, we'll be able to take advantage of the IPAM and DHCP solution for SDN

[@eduardooroedell]

DHCP doesn't work for vxlan on Proxmox 8.1...

[@TechTutorialsDavidMcKone]

Yeah, like I was mentioning in the video it's still in tech preview It only works for simple networks, which is a shame And you can't take advantage of the built-in IPAM solution either So I just carried on using an external DHCP server

[@eduardooroedell]

@@TechTutorialsDavidMcKone thanks for replying! I'm using a Mikrotik GR3 to make my network. Is possible to use mix Mikrotik with Proxmox vxlan?

[@TechTutorialsDavidMcKone]

@@eduardooroedell None of my devices support vxlan so it's not something I've tried I haven't seen any mention of connecting to other devices in the documentation But all the config asks for is IP addressing, so it could be worth trying

[@AdrianuX1985]

++