Goatboy wrote:Oh, that's simple. All you need to do is dedicate many years of your life to studying security.
iistapp wrote:Can't seem to figure it out exactly how it works, so just want someone to clear it out for me if possible ;p
Goatboy wrote:Oh, that's simple. All you need to do is dedicate many years of your life to studying security.
Gatito wrote:Now that you got the IP ( say 64.32.24.200 ) your PC compares that with his own IP and finds out that the server isn't in his local network so he sends the http request to the router pointing out of the network.
Gatito wrote:Now when this router receives the request it compares the IP with its table which holds all the IPs of the devices that are connected with him and he probably won't find the server directly, but this router knows that there is another router connected with him which has a bigger scope and knowledge than him so he sends the request to the other router.
iistapp wrote:Thanks Gatito for the answer, so the local network talks with the Internet throught a bunch of different routers around the world? And the DNS converts a url into the right IP for the site or am I wrong?
If that's how it works then I thank you for your answer :)
Phantom Wolf wrote:No, it doesn't. Your computer keeps a routing table that tells it where to send packets so that they get to the proper host/network. Basically, when your computer needs to send out a packet, it checks its routing table for an entry that matches the packet's destination address. That entry will contain all the information that your computer needs to send the packet.
Phantom Wolf wrote:Most routers also use routing tables similar to what I described above. Also, they wouldn't check a list of attached devices, if the destination IP is a local address, it would send out an ARP packet.
Phantom Wolf wrote:DNS converts domain names to IPs, not the whole URL
Users browsing this forum: No registered users and 0 guests