91–100 of 138 posts
This is very interesting, thank you. I didn't get this line > As it happens, 00101 is also binary for the number 5. If you start counting at 0 (A = 0, B = 1, C = 2, and so on), then R is also number 5. R is 17, not 5. You might want to reword it. Stopped here to ask you this and haven't read further yet.
I feel like walkie talkies are something all network engineers need to play with. Furthermore, remember that real world telephone and radio networks were in fact... Networks. (Called 'nets' in the radio world) Ethernet, and 802.11, are both based on the concept of a singular channel shared by many individuals. When Alice talks, she says 'I'm Alice calling Bob, can you hear me Over'. Alice is the source address. Bob i…
> Ethernet, and 802.11 full duplex ethernet circuits (eg: a basic cheap 10Gbps 1310/LR carried over two $30 transceivers and a six foot fiber patch cable between two pieces of equipment) and a half-duplex TDD/CSMA regime like 802.11b/g/n/ac/ax are not the same thing. yes they both enable ethernet connectivity between devices on fabrics of things that can see and arp each other. the ethernet 10GbE might be shared by m…
I probably should have clarified that when I said "Ethernet", I meant classic 10 Mbps Ethernet that today's kids probably don't know about. The Ethernet hub acted like a bus: anything one connection said was broadcast to _ALL_ other connections.
Of course, today we have far faster point-to-point switches. But it helps to remember that the Ethernet-protocol was built in the days of old: half-duplex shared communication broadcast to everyone on your hub.
-------
Today's wired 1Gbps or 10Gbps ethernet are way way faster than half-duplex channels that 802.11 / Wireless technologies are forced to use (after all: the physics behind 802.11 and walkie talkies remains fundamentally the same)
There probably isn't a need for CSMA/CD systems in Ethernet anymore (since today's networks are all dedicated wires). But still, the CSMA/CD system exists for a reason, a legacy of the old "shared ether network communications" that gives rise to the name "Ethernet". (One Ether that everyone on the network can hear simultaneously, like a walkie talkie)
> The answers I get have taught me that most programmers don't have a basic understanding of how the internet works outside of their narrow specialty. This lack of a rudimentary mental model is one of the largest contributors to wasted time and effort in web application development. I'm curious what specific mistakes you're thinking of that application developers make when they don't understand computer networks. In…
In https://www.networksfromscratch.com/2.html
"Remember that when someone presses button 0 the output is set to -5v and when someone presses button 1, the output is set to +5v."
This should be 0v, +5v.
"We connect two output pins on the letter writer to two input pins to the input pins that were previously connected to the buttons."
This sounds really weird.
> The answers I get have taught me that most programmers don't have a basic understanding of how the internet works outside of their narrow specialty. This lack of a rudimentary mental model is one of the largest contributors to wasted time and effort in web application development. I'm curious what specific mistakes you're thinking of that application developers make when they don't understand computer networks. In…
I once blew the minds of a room full of senior engineers by setting up a server which responds with the headers and different chunks of the body at different times, and so the content appears sequentially in the browser with a delay. They literally did not know you could do that.
Was looking for a TOC, but quickly realized it's still in progress. Any ballpark on how many chapters there would be? Thanks and keep it up!
You're welcome! Probably somewhere between 25 and 30.
I have written, or been involved in the writing of, a few books. My e pertain every was that it is easier to start a book from the TOC.
I am assuming you will be using LaTex or something similar? Writing a book in anything other than a structured writing environment can be hell. Certainly avoid ms word like a cockroach should avoid a hammer.
I tried checking the content with my kindle (a Kindle Touch paperwhite 6 inches) and the first chapter rendered pretty good, with images and text aligning as intended. However the second chapter did not render the first figure and beyond. Chapter 3 rendered OK, similar to Ch 1.
A few more feedback if that helps for enhancing the format even more: - Colors, and references to those do not work on a kindle. I only saw one minor use of colors (red, green) in Chapter 1 so that's not a blocker. - For some reason, the kindle browser doesn't put left and right margins on the page, so the text uses the full length of the device. - Links are rendered with a pale gray, sometimes hard to distinguish. - Figuring out why the Chapter 2 did not render would definitely help.
I feel like walkie talkies are something all network engineers need to play with. Furthermore, remember that real world telephone and radio networks were in fact... Networks. (Called 'nets' in the radio world) Ethernet, and 802.11, are both based on the concept of a singular channel shared by many individuals. When Alice talks, she says 'I'm Alice calling Bob, can you hear me Over'. Alice is the source address. Bob i…
> Ethernet, and 802.11 full duplex ethernet circuits (eg: a basic cheap 10Gbps 1310/LR carried over two $30 transceivers and a six foot fiber patch cable between two pieces of equipment) and a half-duplex TDD/CSMA regime like 802.11b/g/n/ac/ax are not the same thing. yes they both enable ethernet connectivity between devices on fabrics of things that can see and arp each other. the ethernet 10GbE might be shared by m…
When sailing through the computer network topic, my great companion was Tanenbaum's and Richard Stevens's book. Although, I have to be honest that if I only read that book without exposure to the real-world problem, I might quit computer networks many years ago.
My two cents for the rest of the chapters would be: to make sure to provide a real-world problem and example in which anyone could have access to them. In my case, I had the privilege to build a real network (10k users) with FreeBSD as the router, proxy, DNS, mail, etc. With all the tooling available today, one can easily acquire these swiss army knives for networking. Sure, tooling comes and goes, but at least it can provide better abstractions to the students. At least it worked for me.
https://youtu.be/hFsjbBfFyLg?t=503
It was meant to be a Django tutorial, but I wanted the audience to get an idea about how HTTP works.