Ethereal-dev: Re: [Ethereal-dev] [patch] add TCP desegmentation to laplink dissector

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Loïc Minier <lool+ethereal@xxxxxxxxxx>
Date: Mon, 20 Oct 2003 10:19:47 +0200
Ronnie Sahlberg <ronnie_sahlberg@xxxxxxxxxxxxxx> - Mon, Oct 20, 2003:

> Othervise, Imagine how surprised an innocent user would be when his Ethereal
> completely hangs when
> he loads a huge NFS over TCP capture with many many READ/WRITEs in it. :-)

 Yes, Ethereal's default seems logical to a developper, but it's
 disappointing for an user when he turns on TCP-desegmentation and forgets
 IP-reassembly for example. The same thing happens when he'd like to see
 a protocol running atop TCP reassembled but forget TCP-desegmentation.
   One could think the Preferences miss some logic, but it's really a
 difficult problem because one protocol can run atop of a lot of other
 protocols. May be dissectors of a level noticing the users wants
 desegmentation/reassembly should be able of requiring their lower level
 protocol to turn on desegmentation/reassembly too.

   As a temporary workaround, what do you think of including a hint
 regarding "IP reassembly" or "TCP desegmentation" in the comments of
 the reassembly options for all dissectors providing desegmentation?

-- 
Loïc Minier <lool@xxxxxxxx>