How do I know if I have a technical understanding of TCP/IP networking and network ar
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do I know if I have a technical understanding of TCP/IP networking and network ar
How do I know if I have a technical understanding of TCP/IP networking and network architecture?
I am considering taking a snort class, but they require I have technical understanding of TCP/IP networking and network architecture.
I have some experience with IPtables, not much, some experience with tcpdump, some experience with cisco switches, and some experience with configuring 3rd party firewall software (like the APF) for ingress/egress traffic by port and/or ip. I would say I'm at the beginner level of those, execpt for tcpdump and configuring 3rd party firewall which I am intermeidate.
if you do honestly understand tcpdump output then that's probably a good yardstick. with more information it might be clearer but i'd say you should...
- know the osi model
- know the tcp/ip model
- be able to compare the above matching up each layer
- compare tcp and udp
- understand arp
- appreciate relationships between each model layer and the realities of encapsulation
but if you're the sort of person who can appreciate things without necessarily already knowing them, then you can probably fill in the gaps yourself as you go along.
Obviously prereqs vary hugely, but i would think that for snort you could well go into quite a bit of theory in order to make the practical make sense, and lots of snort checks are analysing the health of the network packets themselves, not just the data contents.
I'd say if you comfortably understand the information required to pass the Cisco ICND course (Minus the Cisco specific commands) you should have a decent understanding of TCP/IP and networking. (addressing, Routing, Subnetting, NAT, etc.. )
Do you understand the OSI network Model ?
Do you understand the TCP/IP Network Model ?
I would imagine there would be quite a few concepts from those models referenced in an IDS course.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.