The Bits and Bytes of Computer Networking

share ›
‹ links

Below are the top discussions from Reddit that mention this online Coursera course from Google.

Offered by Google. This course is designed to provide a full overview of computer networking. We’ll cover everything from the fundamentals ... Enroll for free.

Reddsera may receive an affiliate commission if you enroll in a paid course after using these buttons to visit Coursera. Thank you for using these buttons to support Reddsera.

Taught by
Google Career Certificates

and 13 more instructors

Offered by

Reddit Posts and Comments

0 posts • 15 mentions • top 15 shown below

r/networking • comment
3 points • jaogiz

Here’s a free course:

r/coursera • comment
1 points • kl2342

Try this direct link to course 2

r/devops • comment
1 points • yetAnotherPousa

It is not a book, but an online course. Goes from the basics of networking.

r/compsci • comment
1 points • anuragroy11

For Networks, I can recommend this free course by Google

r/ethdev • comment
2 points • anon333777

Very interesting, thank you! On a related note, would you suggest I take this brief course as part of my blockchain journey? I see it touches on DNS for example.

r/ITCareerQuestions • comment
1 points • am-i-the-rabbit

Try this:

There are free courses for most everything in IT/CS on Coursera and edX. If you're not a Microsoft hater, Microsoft Learn is also a great resource but most of their infrastructure and networking resources are geared towards Azure.

Alternatively, any Network+ or CCNA study guide should give you a more-than-suitable working knowledge of networking. Unless you're wanting to dive into full time network administration or cyber security, though, even that might be overkill.

If you're interested, specifically, in developing a working knowledge of networking as it applies to DevOps, my best advice is to learn the fundamentals of networking, but focus your studies on the upper layers of the OSI model (that is, the Application, Presentation, Session, and Transport layers). If you use virtualization (and, therefore, virtual networking), study up on the Network layer, too; make sure you understand how subnetting works.

Good luck. And I did this the other way around (I started in net/sys admin and segued into DevSecOps later); feel free to DM me (might take a few days for me to get back to you, but I will, I promise) if you want anymore suggestions.

r/devops • comment
1 points • sudoreboot-f

Honestly, that's where I got my start. I recently looked through the materials for the Google IT Support Professional Certificate (you can just audit it for free), and they had some pretty decent starter material on networking as well.

r/sysadmin • comment
1 points • shiro_eugenie

Coursera has a great course on Networking by google

r/suggestmeabook • comment
1 points • bartimaeus_

This is not exactly a book and might be what you are looking for but I remember doing the course sometime ago just for the basics and being satisfied. You can check it out if you don't mind video resources. And if you do not get enough recommendations here then a better place might be /r/compsci/ or even as they generally have master threads with list of books for most topics.

r/hacking • comment
1 points • precisionroy

Take these Coursera courses. They're a good intro and will ease you in to the basic concepts:

Take things slow. Learn one thing at a time and learn the basics well. It'll all build up. Focus on the process of learning instead of the product/final goal.

r/networking • comment
0 points • zraklarP

I've mainly looked at these two courses:

But I'm afraid that they'll be more catered towards the not-so-techy people.

r/learnprogramming • comment
1 points • Hernanpm
r/ITCareerQuestions • comment
2 points • VA_Network_Nerd

r/computing • comment
1 points • QuickenMcNuggets

You're correct, knowing an IP may help give someone an idea of where you are in the world (which could be inaccurate because of ISP configurations, or proxy settings used by the user). It's probably not even accurate to say there's a possible radius ... more like a city, or state, or region most likely.

Since this is /r/computing, and I have interest in computer networking, I thought I'd elaborate further. This is a gross simplification of how IP addressing works, but the range can be anything from 1-255.0-255.0-255.1-254 - the addresses and are reserved addresses for network and broadcast, and can't be assigned. There's a lot of resources online for why this is, but check out for a course on the matter.

This address space represents the total number of IPv4 addresses - 4,294,967,296 IPs - but there's some caveats to that number. Namely, Private IP addresses are carved out of this pool of numbers and cannot be assigned by ISP's to customers for their WAN (Wide Area Network, or Public) interface. Also these networks are assigned in blocks to subscribers, which is determined by a subnet mask value. The ISPs all have a portion of the total public IP address ranges, and carve up their portions to their subscribers using subnet masks.

Going back to the question of using an IP address to find the location of a user, IP addressing does only give a partial idea of a user's location. IP addressing is also VERY easy to spoof or obfuscate using a proxy service. As others have mentioned, the process involved to backtrace an IP address to a physical location or subscriber is not trivial, especially if you're not a law enforcement agency or have authority to issue subpoenas. Furthermore, the IP address you obtain would most likely be a public IP address for the customer or business modem, which acts as an interface between the subscriber's Private network and the Public internet. This modem is likely in close proximity to the user, but doesn't necessarily align directly with the user, and in enterprise scenarios could be in separate buildings from where the end user physically resides.

You can certainly run a "whois" on an IP address, and for example gives a good "idea" of a location for a public IP address, but to really get more detail on what subscriber was using that IP address, and when, would require accessing the DHCP or static provisioning systems for the related ISP, and cross referencing DHCP or static configuration logs against a subscriber ID table or similar ... not something easily done, or easy to do without significant investment.

Then there's IPv6, which is much more unique to a user, but still would be difficult to backtrace to a given location because of how address assignments would be handled by the ISP and would require either the ISP to divulge subscriber information based on IP assignment, or for the investigator to access the subscriber-to-IP relationship through some other method.

r/compsci • comment
1 points • sharjeelsayed

The Bits and Bytes of Computer Networking -Grow with Google (Computer Networking Complete Course by Google - Beginner to Advanced)

Computer Networking: A Top-Down Approach (7th Edition) (Supplements: Wireshark Labs)

CS144 Introduction to Computer Networking Stanford University

High Performance Browser Networking

Beej's Guide to Network Programming

Unix Network Programming, Volume 1: The Sockets Networking API (3rd Edition)

Additional Material:

CCNA Routing and Switching 200-125 Official Cert Guide Library

CBT Nuggets by Jeremey Cioara

Eli The Computer Guy

Load Balancing Servers, Firewalls, and Caches

Professor Messer - Seven Second Subnetting

More at