7

Hey! I know this is maybe better suited for a VMWare group, but I can't find one with the whole Reddit fiasco. So I'm hoping someone can point me in the right direction or give a bit of advice.

I have VMWare Workstation 16 currently using NAT. This has been working well for a while, as whenever I need to open a port, I just manually do it one by one. But as I've been hosting game servers it's becoming a bit tedious to do one by one and there's not an option to open ports by ranges using NAT.

I read that Bridged is what is recommended for my use case. And I've tried this but can never get it to work. I've tried deselecting all but the main NIC too.

I rent a dedicated server, I only have access to one IP with the option to purchase a secondary IP. I'm guessing it's because of this I can't get Bridge to work, because I don't have access to DHCP.

Is my only option to purchase a secondary IP, create a VM for PfSense and have that manage the DHCP? (That's even if I'm understanding this correctly)

Or would installing something like EXSi achieve what I'm trying to do?

Many thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[-] Trainguyrom@reddthat.com 1 points 2 years ago

I think you might be misunderstanding what bridging and NAT are.

Network Address Translation (NAT) is a technology that allows one IP to have many IPs behind it, and those IPs will route through a specific (potentially virtual) machine to reach things on the internet (and vice versa). In the case of a VPS hosting VMs or Containers it allows you to have many different VMs and Containers share a single IP and therefore save IPs and money.

Bridging is effectively creating a switch, so every VM would be directly connected to whatever network is a being bridged (sounds like that would be the internet in this case)

On a VPS you would almost definitely want to be using NAT

this post was submitted on 17 Jun 2023
7 points (100.0% liked)

Selfhosted

43163 readers
561 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS