On Wed, May 04, 2011 at 10:27:32PM +0200, Sake Blok wrote:
> On 4 mei 2011, at 22:11, Jeff Morriss wrote:
> > I would think desegment_tcp() should be able to handle this by not calling
> > your dissector for an out-of-order segment:
> it should be able to only call your dissector once it has a co
2011/5/5 Jeff Morriss :
>
> I did stumble across a (apparently unrelated) problem in that it will fail
> if you see a gap while the subdissector is returning
> DESEGMENT_ONE_MORE_SEGMENT (as HTTP does until it gets all the headers): in
> that case TCP has to assume that the current message is not p
On 4 mei 2011, at 23:33, Jeff Morriss wrote:
> Sake Blok wrote:
>> On 4 mei 2011, at 22:48, Jeff Morriss wrote:
>>> Sake Blok wrote:
One case that can cause a problem is when the first segment of a PDU is
received out-of-order. Or did your recent work also handle this exception,
J
Max Dmitrichenko wrote:
2011/5/5 Jeff Morriss :
I would think desegment_tcp() should be able to handle this by not calling
your dissector for an out-of-order segment: it should be able to only call
your dissector once it has a completely reassembled (desegmented) PDU.
Did you mean using of tc
Sake Blok wrote:
On 4 mei 2011, at 22:48, Jeff Morriss wrote:
Sake Blok wrote:
On 4 mei 2011, at 22:11, Jeff Morriss wrote:
Max Dmitrichenko wrote:
Hi!
I'm continue to write dissector for an encrypted protocol. Everything
works fine until I receive an out-of-order TCP segment, i.e. previous
w
2011/5/5 Jeff Morriss :
> I would think desegment_tcp() should be able to handle this by not calling
> your dissector for an out-of-order segment: it should be able to only call
> your dissector once it has a completely reassembled (desegmented) PDU.
Did you mean using of tcp_dissect_pdus()?
On 4 mei 2011, at 22:48, Jeff Morriss wrote:
> Sake Blok wrote:
>> On 4 mei 2011, at 22:11, Jeff Morriss wrote:
>>> Max Dmitrichenko wrote:
Hi!
I'm continue to write dissector for an encrypted protocol. Everything
works fine until I receive an out-of-order TCP segment, i.e. previous
2011/5/5 Jeff Morriss :
> Sake Blok wrote:
>>
>> On 4 mei 2011, at 22:11, Jeff Morriss wrote:
>>
>>>
>>> I would think desegment_tcp() should be able to handle this by not
>>> calling your dissector for an out-of-order segment: it should be able to
>>> only call your dissector once it has a complet
Sake Blok wrote:
On 4 mei 2011, at 22:11, Jeff Morriss wrote:
Max Dmitrichenko wrote:
Hi!
I'm continue to write dissector for an encrypted protocol. Everything
works fine until I receive an out-of-order TCP segment, i.e. previous
was lost.
Since I'm trying to decrypt it, I fail with it and bre
On 4 mei 2011, at 22:11, Jeff Morriss wrote:
> Max Dmitrichenko wrote:
>> Hi!
>> I'm continue to write dissector for an encrypted protocol. Everything
>> works fine until I receive an out-of-order TCP segment, i.e. previous
>> was lost.
>> Since I'm trying to decrypt it, I fail with it and break
Max Dmitrichenko wrote:
Hi!
I'm continue to write dissector for an encrypted protocol. Everything
works fine until I receive an out-of-order TCP segment, i.e. previous
was lost.
Since I'm trying to decrypt it, I fail with it and break the whole
decryption context. Is there any way to:
1) Detect
Oon perjantaina toimistolla.
Mikko
Max Dmitrichenko wrote:
>Hi!
>
>I'm continue to write dissector for an encrypted protocol. Everything
>works fine until I receive an out-of-order TCP segment, i.e. previous
>was lost.
>Since I'm trying to decrypt it, I fail with it and break the whole
>decrypt
Hi!
I'm continue to write dissector for an encrypted protocol. Everything
works fine until I receive an out-of-order TCP segment, i.e. previous
was lost.
Since I'm trying to decrypt it, I fail with it and break the whole
decryption context. Is there any way to:
1) Detect that this packet is out of
13 matches
Mail list logo
