|
redeyes posted:Not bad looking at all. Will give it a try. Thanks. No, it isn't paid only, but it's really broad. What does he want to do? If he's really into it, gently caress *nix and use a juniper or gns3 network. Anything else, please say what you actually want. I'm a Linux developer, and you have options, but what you said is frankly too generic to give suggestions
|
#
¿
Jul 28, 2014 02:20
|
|
|
|
| # ¿ May 16, 2024 06:58 |
|
|
Helushune posted:I was going to mention m0n0wall but PFSense is based off it so they pretty much go hand-in-hand. MikroTik (SA thread) seems to be fairly popular as well but I don't know much about it. I think there's something to be said about firing up a fresh linux or *BSD box, enabling IPF or IPTABLES and doing everything by hand. I've found that it helps immensely when you're trying to troubleshoot if something goes wrong or the GUI isn't working for whatever reason and you need to add a firewall rule asap. I'd agree, though that "something" is mostly fumbling through Google looking for the right syntax to do something for some concept you barely understand instead of learning it. It's 2014. Use something that doesn't get in your way or designed for it (Cisco/Juniper kit, virtualized or otherwise). No need to do it the hard way. Learn that part once you have a the concepts down pat, especially since you still have to touch sysctls for some stuff. Honestly, what does he want to learn? Because "networking" is a little too broad. And if it is just "networking", buy a ccna lab off Craigslist, get a study guide, and go from there. If it's "stuff on the network (webservers, DNS, etc)", you'll need a different tack.
|
|
#
¿
Jul 29, 2014 23:34
|
|