shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

261
active users

#vlans

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://bsd.network/@dvl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dvl</span></a></span> hmm...</p><p>Not shure if <a href="https://infosec.space/tags/LAGG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LAGG</span></a> works across different LANs.</p><ul><li>Usually one LAGGs physical interfaces instead of <a href="https://infosec.space/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VLAN</span></a>, so the <a href="https://infosec.space/tags/VLANs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VLANs</span></a> just get transparently spread across the overlay'd LAGG.</li></ul><p>I guess one would have to setup Inter-VLAN routing instead...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>sodiboo</span></a></span> instead if using proprietary SaaS like Tailscale I can recommend using <a href="https://infosec.space/tags/pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pfSense</span></a> and other Networking-focussed <a href="https://infosec.space/tags/distros" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>distros</span></a> to manage your <a href="https://infosec.space/tags/WireGiard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WireGiard</span></a> Setup where you can easily deploy &amp; maange configs for clients and the clients themselves...</p><ul><li>Besides that you are correct: Similar to <a href="https://infosec.space/tags/LAGG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LAGG</span></a> / <a href="https://infosec.space/tags/LACP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LACP</span></a>-<a href="https://infosec.space/tags/Bonding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bonding</span></a> and <a href="https://infosec.space/tags/VLANs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VLANs</span></a>, WireGuard is a virtual interdace that is treated natively, unlike <a href="https://infosec.space/tags/tun" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tun</span></a> / <a href="https://infosec.space/tags/tap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tap</span></a> interfaces for like <a href="https://infosec.space/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenVPN</span></a>...</li></ul>