October 6th, 2003 08:28 PM
[gloworange]And then it happened... a door opened to a world... rushing through the phone line like heroin through an addict\'s veins, an electronic pulse is sent out, a refuge from the day-to-day incompetencies is sought... a board is found. \"This is it... this is where I belong...\" I know everyone here... even if I\'ve never met them, never talked to them, may never hear from them again... I know you all...[/gloworange]
October 12th, 2003 02:33 PM
Thanks for taking the time to write this.
October 12th, 2003 06:39 PM
UDP -- The User Datagram Protocol (UDP) is in the same OSI layer as TCP. UDP is more used for simple data transfers.
| source port | destination port |
| length | checksum |
The (network) protocol IP from OSI layer 3 is only responsible for transporting packets from one to another. Both transport protocols TCP and UDP have to make sure that the packets are received by the right computer. To arrange this, UDP and TCP are using ports for addressing. A port is a 16 bits number. A not standard application which uses UDP or TCP can use different ports on both sides of the communication line or choose a port which is free. (portnumbers from 0 to 255 have a special meaning because some of them are standard we call them "well known ports", ports which have the number 256 and above are used for different applications which are not standard.
October 15th, 2004 06:53 AM
Wow!!! how great this is men !@!!!
October 4th, 2006 04:19 PM
thanks for the tut ;its a really good one and written in a nice way
October 24th, 2006 06:48 PM
A belated reply but I had to post something about:
Wow...I continued reading the thread after I read this...and I am still laughing now!
Originally Posted by Arcanus Aegis
Could someone tell me how my UDP DNS lookups get off my small internal network, past two routers, two firewalls, out on to the internet, past countless other backbone routers, find a DNS server and come all the way back on to my small internal network.....and at the same time have a destination address of my subnets broadcast address as it has to be a broadcast packet because it is UDP......cause I am mighty confused now!
I didn't see a mention of TCP Sequence numbers on the original explanation, which are just as important as the TCP flags - if not more so.
This is NOT a plug for myself or the site but as there seems to be some genuine interest in this subject, there are some slightly more advanced TCP/OSI/Routing etc tutorials HERE HERE and HERE
October 24th, 2006 07:19 PM
It also makes sure that all packets get there in the same order that they were sent.
Originally Posted by Nokia
hehehe.. I thought the same thing Nokia. When I saw the first quote that I put into this reply I laughed pretty hard. TCP doesn't care what order the packets arrive in because it can put them back into the proper order. So to say that TCP makes sure that all apckets get there in the same order that they were sent is completely wrong.
You need to implement some type of Quality Of Service(QOS) on top of tcp/ip for packets that absolutely have to arrive in the proper order. The best example of this is VOIP or internet based TV.