this post was submitted on 28 Oct 2023
8 points (75.0% liked)

Selfhosted

60910 readers
1060 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hello. I wanted to know if it was possible to get a VMWare guest VM that's acting as my self-hosted streaming server to be accessible by other devices outside my host pc?

I know it would be able to if I just set it to a bridged network connection, but I also want it to strictly only have access to the internet through my host pc that would also be using a VPN, which is why I want to leave it on NAT.

Basically, I want all my local network devices on my router to be able to access a guest VM on my PC that is only able to access the internet through the host PC.

I'm using VMWare workstation Pro, with an Ubuntu guest VM that has Jellyfin, Plex, Jackett, and etc. for streaming media.

you are viewing a single comment's thread
view the rest of the comments
[–] BrownianMotion@lemmy.world -2 points 2 years ago

Thats not how it works.

You have a LAN and hopefully you have a firewall that shields your LAN from WAN. Your fw is probably handing out DHCP lease IP (like 192.168.x.y)

When you "bridge" your VM looks like an independant device on you LAN. Nothing at this point has allowed it to the public. Your dhcp can even give it an IP (but its probably better to set a static ip). In bridge mode, a "fake mac is spoofed alongside you nic's real mac, and only for said VM)

At that point the VM id accessible likr any other device on the LAN.

if you then want to use vpn, just connect to your LAN however that works(vpn to computer or vpn to firewall/vpn server) and access.

if you want to access from WAN without vpn, then you need to understand reverse proxying and youll need a full proper firewall\gateway device at the front of your network (like OPNsense).