Hello everyone,

I hope you’re all doing well. I’m reaching out for some guidance on a network project I’ve been working on.

Currently, my setup includes:

  • OPNsense Firewall: This is running smoothly and is the primary gateway for my network.
  • Proxmox Server: I’m in the process of integrating this. It has a single Ethernet port for network connectivity.

My primary goal is to deploy a Pi-hole instance on the Proxmox server. I’m still weighing whether to go with a Docker container or a standalone VM for this.

Here’s the crux: My existing network devices operate in the 192.168.0.1xx IP range. I’d like the Pi-hole to be on a different subnet, specifically 192.168.33.xxx. This move is mainly for organization and segmentation purposes.

Considering the single Ethernet port on the Proxmox server and my intended setup, is this feasible? Moreover, are there specific challenges or configurations I should be aware of?

Any insights, advice, or shared experiences would be invaluable.

Thank you for your collective wisdom and time!

  • Boring@lemmy.ml
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    Subnetting and VLANs can get hard to conceptualize when they are virtualized on a single machine.

    I’d suggest going to draw.io and making a logical network diagram so that you can have a reference when setting up your network.

    If you want EVERYTHING going through piHole which is on a different subnet, easiest way I’ve done it was make going through the pihole necessary to make it to the default gateway.

    But if you have a different situation for pihole you can set up DNS relays.

    • SmilinArtist@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      yeah I should draw it out first. Right now traffic is routed trough a pihole on a raspberry

      I think I will keep this route

  • themoonisacheese@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    It should work just fine. the proxmox just sets up a bridge to the virtual interface when you install it and after that, VMs you deploy will appear in to everything else on the network as if connected through a switch.

    However, watch out about it your routing tables. If the pihole isn’t on the same network (regardless of if it is virtualized or not), you have to tell other computers on the network how to reach that other network, by making changes to their routing table, or the one in your router (that is literally its job, after all).

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Slapping another NIC and using OPNsense as a VM on Proxmox has numerous advantages, as well as a few drawbacks. And opnsense has plugins that do what pihole does if you wanted to investigate that a bit before you commit.

    • SmilinArtist@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Oh opnsense has this pihole filtering in it it self I did not know that I have to check that out