Community Discussions
Explore the latest discussions and community conversations related to this domain.
Computer to Computer File Transfer no network? : HomeNetworking
Main Post: Computer to Computer File Transfer no network? : HomeNetworking
Computer Networking
Main Post:
I am a computer science student. I am also a freelance Web Developer. I want to learn computer networking to a point where I can "picture" the internet in my head. I want to know how packets get delivered through the internet. I don't care how complex the technical stuff gets but language should be easy to understand, If you guys have an suggestions on "where to start". Please do let me know. I like learning from youtube playlists mostly, But I dont know "what to search", or "where to start". Again I am a noob- I have some programming knowledge here and there, But thats all.
Top Comment:
This Video is an excellent start. The guy has a knack for teaching really well.
"Should I Get Into Networking?" Look Here First, Curious Wanderer! [GUIDE]
Main Post:
Pardon the silly title, I'm writing this post in the hopes that those who search this subreddit in the future come across this post before deciding that their case is too specific to be covered by the information below. Please correct me if I'm wrong.
Questions I aim to cover:
- Should I get into networking? Am I too late to get into networking?
- What degree should I get for networking? Should I get multiple degrees?
- How much will this cert/this degree/this much experience command in terms of salary?
..
TL;DR: Availability of jobs, pay grade, which certs/education to get, etc depends on: what you want to do, where you are, what you know, and can actually do, and who is hiring.
The Grand Trifecta...
...of breaking into the IT networking industry includes the following, in order of general weight:
- Experience (you've done the work in the field, you've demonstrated what you know)
- Certifications (you've studied the technology enough to pass tests)
- College/University-level degree (you've studied the technology in a lab environment)
Notice I said general weight: It depends on who's doing the interviewing/hiring. Certs may not actually have more weight than degrees - depends on who's doing the hiring/interviewing. Even experience might weigh less than the others - depends on who's hiring/interviewing!
Certs
People cheat their way through certification exams (surprise!), so they are not perceived with the same weight from employer to employer (or from coworker to coworker). Employers will almost always put great value in your past experience, some value into certs, and some into your degree. Some places enjoy certain certifications over others, some don't care at all what acronyms pop up on your resume. Having them is typically better than not having them, but they're certainly not the be-all end-all of getting hired.
Certs get your foot in the door for the interview, experience and knowledge will get you hired.
So which certs to get? That depends on what you want to do. Cisco is a big name in networking technology certification, and has a seriously fragmented tree you can pick and choose from. Most start with the CCNA Routing & Switching cert, and then specialize in fields like CCNA Voice, CCNA Security, CCNA Wireless, etc. Another vendor offering certifications related to networking includes Juniper (starting with JNCIA). The CompTIA Network+ will easily be trumped by the CCNA, so go for the latter if you can jump right in. There are other certifying bodies, but these are the most widely recognized and will probably be the best place to start if you're new to the field.
Generally speaking, you'll want to study and sit for the CCNA R&S, and branch out from there into your specific interests. For help understanding Cisco's tree of certifications, [url=http://www.cisco.com/web/learning/netacad/get_involved/careerPath.html]this visual representation[/url] will help. Remember, this is just Cisco's cert offerings - there are many others for many different areas of networking!
Degrees
Also, degrees can be bought earned anywhere these days. The name of the college doesn't matter as much as what you learn. You still have to put in a few years of your life to earn it, of course, but understand that it is (like certs) not the be-all end-all. It makes sure that you've put your hands on some equipment in a lab environment (whether physical or virtual) and that you've passed more than one test to prove it. Some employers really like to see degrees, some don't value it as much. It is better to have than not, but what you know is what gets you hired - not what acronyms you can type on your resume.
Another note about degrees, a bachelor's degree is generally only required if you're looking for a management (read: non-technical) position or career track. I've been working almost a year with an associate's and a couple certs, and I've yet to be turned down an opportunity due to a lacking degree. (Also, if you have a degree from a field not related to IT/networking, that's okay! You at least have college education, and this only works in your favour.) This will not always be true (see larger employers who need to filter out sort through thousands of applications), but if you're looking for a NOC position and are worried that they'll pass you up 'cause you've only got a 2 year degree, apply anyway, even if it says "bachelor's required." The worst they can say is "sorry, no."
So, cert and degree combos then?
Also, if you're asking about what combination of experience/certs/degrees will get you in terms of salary, it depends on your location and your career path. Remember that the cost of living is wildly different depending on where you live, and that's reflected in part in your salary. That, and the kind of employer you'll interview with, make it difficult to say how much you'll be making. If someone's reading this in the future, it's safe to say that in 2014 US dollars a networking professional with a CCIE-level certification from Cisco will typically be over the six-figure salary line no matter where they are. How high above depends on where you live, what your title is, what company you work for, etc.
Should I get into networking?
That depends: what do you want to do with yourself? You can learn routing and switching to build and troubleshoot networks, you can learn Voip systems, you can learn security, you can learn wireless, etc. Research the branches that are out there, find out what it is that your personal passion is closest to in the field, and keep reading up on that. Once you've found the one(s?) for you, schedule a class or buy a book to study for a relevant cert. Look up jobs in that field, see what you'd like to apply for when ready.
Also, if you think it's too late to get into networking (due to age or how much time you've put into education already), ask yourself what you're willing to put in the time to learn. If you have the passion, it really doesn't matter how far along you are, 'cause who's gonna stop you? If/when you do take the first jump and schedule your first networking class, please be excellent at what you do. If you know the material and understand the technology, you will do well: in class, on tests, and in the field.
How long does it take to be working in the field?
Entry-level jobs are often help-desk positions in a NOC (Network Operations Center). This is where you "earn your wings" in this field. Everyone's gotta do the helldesk for a while! After that it's a matter of what you spend your time learning and what you like to do, and how hard you beat the pavement with applying to other employers or trying to move up in your current company. You will not be a network engineer without experience, and you will not be a network engineer with just a year of experience - but you will be on your way there as long as you keep learning and never settle.
So how do I get into networking?
Hard work. If you're still not sure, YouTube/Google different networking topics to get seeing the terminology and some different network configurations. The sooner you get into the CBT Nuggets for CCNA the better as they do an excellent job of covering the topics and will give you a great intro to networking as well as being a phenomenal study tool.
What equipment should I buy to practice and learn on?
No physical equipment. You won't be able to economically build a learning network that would translate well to networks in the field. Instead, virtualizing your networks will be your best bet by far: GNS3 and Packet Tracer are the two program choices you'll hear of most. Many start with Packet Tracer, and that's what Cisco's NetAcad uses for its labs, if that piques your interest.
Should I apply for this job? I have barely any qualifications that they require--
Good god man, apply anyway!
..
I'll further edit this to better cover the questions we keep seeing daily on r/networking. Anything I missed?
Thank you for using the search, fellow redditors! :) (And thank you for the reddit gold! Never had that before!)
..
Disclaimer/Full Disclosure: I am Joseph Greene, a 25-year-old packet detective. I am a CCNP R&S, and hold an Associate's degree in Network Technology. In short, I'm no guru and I don't hold all the answers. However, I've read a few topics around r/networking through the last 6 months 1.5 2.5 years or so that almost all get answered by the information I've summarized above. I post this in the hopes that someone gets some guidance in starting their networking career, or looking to other fields.
EDIT: This information is still generally accurate as of 12/2015 08/2016. No edits to the content as of this update, just to my personal info.
Top Comment:
My general advice is thus... Learn the fundamentals, and learn them well... CCNA is fine, or whatever entry level networking cert or training you want. Don't just do it for the cert, but ACTUALLY UNDERSTAND IT. Your interviews won't ask you the softball CCNA questions, they will ask you to apply the learned knowledge in practical ways.
You should be able to tell me about the process of turning on a computer and going to www.google.com. What are the protocols involved. What potential problems exist. How might you troubleshoot any problems. Start as if the question should take 10 minutes to answer... I usually cut people off once I know they actually understand the scope of the question I'm asking, and demonstrate a deep understanding of the material.
The OSI model is generally useless (TCP model is what is actually used), but I do refer to the OSI Model when talking about troubleshooting methodology. When it comes to methodology... Have one... be consistant... I troubleshoot and teach L1 up... You can do whatever, but have a repeatable troubleshooting process...
My interviewing advice is thus... NEVER EVER TRY TO BULLSHIT. I will gladly accept an "I don't know, but I would guess <xyz>" If you bullshit, you can't be trusted to admit mistakes. As a NOC engineer or Jr Engineer, I have to be able to trust you to come to me if something breaks. I can't tell you how many people fuck up and try to hide it. They don't last long.
FYI, I've been doing Network Engineering for 17 years. I work with the worlds largest Enterprises and Service Providers. I can tell you that you can probably get a job and be a shitty network engineer, but it will be boring drudge work. If you take your time, ask endless questions of smart people you will earn a great living, get to travel, and have lots of fun and enjoy what you do... I meet both, but more of the latter, and they are great people (except for the assholes). My credentials are I got my CCNA in 1997 or so... I have a non-engineering degree. I got my first job at a small company doing dial up support, moved to a NOC at a telco, and moved up to engineering in 1.5 years. I constantly asked smart people questions, and I still do... Take your time and ask good questions.
The most practical computer networking video course you can recommend , particularly for learning real world troubleshooting scenarios?
Main Post:
I need more recommendations to help substitute for my lack of real world experience.
I have found these 2 courses to be very helpful:
Practical Networking By Ben Piper Duration 3h 26m Updated 30 Apr 2015 https://www.pluralsight.com/courses/practical-networking
Troubleshooting Network Connectivity Greg Sowell Released 9/28/2016 Skill Level Intermediate 1h 10m https://www.lynda.com/Wireshark-tutorials/Troubleshooting-Network-Connectivity/502103-2.html
Thanks a million.
Top Comment: CBT Nuggets with Jeremy Cioara
Is taking a Computer Networks class important/relevant for a CS career?
Main Post:
This might be a vague/strange question I feel, but I am deciding between taking a Computer Networks class and an Intro to AI course. Both are grad level courses, but are kind of intro based. I'm interested in the Networks course since it does seem more interesting, but from what I hear, AI/Machine Learning is very lucrative at the moment, whereas Networks/Security/Infosec is a dying breed. Is this true and is pursuing more networks courses a waste?
Top Comment:
"...Networks/Security/Infosec is a dying breed."
Think about where you heard this. Think very long and hard and try and pinpoint where exactly you got this information. When you remember, never trust industry information from that source again.
Networking is a hugely valuable skill (admittedly, I'm somewhat biased, I work on a browser networking team), and getting more, not less so. Most of the work you will do in the modern era will be distributed computing. Your code will be executing on one or more remote boxes, connected via network links, often over the Internet. Understanding how those links work is critical to building performant, reliable systems.
Also: the whole idea that there's someone out there telling new programmers that security is a "dying breed" topic is puckering. Were it up to me, system and information security would be a mandatory two-semester sequence in every CS program in the world.
All that being said, none of the skills in networking or security require a classroom environment to learn. So if you're more interested in other electives, then by all means take those. But definitely DO take the time to learn about networking and security. They are critical topics that every engineer should know, and you'll be doing yourself a disservice if you don't familiarize yourself with them.
ELI5: How do computer networks work?
Main Post:
I know that's probably a really broad question. I guess I'm specifically interested in definitions of things like IP addresses, LANs and routers and all that computer jargon.
Top Comment:
lets see. you can say that the IP is your address, like your house address. Then your mac (the serial number of your network card) is your name in this metaphor. LAN (or WAN - wide area network, might be more accurate) would then be your neighborhood and the internet a bunch of "connected" neighborhoods making a city (the internet).
Sending a letter (a packet) would then use your public address (your IP). This IP would lead to your house (your router/a LAN - local area network too). Here your router would look up your name (mac address) and send the packet to you.
When you download stuff you normally send a letter saying you would like to receive something from someone else (their IP), then they send a letter back saying OK, then you and that person send letter back and forth ( a hand-shake, how a TCP connection is established ).
Or maybe you would like to be an ass and just send info to everyone, so you have a picture you really like and send it to all addresses you come across, not waiting for a replay. This is called a UDP (no hand-shake or connection establishment)
How did you learn computer networks?
Main Post:
I have started learning CN. Past few weeks, I learnt the OSI, TCP/IP reference models. Then the dissection of different layers. I am following Tannebum's book(5th Edition).
The problem I have is that it is very much theoretical. How can I see the actual application of each layer?
OR
How can I actually implement it?
Also how to differentiate between layers' features. Most of them have Error control. How would one know which layer to fix once a problem occurs?
I don't know if I am asking the right way as I am a noob to this field.
What are the resources that you learnt CN from?
Any tips, tricks , suggestions will be welcome.
Top Comment:
Beej's Guide to Network Programming. I took a class on networking that was very much applied. Wrote a basic chat application, wrote a tool to simulate network failure, wrote a tool on top of that to compensate for failure. All very hands on, but Beej's guide got me through all of it.