Routing between different NICS / Networks

rfox

Member
May 28, 2021
48
3
13
58
I have a Proxmox server running multiple NICs - each sits on a separate network (see diagram) - What's the best way to set up routing between the two networks so all devices on the 192.168.10.0/24 network can see the 192.168.30.0/24 network? Is it best to create a VM or container with OpenWRT or can I just add direct routes to the proxmox server?

Any advice would be welcome!

Cheers,
R.Fox
 

Attachments

I would either enable routing directy on the PVE node if you are fine with CLI configuration or setup a OPNsense/pfsense VM as a router.
Benefit of the latter would be a NIC webUI and the ability to do alot more stuff that you might need anyway (recursive DNS, adblocking, DHCP, VPN, intrusion prevention/detection, reverse proxy, HA, ...).
 
  • Like
Reactions: rfox
I would either enable routing directy on the PVE node if you are fine with CLI configuration or setup a OPNsense/pfsense VM as a router.
Benefit of the latter would be a NIC webUI and the ability to do alot more stuff that you might need anyway (recursive DNS, adblocking, DHCP, VPN, intrusion prevention/detection, reverse proxy, HA, ...).
Thanks Dunuin - I was debating about OPNSense or OpenWRT as well . . . Is there any write up or example how to do the routing directly from the CLI ??

Cheers,
R.Fox
 
Thanks Dunuin - I was debating about OPNSense or OpenWRT as well . . . Is there any write up or example how to do the routing directly from the CLI ??

Cheers,
R.Fox
OpenWRT is very lightweight, designed to be run bare metal on very low end ARM hardware (the stuff your typical ISPs router runs on so 32-128MB RAM, 2-4 slow ARM cores). Its more for consumers that want some more features like VLANs, routing between multiple subnets, not forced to run outdated manufacturers firmwares because its open souce and so on.
OPNsense on the other hand is targeted at enterprises, got more features and is meant to run on more powerful hardware (x86 machines with dedicated NICs, 1-4GB RAM, 2-4 x64 cores).

One example for a routed setup is shown in the documentation: https://pve.proxmox.com/wiki/Network_Configuration#_routed_configuration
 
Last edited:
OpenWRT is very lightweight, designed to be run bare metal on very low end ARM hardware (the stuff your typical ISPs router runs on so 32-128MB RAM, 2-4 slow ARM cores). Its more for consumers that want some more features like VLANs, routing between multiple subnets, not forced to run outdated manufacturers firmwares because its open souce and so on.
OPNsense on the other hand is targeted at enterprises, got more features and is meant to run on more powerful hardware (x86 machines with dedicated NICs, 1-4GB RAM, 2-4 x64 cores).

One example for a routed setup is shown in the documentation: https://pve.proxmox.com/wiki/Network_Configuration#_routed_configuration
Thanks again - I already have my own OPNSense firewall running (on top of ProxMox) using this device: J4125 Quad Core Firewall Pretty cool stuff!

The example you sent is not obvious how to add the routing between the nics . . . maybe I'll just try an OPNSense VM and see what happens . . .

Cheers,
R.Fox
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!