4 ms·
like at the kernel level? even if not, seems like a such a great exercise. i guess i'm also interested in routing... any tips on creating a network of computer
by waynesonfire 4y ago
like at the kernel level? even if not, seems like a such a great exercise.
i guess i'm also interested in routing... any tips on creating a network of computers to experiment with? I guess ideally, you'd have real hardware to assemble, . what's the next best option? VMs? jails w/ vnet?
- TYPE_FASTER 4y agoBack then, I put OpenBSD on a spare P133 with two network adapters to do something like this: https://www.openbsd.org/faq/pf/example1.html https://www.openbsd.org/faq/pf/example1.html VM and/or containers make sense today. I've got an old Mac Pro tower I found on Craigslist in the basement. 64G of RAM for it was less than $150. Since Cisco offers virtual versions of their routers, you can look at what people are doing to build home labs for practicing for Cisco certifications. The homelab subreddit has a lot of interesting examples of peoples' setups as well.
- buzer 4y agoIt depends a bit on what you want to learn exactly. E.g. do you want to just learn about basic routing, BGP, MPLS, certain vendor specific stuff (like Cisco) etc. If you mostly just want to try out what you can archive on Linux you can get quite far with doing things via network namespaces (+whatever software you want to use, e.g. BIRD or Quagga) these days. Large pro on doing things via namespaces is that you can set them up & tear them down a lot quicker compared to VMs or physical hardware & scripting those steps is a lot easier. VMs & physical hardware provide more ways to do things. At least in the past there were various limitations on what you could do emulate with Cisco VMs for example (especially on some more advanced Nexus features).