Internet access for Proxmox VXLAN
from jobbies@lemmy.zip to selfhosted@lemmy.world on 01 Jul 05:48
https://lemmy.zip/post/67116631
from jobbies@lemmy.zip to selfhosted@lemmy.world on 01 Jul 05:48
https://lemmy.zip/post/67116631
What is the best way to provide internet access to guests on a Proxmox VXLAN? Is it:
- One node (host) in the cluster is the default gateway, all traffic is routed through it. Sounds clean and simple but there’s multiple layers of jank to get it working, if it works at all
- Have a guest (lxc or VM) on the VXLAN act as a gateway. Give it two NICs - one on the vnet and another on the hosts bridge (physical lan), route traffic through the second.
My default approach is the first but despite hours of tinkering and forwarding tricks it never works. I’m leaning more to the second but having a dedicated gateway guest seems like a waste of resources - logically the host should be doing it.
And yes, SNAT is enabled 😅
#selfhosted
threaded - newest
I would also do #1, and I’d probably make it work (loooong time Linux user and persistent debugger).
#2 is probably simpler, both conceptually and technically. NAT and FW config is self-contained, and there are plenty of docs and how-tos.
Note: I’m not a proxmox user, so there could be some proxmox specific spanners… But I doubt it.
#2 with opnsense
Do you use that setup? What made you choose it?
Proxmox is a virtualization solution: let it do its job and run a vm with opnsense.
It is simple both from a virtualization and a networking perspective; your hypervisor is ‘hypervisoring’ and the firewall is firewalling, easier to maintain and debug, no custom thinkering required.
If you are at home go with #1, more fun and lots of discoveries; if you have to pay the bills, go with #2, tested, solid, easier to handoff to your colleagues.
I’m at home but networking/firewalling does my tits in - #2 for me I think 😅
(me too i did #2 at home…)
I’m always uncomfortable doing #2 anywhere but at home.