1
All computers connected in a network are hosts, right? According to Wikipedia the hosts are hardware that communicate with other network nodes, so a router can be considered a host? And what differentiates a host one-knotted?
Another thing: Studying about networks, I saw that the routers have internally the routing tables that allow it to go directing the packets from point to point until it reaches its final destination. What are these points of the network that the packets go through? For example: if I, who am in Rio Grande do Sul, am requesting something from a server who is in São Paulo, what are these points that he passes? What are these routers?
Are my provider’s devices and a larger structure? Are these the nodes?
EDIT: Links in Portuguese or English that can explain these questions to me are welcome.
I voted to close as broad because, although some topics are "acceptable" on the site, most of them believe need to explain concepts that may end up escaping the scope of the site.
– user28595
Hi @Articuno Can help me make it adapted to the site?
– Evilmaax
The first doubt I believe is acceptable, the rest ends up getting into hardware concepts, which is totally outside the scope of the site
– user28595
@Articuno , I am opening a question in the goal on the salvation of this question, I believe it is not so off topic or as wide as that. I paste the link as soon as I have asked
– Jefferson Quesado
@Jeffersonquesado most of the issues come into hardware matters, despite broadening the scope, it is not the focus to add hardware to it.
– user28595
@Articuno, here: https://pt.meta.stackoverflow.com/q/6390/64969
– Jefferson Quesado
@Max we are talking about tcp/ip v4 networks here?
– Intruso
@Intruder Exactly, Ipv4
– Evilmaax
I am in favor of creating new questions, one for each specific point of this question. Your content is salvable, but not in a single question.
– Oralista de Sistemas
@max, look at the discussion about your question there, see if it can further improve your question.
– Intruso
I’m scratching here to start an answer, but, there are some network things there that people will style, the protocol part is basically documentation on routing algorithms, the Rfcs themselves already help a lot, but there are other questions that are basically the concepts of networks to understand the algorithms, you know? Maybe if we try to direct more protocols/algorithms and explore the concepts, your question will enter the scope of the site. In general, the problem is that the question has many questions and is not focused on programming, bags?
– Intruso
Your question may be better answered here: https://networkengineering.stackexchange.com/
– Intruso
Actually, my question was more basic. I know the people here value the highest quality in everything they do, but I wasn’t even thinking about getting into the technical and engineering details. Anyway, thank you all so far
– Evilmaax
Max, take advantage of the Anderson edition and remove all other questions, leaving only the one related to the title. The question of the title is acceptable on the site, Too, anyone who answers can leave references for you to read, because this does not escape the scope.
– user28595
@Max what people are trying to say is that it’s usually bad to ask too many questions in one place, because you end up losing focus and getting too comprehensive. You can even ask the person to clarify a path, but the more objective the question the better.
– Intruso
@Intruder There’s already a question there
– Bruno Costa