Getting my head round TCP/IP

Kua

Kua

Kua

Associate
Joined
21 Jul 2008
Posts
512
Location
Lancaster
I'm revising for a first year ug networking exam. HTTP is easier to get your head round, because its possible to view HTTP requests and responses.

TCP/IP less so.

So far as I understand it when a HTTP request is made from a client to a web server they must set up a Transmission Control Protocol 'connection' - a protocol by which they agree to exchange information. I know its at the transmission layer and its analagous to the delivery firm you choose to deliver a package.

Is it possible to see some kind of code that would firm up my understanding? As far as I know TCP is also a request/response type protocol, so it must send messages itself...

Networking seems so abstract! Anyway the plan is over summer to start using Linux - perhaps that'll help.
 
Wow, that app is fantastic, better than I could've hoped for. Good explanation too. Thanks!

192.168.1.5 kind of acts as your own IP address, but isn't actually your IP address, presumably to keep it secret...

Also, am I correct in thinking that each line is an individual packet?
 
Last edited:
packets.jpg


Let me see if I've got this roughly right:

Packets 1-3: Are they to do with setting up the TCP?

Packet 4: Is the client sending a request to its domain name server to find the numerical IP address for the domain name I entered in the URL?

Packet 10: The TCP connections must be established because the client is able to send a GET HTTP request to the server.

First thing that strikes me is the amount of TCP packets the client sends and receives. I guess that's because every time we try to send an HTTP packet, there is a series of requests and acknowledgments between the client and server.

I need to read more into it... To be honest I think this is far more advance than I need but still its useful knowledge.

Do you work with networks tntcoder?
 
Don't worry if you don't have time to answer all these questions btw!

But why is it that after packet 7 we are contacting a different computer in the same domain?

Wait, actually its a different domain. 208.111.171.82 initially. Then 207.126.123.20
 
You must log in or register to reply here.
Back
Top Bottom