social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

492
active users

#y

1 post1 participant0 posts today

Y Combinator, ein im März 2005 gegründetes US-amerikanisches Gründerzentrum mit Sitz in San Francisco, Kalifornien, forderte die Trump-Regierung am Mittwoch in einem Brief auf, den europäischen Digital Markets Act (DMA) offen zu unterstützen...

techcrunch.com/2025/03/13/y-co

TechCrunch · Y Combinator urges the White House to support Europe's Digital Markets Act | TechCrunchYC sent a letter on Wednesday urging the Trump Administration to support Europe's Digital Markets Act (DMA).
#y#dma#trump

What is the most manageable way to configure VLANs on a small network (e.g. <=1 rack of servers)?

I am setting up internet-accessible mail/web servers on my home LAN with IPv4 (HAProxy/NAT) and IPv6 connectivity, and I think the easiest way will be to give them a VLAN for managing firewall rules at the internet router level.

I am leaning toward FreeBSD-based VLANS using vlan(4) because I could configure separate VLANS for separate VMs (e.g. separate rules for mail vs. web, or for different domain names, or any other reason to separate VMs on a single physical server).

However, a switch-based VLAN would be easier in some ways (just plug server into access port #x, and you are on VLAN #y).

Do you have an opinion?