Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3701
| From | William Unruh <unruh@invalid.ca> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: networking and fragments |
| Date | 2016-04-12 03:16 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <nehpap$opv$1@dont-email.me> (permalink) |
| References | <nehfiq$d6t$2@reader1.panix.com> |
On 2016-04-12, Popping mad <rainbow@colition.gov> wrote: > Hi > > I'm reading this line in the Ross - Kause textbook "Computer Networking - > Top-Down Aproach" and it says > > > "The solution is to fragment the data in the IP datagram into two or more > smaller IP datagrams, encapsulate each of these smaller IP datagrams in a > separate link-layer frame; and send these frames over the outgoing link. > Each of these smaller data-grams is referred to as a fragment. > > Fragments need to be reassembled before they reach the transport layer at > the destination. Indeed, both TCP and UDP are expecting to receive > complete, unfragmented segments from the network layer." > > I thought that was wrong. They have to be reassembled AT the > destination, not before that. YOu have misread. "need to be reassembled before they reach the transport layer" is the key phrase. Ie, they are reassembled on the destination machine but before they are handed over to the transport layer. > > > ? > > Where am I confused, or is this in fact incorrect? > > Reuvain
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
networking and fragments Popping mad <rainbow@colition.gov> - 2016-04-12 00:30 +0000
Re: networking and fragments William Unruh <unruh@invalid.ca> - 2016-04-12 03:16 +0000
Re: networking and fragments Pascal Hambourg <boite-a-spam@plouf.fr.eu.org> - 2016-04-23 12:05 +0200
Re: networking and fragments Jorgen Grahn <grahn+nntp@snipabacken.se> - 2016-04-24 12:53 +0000
csiph-web