Since I had already invested in a nice beefy server for running VMs on, it made a kind of sense 2 to run my router as a Virtual Machine and pick up a nice enterprise-grade switch that could handle VLANs. This means I have to replace it with something better. Unfortunately it does not support VLANs, which will be the building block of how I’ll achieve my aforementioned network separation even if I won’t talk about it in this post. I have, as most DSL Internet consumers do, a DSL modem and a home router. If you’re a keener, contrast ethernet switches against ethernet hubs. I don’t want to explain how it does this, so let’s just say it’s magic because the way switches work are actually hella interesting and fascinating. Network Switch: A switch is a device that, uh, basically is like multiple bridges where traffic from any port can be sent to any other port. There is a real difference between the two terms but I don’t know what it is.
Network Router and/or Network Gateway: A device that sits as a single point separating an outside network from an “inside”/”private” network. Useful for passing ethernet traffic from one physical media to another. Network bridge: A device that lets traffic pass through it unadultered. This is similar to KVM on Linux.įirewall: A software or hardware application that filters all network traffic coming it to keep malicious traffic out allow good traffic through. A linux alternative would be dd-wrt.įreeBSD: an open source unix clone with a different design philosophy than the more commonly-known Linux.īhyve/Iohyve: Virtualization software native to FreeBSD.
PfSense: a firewall/router project built off FreeBSD.
Warning: these are not incredibly accurate I have chosen, for better or for worse, to run my infrastructure on FreeBSD because I feel it is more approachable a UNIX to explore intimately as an enthusiast network infrastructure engineer and relatively junior DevOps person (I recently switched over after a decade being an unremarkable but experienced Software Developer). A “home lab” to me means I will have my own server infrastructure and possibly even non-trivial networking infrastructure in my own home, including separate LANs to keep my publicly facing self-hosted applications separate from my internal wireless network or video game consoles and such. I have been interested in setting up my own “home lab”.
0 kommentar(er)
