Selfhosted

40023 readers

634 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Best practice for external facing service (lemmy.world)

submitted 1 year ago by root@lemmy.world to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

On my network, I have quite a few VLANS.

One for work, one for IoT devices, one for security cameras and home automation, one for Guests, etc.

I typically keep everything inward facing, with the only way to access them via my OpenVPN connection (which only can see specific services on specific VLANs).

Recently, I thought of hosting a little Lemmy instance, since I have a couple domains I'm not doing much with.

I know I can just expose that one system/NGINX proxy and the necessary ports via WAN, but is it best practice to put external facing things on their own VLANs?

I was thinking of just throwing it on my IoT VLAN, but if it were to be compromised, it would have access to other devices on that VLAN because (to my knowledge) you cannot prevent communication between clients within the same VLAN.

you are viewing a single comment's thread
view the rest of the comments

[–] ShouldIHaveFun@lemmy.pec0ra.ch 2 points 1 year ago* (last edited 1 year ago) (1 children)

you cannot prevent communication between clients within the same VLAN.

Can't you use a firewall for this?

Anyway, my guess is it's probably better to use a separate vlan or a DMZ for that. But given my poor security experience, others can probably better help you on this one

[–] root@lemmy.world 1 points 1 year ago

To my knowledge, devices within a VLAN can see eachother, because they do not cross the firewall (since they are layer 2). I may be wrong, but that's my experience and what I've read.